<smacks forehead>

Ya.. that is a lot easier.

Someone should put this in as a feature request.  I don't want HA (and have
errors on getting that to work)  I just want VMs to boot on initial cluster
start.

this was standard in libvirt :)   I am trying to convert to oVirt ways...

On Wed, Sep 30, 2020 at 4:10 PM Derek Atkins <[email protected]> wrote:

> HI,
>
> On Wed, September 30, 2020 3:50 pm, Jeremey Wise wrote:
> > As the three servers are Centos8 minimal installs. + oVirt HCI wizard to
> > keep them lean and mean... a couple questions
>
> Note that you run this on the Engine VM, not on a host.
>
> > 1) which version of python would I need for this (note in script about
> > python 2 but isn't that deprecated?)
> > [root@thor /]# yum install python
> > Last metadata expiration check: 2:29:38 ago on Wed 30 Sep 2020 01:18:32
> PM
> > EDT.
> > No match for argument: python
> > There are following alternatives for "python": python2, python36,
> python38
> > Error: Unable to find a match: python
>
> I am still running 4.3, so "python" is 2.7.
> I have not tested with python3..
>
> > 2)  When you have three nodes.. one is set to host the ovirt-engine
> > active,
> > and another as backup.  If this is added to rc.local.   Of the two nodes
> > hosting HA for oVirt-engine.. node which boots first will host (or so it
> > seems). I think if I add this to both those hosts .. it will not create
> > issues.  Any thoughts?
>
> Don't run it on a host, run it from within the Engine VM.
>
> The host(s) will figure out by themselves that they need to start the
> engine if one isn't running.  Then when the engine starts the script will
> run and start the VMs.
>
> -derek
>
> >
> > On Wed, Sep 30, 2020 at 3:23 PM Derek Atkins <[email protected]> wrote:
> >
> >> I run it out of rc.local:
> >>
> >> /usr/local/sbin/start_vms.py > /var/log/start_vms 2>&1 &
> >>
> >> The script is smart enough to wait for the engine to be fully active.
> >>
> >> -derek
> >>
> >> On Wed, September 30, 2020 3:11 pm, Jeremey Wise wrote:
> >> > i would like to eventually go ansible route..  and was starting down
> >> that
> >> > path.... but this is fabulous.
> >> >
> >> > I will modify and post how it went.
> >> >
> >> > One question:  How /where do you set this saved new and delicious
> >> script
> >> > so
> >> > once oVirt-engine comes up... it runs?
> >> >
> >> > Thanks
> >> >
> >> > On Wed, Sep 30, 2020 at 2:42 PM Derek Atkins <[email protected]> wrote:
> >> >
> >> >> Hi,
> >> >>
> >> >> I had a script based around ovirt-shell which I re-wrote as a script
> >> >> around the Python SDK4 which I run on my engine during the startup
> >> >> sequence.  The script will wait for the engine to come up and ensure
> >> the
> >> >> storage domains are up before it tries to start the VMs.  Then it
> >> will
> >> >> go
> >> >> ahead and start the VMs in the specified order with specified delay
> >> >> and/or
> >> >> wait-for-up signal between them.
> >> >>
> >> >> You can find my scripts at https://www.ihtfp.org/ovirt/
> >> >>
> >> >> Or you can go the ansible route :)
> >> >>
> >> >> Enjoy!
> >> >>
> >> >> -derek
> >> >>
> >> >> On Wed, September 30, 2020 11:21 am, Jeremey Wise wrote:
> >> >> > When I have to shut down cluster... ups runs out etc..  I need a
> >> >> sequence
> >> >> > set of just a small number of VMs to "autostart"
> >> >> >
> >> >> > Normally I just use DNS FQND to connect to oVirt engine but as two
> >> of
> >> >> my
> >> >> > VMs  are a DNS HA cluster..  as well as NTP / SMTP /DHCP etc...  I
> >> >> need
> >> >> > those two infrastructure VMs to be auto boot.
> >> >> >
> >> >> > I looked at HA settings for those VMs but it seems to be watching
> >> for
> >> >> > pause
> >> >> > /resume.. but it does not imply or state auto start on clean first
> >> >> boot.
> >> >> >
> >> >> > Options?
> >> >> >
> >> >> >
> >> >> > --
> >> >> > p <[email protected]>enguinpages
> >> >> > _______________________________________________
> >> >> > Users mailing list -- [email protected]
> >> >> > To unsubscribe send an email to [email protected]
> >> >> > Privacy Statement: https://www.ovirt.org/privacy-policy.html
> >> >> > oVirt Code of Conduct:
> >> >> > https://www.ovirt.org/community/about/community-guidelines/
> >> >> > List Archives:
> >> >> >
> >> >>
> >>
> https://lists.ovirt.org/archives/list/[email protected]/message/VAYHFFSANCBRN44ABBTXIYEAR3ZFCP6N/
> >> >> >
> >> >>
> >> >>
> >> >> --
> >> >>        Derek Atkins                 617-623-3745
> >> >>        [email protected]             www.ihtfp.com
> >> >>        Computer and Internet Security Consultant
> >> >>
> >> >>
> >> >
> >> > --
> >> > [email protected]
> >> >
> >>
> >>
> >> --
> >>        Derek Atkins                 617-623-3745
> >>        [email protected]             www.ihtfp.com
> >>        Computer and Internet Security Consultant
> >>
> >>
> >
> > --
> > [email protected]
> >
>
>
> --
>        Derek Atkins                 617-623-3745
>        [email protected]             www.ihtfp.com
>        Computer and Internet Security Consultant
>
>

-- 
[email protected]
_______________________________________________
Users mailing list -- [email protected]
To unsubscribe send an email to [email protected]
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/[email protected]/message/QBAVFB7XLOMSSHYYG5U7W4FIH3KKGC4N/

Reply via email to