Rollback a zone and related records to a prior version
Registered by
Joe McBride
Upon reviewing prior versions of a zone and related records. A user can then choose a specific prior version and notify the system to update the zone to that version's state.
Example:
User A made a change to record Y on zone X.
User X created zone T with records B, C and D.
An option to define the time period/number of changes to keep is also needed.
Design note:
- The capability would need an API spec, as it should be accessible to users via API
- Database implications
- Ceilometer is considered useful for events the operator cares about (e.g. to track billing changes). It is not necessarily considered a viable implementation for this.
- Use the "state" model vs CRUD for "undoing"
Blueprint information
- Status:
- Not started
- Approver:
- None
- Priority:
- High
- Drafter:
- None
- Direction:
- Needs approval
- Assignee:
- None
- Definition:
- New
- Series goal:
- None
- Implementation:
- Unknown
- Milestone target:
- None
- Started by
- Completed by
Whiteboard
Removing the "point in time" references.
(?)