Opened 3 years ago

Last modified 2 years ago

#5300 new enhancement

Consider configuration version numbering

Reported by: tomek Owned by:
Priority: medium Milestone: Outstanding Tasks
Component: configuration 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


This ticket is about defining how and then implementing configuration version management. There are at least two opposite approaches this could take:

  1. the use may optionally specify configuration version number and then later retrieve it. The use case for this is a large number of servers that are supposed to have the same version deployed from a central configuration provisioning system. Sysadmin would deploy the configuration and then later check if any of his servers require configuration update.
  1. Kea could internally maintain configuration versions. Every time configuration changes, its internal counter would increase and the configuration would get associated with that number. That's useful to check whether your configuration was changed, e.g. by your automated update script or perhaps some rouge admin. The downside is that this approach would be useless to compare two or more servers whether they have the same configuration version as those numbers would very easily get out of sync on separate servers.

For more background, see comment #3 on Commands.


Change History (1)

comment:1 Changed 2 years ago by tomek

  • Milestone changed from Kea-proposed to Outstanding Tasks

As discussed on 2017-06-22 call, moving to Outstanding.

Note: See TracTickets for help on using tickets.