-
Notifications
You must be signed in to change notification settings - Fork 196
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
Add D-Bus API (and possibly CLI) for better staging and finalizing #1748
Labels
jira
for syncing to jira
Comments
(Note whether we actually use this in FCOS is still being discussed in the ticket above, though such an API on its own seems useful enough). |
Strawman: add e.g. |
jlebon
added a commit
to jlebon/ostree
that referenced
this issue
Apr 16, 2019
Teach `ostree-finalize-staged.service` to check for a file in `/run` to determine if it should do the finalization. This will be used in RPM-OSTree, where we want to be able to separate out "preparing updates" from "making update the default" for more fine-grained control. See: coreos/rpm-ostree#1748
jlebon
added a commit
to jlebon/ostree
that referenced
this issue
Apr 16, 2019
Teach `ostree-finalize-staged.service` to check for a file in `/run` to determine if it should do the finalization. This will be used in RPM-OSTree, where we want to be able to separate out "preparing updates" from "making update the default" for more fine-grained control. See: coreos/rpm-ostree#1748
jlebon
added a commit
to jlebon/ostree
that referenced
this issue
Apr 16, 2019
Teach `ostree-finalize-staged.service` to check for a file in `/run` to determine if it should do the finalization. This will be used in RPM-OSTree, where we want to be able to separate out "preparing updates" from "making update the default" for more fine-grained control. See: coreos/rpm-ostree#1748
jlebon
added a commit
to jlebon/ostree
that referenced
this issue
Apr 16, 2019
Teach `ostree-finalize-staged.service` to check for a file in `/run` to determine if it should do the finalization. This will be used in RPM-OSTree, where we want to be able to separate out "preparing updates" from "making update the default" for more fine-grained control. See: coreos/rpm-ostree#1748
jlebon
added a commit
to jlebon/ostree
that referenced
this issue
Apr 17, 2019
Teach `ostree-finalize-staged.service` to check for a file in `/run` to determine if it should do the finalization. This will be used in RPM-OSTree, where we want to be able to separate out "preparing updates" from "making update the default" for more fine-grained control. See: coreos/rpm-ostree#1748
jlebon
added a commit
to jlebon/rpm-ostree
that referenced
this issue
Apr 18, 2019
Still need to test this properly, but essentially, we teach `UpdateDeployment` to make use of libostree's staging lock and then add a `FinalizeDeployment` API to perform the final unlock & reboot. Closes: coreos#1748
jlebon
added a commit
to jlebon/rpm-ostree
that referenced
this issue
Apr 18, 2019
Still need to test this properly, but essentially, we teach `UpdateDeployment` to make use of libostree's staging lock and then add a `FinalizeDeployment` API to perform the final unlock & reboot. Closes: coreos#1748
jlebon
added a commit
to jlebon/rpm-ostree
that referenced
this issue
Apr 18, 2019
Still need to test this properly, but essentially, we teach `UpdateDeployment` to make use of libostree's staging lock and then add a `FinalizeDeployment` API to perform the final unlock & reboot. Closes: coreos#1748
jlebon
added a commit
to jlebon/rpm-ostree
that referenced
this issue
Apr 24, 2019
Teach `UpdateDeployment` to make use of libostree's staging lock and then add a `FinalizeDeployment` API to perform the final unlock & reboot. I also added a hidden CLI to make testing this easier, but also because it's likely the FCOS-agent-yet-to-be-named will just end up using the CLI to keep it simple. Closes: coreos#1748
jlebon
added a commit
to jlebon/ostree
that referenced
this issue
Apr 24, 2019
Teach `ostree-finalize-staged.service` to check for a file in `/run` to determine if it should do the finalization. This will be used in RPM-OSTree, where we want to be able to separate out "preparing updates" from "making update the default" for more fine-grained control. See: coreos/rpm-ostree#1748
jlebon
added a commit
to jlebon/rpm-ostree
that referenced
this issue
Apr 24, 2019
Teach `UpdateDeployment` to make use of libostree's staging lock and then add a `FinalizeDeployment` API to perform the final unlock & reboot. I also added a hidden CLI to make testing this easier, but also because it's likely the FCOS-agent-yet-to-be-named will just end up using the CLI to keep it simple. Closes: coreos#1748
rh-atomic-bot
pushed a commit
to ostreedev/ostree
that referenced
this issue
Apr 24, 2019
Teach `ostree-finalize-staged.service` to check for a file in `/run` to determine if it should do the finalization. This will be used in RPM-OSTree, where we want to be able to separate out "preparing updates" from "making update the default" for more fine-grained control. See: coreos/rpm-ostree#1748 Closes: #1841 Approved by: cgwalters
jlebon
added a commit
to jlebon/rpm-ostree
that referenced
this issue
Apr 26, 2019
Teach `UpdateDeployment` to make use of libostree's staging lock and then add a `FinalizeDeployment` API to perform the final unlock & reboot. I also added a hidden CLI to make testing this easier, but also because it's likely the FCOS-agent-yet-to-be-named will just end up using the CLI to keep it simple. Closes: coreos#1748
jlebon
added a commit
to jlebon/rpm-ostree
that referenced
this issue
Apr 29, 2019
Teach `UpdateDeployment` to make use of libostree's staging lock and then add a `FinalizeDeployment` API to perform the final unlock & reboot. I also added a hidden CLI to make testing this easier, but also because it's likely the FCOS-agent-yet-to-be-named will just end up using the CLI to keep it simple. Closes: coreos#1748
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In scenarios where rpm-ostree is driven by a separate app (see #1747), we need to provide more control over how updates are applied. This RFE is about being able to separate staging a deployment from rebooting into it by default (see FCOS discussions for details). IOW, we want at least two API enhancements:
ostree-finalize-staged.service
becomes conditional on).systemctl reboot
).The text was updated successfully, but these errors were encountered: