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鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add support for "pinning" 馃搶 deployments #1460

Closed
cgwalters opened this Issue Feb 21, 2018 · 1 comment

Comments

Projects
None yet
2 participants
@cgwalters
Member

cgwalters commented Feb 21, 2018

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 version N, and wants to keep around N-1 even after a few upgrades for a while so she can easily roll back.

@dustymabe

This comment has been minimized.

Contributor

dustymabe commented Feb 21, 2018

very similar to projectatomic/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

sysroot: Add concept of deployment "pinning" 馃搶
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

sysroot: Add concept of deployment "pinning" 馃搶
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

sysroot: Add concept of deployment "pinning" 馃搶
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