Opened 5 years ago

Last modified 4 years ago

#3566 new enhancement

Extend DB backends with capability reporting

Reported by: tomek Owned by:
Priority: medium Milestone: Outstanding Tasks
Component: database-all Version: git
Keywords: Cc:
CVSS Scoring: Parent Tickets:
Sensitive: no Defect Severity: N/A
Sub-Project: DHCP Feature Depending on Ticket:
Estimated Difficulty: 0 Add Hours to Ticket: 0
Total Hours: 0 Internal?: no

Description (last modified by tomek)

Once the planned features (host reservation for now, but there will be others) are being implemented, there will be a disparity between backends. Sometimes it will be temporary (implemented feature X for some of the backends), but in other cases it will be permanent (we will likey not implement host definitions in memfile, because it does not give any benefit over keeping it in the configuration file).

Details are TBD, but I think the capability should be a key->value type of thing. We could have the following properties:

host-reservation: yes | no
options-in-hosts: yes | no
subnet-storage: yes | no

This capability reporting could be used for many things:

  • sanity checking (e.g. refusing configuration that attempts to use host definitions from a backend that doesn't support it)
  • affecting how the engine is working (some operations may work differently for memfile that can enforce data integrity vs. mysql which allows user to tweak and possibly corrupt the data)


Change History (4)

comment:1 Changed 5 years ago by hschempf

  • Milestone changed from Kea0.9.1 to Kea0.9.2

comment:2 Changed 5 years ago by hschempf

  • Milestone changed from Kea0.9.2 to Kea1.1

comment:3 Changed 4 years ago by tomek

  • Description modified (diff)

comment:4 Changed 4 years ago by tomek

  • Description modified (diff)
  • Milestone changed from Kea1.1 to Outstanding Tasks

As discussed on Kea-2016-02-03 call, moving this to Outstanding.

Note: See TracTickets for help on using tickets.