Add support for "pinning" 📌 deployments
#1460
Labels
Comments
|
very similar to coreos/rpm-ostree#577. basically the difference is in the heuristic. Both want to keep around old deployments. One asks for them to be garbage collected based on a number, the other asks for them to be garbage collected based on a configurable flag. |
cgwalters
added a commit
to cgwalters/ostree
that referenced
this issue
Feb 23, 2018
Example user story: Jane rebases her OS to a new major version N, and wants to keep around N-1 even after a few upgrades for a while so she can easily roll back. I plan to add `rpm-ostree rebase --pin` to opt-in to this for example. Builds on the new `libostree-transient` group to store pinning state there. Closes: ostreedev#1460
cgwalters
added a commit
to cgwalters/ostree
that referenced
this issue
Feb 26, 2018
Example user story: Jane rebases her OS to a new major version N, and wants to keep around N-1 even after a few upgrades for a while so she can easily roll back. I plan to add `rpm-ostree rebase --pin` to opt-in to this for example. Builds on the new `libostree-transient` group to store pinning state there. Closes: ostreedev#1460
cgwalters
added a commit
to cgwalters/ostree
that referenced
this issue
Feb 26, 2018
Example user story: Jane rebases her OS to a new major version N, and wants to keep around N-1 even after a few upgrades for a while so she can easily roll back. I plan to add `rpm-ostree rebase --pin` to opt-in to this for example. Builds on the new `libostree-transient` group to store pinning state there. Closes: ostreedev#1460
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Update 2018-02-23 PR: #1464
We should add
ostree admin pin <deploymentid>which makes the deployment persist until explicitly unpinned. Example user story: Jane rebases her OS to a new major versionN, and wants to keep aroundN-1even after a few upgrades for a while so she can easily roll back.The text was updated successfully, but these errors were encountered: