Bug 998532 - Snapshot and Rollback Tool
Summary: Snapshot and Rollback Tool
Alias: None
Product: Fedora
Classification: Fedora
Component: Changes Tracking
Version: rawhide
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
Assignee: Jaroslav Reznik
QA Contact:
Whiteboard: ChangeAcceptedF20
Depends On: 998527 1008211 1008212 1021570
TreeView+ depends on / blocked
Reported: 2013-08-19 13:31 UTC by Jaroslav Reznik
Modified: 2018-08-10 12:05 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2018-08-10 12:05:45 UTC
Type: ---

Attachments (Terms of Use)

Description Jaroslav Reznik 2013-08-19 13:31:14 UTC
This is a tracking bug for Change: Snapshot and Rollback Tool
For more details, see: http://fedoraproject.org//wiki/Changes/Rollback

With the advent of thinly-provisioned LVM pools, it has become possible for us to implement full-system LVM snapshotting for recording rollback points. We are planning to support this for yum updates and eventually fedup upgrades going forwards. This change request notes the addition of new tools provided by the roller-derby project to present an interface and a CLI for managing and initiating rollbacks.

Comment 1 Jaroslav Reznik 2013-10-11 08:44:38 UTC
This message is a reminder that Fedora 20 Accepted Changes 100%
Completed Deadline is on 2013-10-15 [1].

All Accepted Changes has to be code complete and ready to be
validated in the Beta release (optionally by Fedora QA). Required
bug state at this point is ON_QA.

As for several System Wide Changes, Beta Change Deadline is a
point of contingency plan, all incomplete Changes will be 
reported to FESCo for 2013-10-16 meeting. In case of any
questions, don't hesitate to ask Wrangler (jreznik).

[1] https://fedoraproject.org/wiki/Releases/20/Schedule

Comment 2 Jaroslav Reznik 2013-10-15 14:20:58 UTC
Move the Change to the next Fedora version, agreed by owner.

Comment 3 Ben Cotton 2018-08-10 12:05:45 UTC
No activity here or on the change page since 2013. Will create new a bug if the change is revived.

Note You need to log in before you can comment on or make changes to this bug.