Opened 6 months ago

Last modified 5 months ago

#5299 new enhancement

Configuration timestamp

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

Description

In comment #2 for Commands Shawn had suggested that configuration should have a timestamp. His argument for it is as follows:

I’m thinking of the case of an admin trying to synchronize the configuration
with an external source and being able to confirm that the version or time
stamp is the same as when the external source last updated the configuration
could avoid having to retrieve and compare the entire configuration.

That seems like a good idea, especially with the concept of SubnetCommands being able to update the configuration on the fly. There should be two dates: initial commit and last update.

Subtickets

Change History (1)

comment:1 Changed 5 months 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.