-
Notifications
You must be signed in to change notification settings - Fork 192
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
atomic-upgrade-svc #44
Comments
Doesn't this daemon have to do all rpm-ostree operations (including rollback, upgrade, status, and probably compose, db) in order to provide the prerequisite locking and coordination? If so, why would it be called 'atomic-upgrade-svc'? |
So basically let's just focus on |
This was done. |
I think we still should have an example systemd unit timer for doing hands-off automatic updates for individual systems. That's an rpm-ostree issue which I'll file here. But at a cluster level one needs to script things more, there are a few projects/models around this like https://github.com/projectatomic/commissaire |
Created #247 for the first part. |
commissiare should already be able to do on demand upgrade and status. I think it would make sense to add rollback as well as an optional operation scheduler (or a controller of local operation schedulers). |
Why rpm-ostree have an issue on automatic updates for individual system? If the system can updated manually, then the automatic is possible. |
Let's talk in #247 for making it easier to turn on automatic host updates as well as scripting them. |
(Note: not called atomic-upgraded since the "d" there parses as English past tense, not Unix daemon)
Some deployments would like to enable automatic updates. We need a mode to make that work well.
See: #40
See: https://github.com/coreos/locksmith
The text was updated successfully, but these errors were encountered: