The Workstation PRD includes "better upgrade/rollback control" under plans &
policies.
"• Better upgrade/rollback control
If there are any problems with an upgrade or an upgrade breaks a configuration script we
want to offer an easy way for users to roll-back such upgrades and changes."
The Technical Specification doesn't address this requirement. And I'm also not
finding anything in the list archives about it.
I'm aware of three possible candidates for implementing snapshots and rollbacks:
a.) Roller Derby Project: It lists a dependency on LVM Thin Provisioning, which is a new
option in Fedora 20. I'm uncertain if it's considered stable for production use or
not. Also uncertain is if the project is adaptable for Btrfs, although it seems likely.
https://fedorahosted.org/roller-derby/
http://fedoraproject.org/wiki/Changes/Rollback
https://lists.fedoraproject.org/pipermail/devel-announce/2013-July/001204...
b.) Snapper: Lists a dependency on either LVM Thin Provisioning, or Btrfs. Snapper+Btrfs
is the most mature and actively maintained option at this time. It's presently used in
openSUSE, by default when the file system is Btrfs, for at least a couple of years.
https://github.com/openSUSE/snapper/blob/master/README
http://snapper.io/
http://snapper.io/faq.html
c. ) Gnome: Richard Hughes has expressed interest in making this happen within Gnome. As
far as I know it doesn't yet exist, but is expected to depend on either Btrfs or LVM
Thin Provisioning snapshots.
Am I missing any others?
It seems to me the PRD requirement necessitates some assessment of file systems, the
various snapshotting/rollback strategies and software, before the spec can detail an
implementation. Should the facts as they're presently known be included in the spec in
the meantime, with a TDB status?
Chris Murphy