Opened 6 weeks ago

Last modified 3 weeks ago

#5534 reviewing enhancement

cache-remove, cache-flush commands

Reported by: tomek Owned by: tomek
Priority: medium Milestone: Kea1.4
Component: host-reservations 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: 4
Total Hours: 0 Internal?: no


The RadiusDesign calls for implementation of a caching mechanism. The hosts returned by other backends may be cached. However, this brings a topic of dealing with the information in the cache becoming stale (i.e. they were changed in the original backend, but cache contains old information about it).

To deal with this problem, at least two commands should be implemented:

  • cache-remove that removes a single host
  • cache-flush that removes all hosts

Additional commands may be added if desired, but only if their implementation does not significantly extend the time needed to implement this ticket.


Change History (6)

comment:1 Changed 4 weeks ago by fdupont

  • Owner set to fdupont
  • Status changed from new to accepted

The cache-flush already exists and the code is ready for the cache-remove control as there is a cache-insert doing the opposite.
Requires #5532 (but not #5533).

comment:2 Changed 4 weeks ago by fdupont

  • Add Hours to Ticket changed from 0 to 4
  • Owner changed from fdupont to UnAssigned
  • Status changed from accepted to reviewing

Done. Interface looks like the reservation-del's one.
Ready for review (after #5532).

comment:3 Changed 4 weeks ago by fdupont

  • Owner changed from UnAssigned to fdupont

comment:4 Changed 4 weeks ago by fdupont

  • Owner changed from fdupont to UnAssigned

Please review premium trac5534a (note the 'a') branch.

comment:5 Changed 4 weeks ago by fdupont

Please review kea trac5533a and premium trac5533.
(#5533 is after #5534 in the host cache train).

comment:6 Changed 3 weeks ago by tomek

  • Owner changed from UnAssigned to tomek

Since 5528, 5531, 5532, 5433 and 5534 are on the same branch, reviewing all them at once.

Note: See TracTickets for help on using tickets.