Bug 1794460
Summary: | [RFE] boom: support for multi-volumes snapshots | |||
---|---|---|---|---|
Product: | Red Hat Enterprise Linux 8 | Reporter: | jhouston | |
Component: | boom-boot | Assignee: | Bryn M. Reeves <bmr> | |
Status: | CLOSED MIGRATED | QA Contact: | cluster-qe <cluster-qe> | |
Severity: | low | Docs Contact: | ||
Priority: | medium | |||
Version: | 8.1 | CC: | agk, amkulkar, bdm, bmader, bmr, eddie.rowe, jbrassow, jentrena, jesper.schmidt, jwesterl, mcsontos, myllynen, ovasik, pdwyer, rhandlin, rtweed, sandkuma, sujagtap, swachira, vchepkov, vcojot, yferszt | |
Target Milestone: | rc | Keywords: | FutureFeature, MigratedToJIRA, Triaged | |
Target Release: | --- | |||
Hardware: | All | |||
OS: | Linux | |||
Whiteboard: | ||||
Fixed In Version: | Doc Type: | If docs needed, set a value | ||
Doc Text: | Story Points: | --- | ||
Clone Of: | ||||
: | 2177839 (view as bug list) | Environment: | ||
Last Closed: | 2023-09-23 15:59:03 UTC | Type: | Story | |
Regression: | --- | Mount Type: | --- | |
Documentation: | --- | CRM: | ||
Verified Versions: | Category: | --- | ||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | ||
Cloudforms Team: | --- | Target Upstream Version: | ||
Embargoed: | ||||
Bug Depends On: | 2190228 | |||
Bug Blocks: | 2177839 |
Description
jhouston
2020-01-23 16:12:51 UTC
Thanks for the interest in boom, and taking the time to file a bug. I've edited the title a little to make it more clear that this is asking about support for snapshots of more than just the root file system. Although there is an update to the boom package in the Red Hat Enterprise Linux 8.2 beta released this week that includes a number of new features and improvements booting is still limited to the root file system volume in this release: we do plan to support multi-volume snapshots in a future RHEL update but there is a system wide change needed before we can enable this functionality. This includes a mechanism to override the system fstab at boot time without modifying the snapshot contents. We have some prototypes that we are evaluating and we plan to start working on the snapshot manager features after the next boom release. Boom is the first step in a plan to deliver improved bootable snapshot management and rollback capabilities: a white paper was published a couple of years ago that describes the full project - it's still fairly up to date with current work, and it might provide useful information in terms of the direction we are taking for these features. You can find it on GitHub here: https://github.com/snapshotmanager/snapshot-boot-docs The boom project is hosted at: https://github.com/snapshotmanager/boom/ Feedback and suggestions on boom and the broader snapshot manager work are welcome, either via bugzilla or the upstream project pages. The snapshot manager and fstab substitution work will be delivered in different components, but I'll keep this open against boom for the time being so that we can keep track of it. I have a prototype for multi-volume snapshots now that is working well in testing. It consists of a new systemd generator that runs in early boot and allows the content of /etc/fstab to be overridden on the kernel command line. This allows booting into a snapshot of the system state including auxiliary mounts such as /var, /home etc. We are still reviewing the options for including this in the distribution and whether the functionality would be acceptable for systemd upstream but we hope to have more updates soon and will update the bugzilla as this work develops. Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug. This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there. Due to differences in account names between systems, some fields were not replicated. Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information. To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer. You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like: "Bugzilla Bug" = 1234567 In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information. |