OK will do! No!!, Puppet with Foreman is great, as Foreman is in the same pool as oVirt I think you need to bring those guys some beers to keep them as friends :P and 2015 was a great year of wine ;) I prefer to do all from the GUI so all in would be best as I described but we can test out if on the commandline CLI we can set the status on Maintenance and see if it returns an exitcode when it finished and can be upgraded. Any idea about that ? Thanks! Cheers, Matt 2017-01-23 13:34 GMT+01:00 Yaniv Kaul <ykaul@redhat.com>:
On Mon, Jan 23, 2017 at 2:31 PM, Matt . <yamakasi.014@gmail.com> wrote:
HI Yaniv,
Nice to hear, I will update the other ticket OK ?
Sure.
I use puppet but can I kick and wait for maintenance mode from the commandline ? I doubt if this works
Puppet is so 2015... ;-) If you refer to the command line the CLI, then while you probably can, I re-iterate that the oVirt CLI will be deprecated by the next release. Y.
Thanks!
Matt
2017-01-23 13:13 GMT+01:00 Yaniv Kaul <ykaul@redhat.com>:
On Mon, Jan 23, 2017 at 2:06 PM, Matt . <yamakasi.014@gmail.com> wrote:
Hi All,
Would it not be nice to have the following upgrade options ?
- Only oVirt packages
This is the default.
or - Yum update all packages
And this is requested in https://bugzilla.redhat.com/show_bug.cgi?id=1380498
Selectbox: - Reboot when upgrade finished
Makes sense, please file a request for enhancement for it.
This with the maintenance mode will save a lot of time.
Agreed. Note that you could easily script it in Ansible. Y.
I hope this is possible.
Thanks Matt! _______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users