Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[CA lifecycle] OEM partition snapshotting #2203

Open
anmazzotti opened this issue Oct 3, 2024 · 1 comment
Open

[CA lifecycle] OEM partition snapshotting #2203

anmazzotti opened this issue Oct 3, 2024 · 1 comment
Labels
kind/enhancement New feature or request
Milestone

Comments

@anmazzotti
Copy link
Contributor

This is a new feature request for OEM partition snapshotting.

The desire is to be able to create new snapshots when running elemental upgrade.
It also probably makes sense to bind them to system snapshots somehow, so that they can be rolled back together seamlessly.

I am also not sure what the behavior for taking the snapshot should be. Shall the toolkit simply take a snapshot of current OEM, or should the user input a path to take a snapshot from?

@davidcassany
Copy link
Contributor

Yes, ideall would also be nice to check what Micro does for /etc, for which a separate overlayfs layer is kept in persistent area for each snapshot. I wonder if it would make sense adding a flag to snapshot somehow the persistent directories we overlay. Not sure how to handle persistent volumes though 🤔 should we start treating /oem as a special case?

@kkaempf kkaempf added the kind/enhancement New feature or request label Oct 4, 2024
@kkaempf kkaempf added this to the Micro6.2 milestone Oct 4, 2024
@fgiudici fgiudici changed the title OEM partition snapshotting [CA lifecycle] OEM partition snapshotting Nov 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/enhancement New feature or request
Projects
Status: No status
Development

No branches or pull requests

3 participants