Opened 5 years ago

Last modified 4 years ago

#3500 new enhancement

Lease database capabilities reporting

Reported by: tomek Owned by:
Priority: low Milestone: Outstanding Tasks
Component: database-all Version:
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

We started a discussion about contexts and necessary improvements to the
lease databases. For now, it is apparent that any backend that supports
contexts, will have to be able to store leases with the same address, but
in different contexts. Depending on the backend nature, some of those
may not be convertable to contexts. Hence we need some way for
database backend to report its capabilities. For now, the sole capability
would be whether leases with non-unique addresses can be stored,
but the number of features that backend may or may not support will
grow over time.

The first use case for this will be to report an error if user wants to run
contexts with a backend that does not support contexts.

Subtickets

Change History (4)

comment:1 Changed 5 years ago by tomek

  • Priority changed from medium to low

comment:2 Changed 4 years ago by marcin

  • Milestone changed from Kea1.0 to Kea1.1

Deferring from 1.0 as per 1.0 tickets scrub.

comment:3 Changed 4 years ago by tomek

  • Milestone changed from Kea1.1 to DHCP Outstanding Tasks

comment:4 Changed 4 years ago by tomek

  • Milestone changed from DHCP Outstanding Tasks to Outstanding Tasks

Milestone renamed

Note: See TracTickets for help on using tickets.