[ovirt-users] More advanced update options for Hosts

[Yaniv Kaul]

On Mon, Jan 23, 2017 at 2:41 PM, Matt . <yamakasi.014 at gmail.com> wrote:

> 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 ;)
>

As both oVirt and Foreman will share a booth in FOSDEM , I think we'll have
a beer[1] together.

Please see a presentation[2] I've given last year at Red Hat Summit 2016 on
the integration.

>
> 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 ?
>

Two options: either use the oVirt CLI, or write something with either of
our SDKs or directly against our REST API to ensure the host is indeed in
maintenance mode.
For example in Python, see the example[2]. It's incomplete in the sense
that it does not wait to ensure that host is indeed in maintenance state.

HTH,
Y.

[1] https://fosdem.org/2017/beerevent/
[2]
https://www.redhat.com/files/summit/session-assets/2016/SS44330-bringing-host-life-cycle-and-content-management-into-red-hat-enterprise-virtualization.pdf
[3]
https://github.com/oVirt/ovirt-engine-sdk/blob/master/sdk/examples/remove_host.py


>
> Thanks!
>
> Cheers,
>
> Matt
>
>
> 2017-01-23 13:34 GMT+01:00 Yaniv Kaul <ykaul at redhat.com>:
> >
> >
> > On Mon, Jan 23, 2017 at 2:31 PM, Matt . <yamakasi.014 at 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 at redhat.com>:
> >> >
> >> >
> >> > On Mon, Jan 23, 2017 at 2:06 PM, Matt . <yamakasi.014 at 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 at ovirt.org
> >> >> http://lists.ovirt.org/mailman/listinfo/users
> >> >
> >> >
> >
> >
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ovirt.org/pipermail/users/attachments/20170123/4fe34d4d/attachment.html>