Cannot mark VMs as highly available?
Hi, I'm running ovirt (4.0.4) with hosted-engine on a single host (replacing a vmware-server system). I just had to reboot the system, and ran through the sequence in this message from April 2014: http://lists.ovirt.org/pipermail/users/2014-April/023861.html to get the sytem back online, and the engine VM came up. But of course none of my other running VMs came back. So I was trying to go in and set them all as Highly Available so that ovirt would start them. I logged into the ovirt admin interface, went to [Virtual Machines], selected one of them, clicked Edit, then the High Availability tab. However even though it's not greyed out, I cannot select the Highly Available checkbox. Clicking on it just does nothing. So I cannot seem to set them as highly available. So what am I missing? Attached is a screenshot of what I'm seeing. I'm connecting using Firefox on a Fedora-23 desktop, in case that makes any difference? -derek -- Derek Atkins 617-623-3745 derek@ihtfp.com www.ihtfp.com Computer and Internet Security Consultant
--Ai73DIFQJCxtgua1FTcSOM4MInOfSAp1B Content-Type: multipart/mixed; boundary="6mHapjsLOhmDOFxFhTs8pdurJ2jNhTM5B"; protected-headers="v1" From: Sven Kieske <s.kieske@mittwald.de> To: users@ovirt.org Message-ID: <663f53d0-4eab-5e85-f4d6-16c2c8435c03@mittwald.de> Subject: Re: [ovirt-users] Cannot mark VMs as highly available? References: <sjmshr0twj8.fsf@securerf.ihtfp.org> In-Reply-To: <sjmshr0twj8.fsf@securerf.ihtfp.org> --6mHapjsLOhmDOFxFhTs8pdurJ2jNhTM5B Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable On 09/11/16 18:04, Derek Atkins wrote:
Clicking on it just does nothing. So I cannot seem to set them as highly available. So what am I missing?
AFAIK in order to use HA, you need to have configured power management and another host in the same cluster (new versions also work with another DC) which acts as a power gate. ovirt ensures your vms run "HA" by being able to fence hosts when they misbehave. So if you got just one host, you can't fence, and you can't set vms as "H= A". HTH --=20 Mit freundlichen Gr=FC=DFen / Regards Sven Kieske Systemadministrator Mittwald CM Service GmbH & Co. KG K=F6nigsberger Stra=DFe 6 32339 Espelkamp T: +495772 293100 F: +495772 293333 https://www.mittwald.de Gesch=E4ftsf=FChrer: Robert Meyer St.Nr.: 331/5721/1033, USt-IdNr.: DE814773217, HRA 6640, AG Bad Oeynhause= n Komplement=E4rin: Robert Meyer Verwaltungs GmbH, HRB 13260, AG Bad Oeynha= usen --6mHapjsLOhmDOFxFhTs8pdurJ2jNhTM5B-- --Ai73DIFQJCxtgua1FTcSOM4MInOfSAp1B Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iQIcBAEBAgAGBQJYJJPCAAoJEMby9TMDAbQRfDQQAKNasvnvKFKhu4SVS4l6Hzrc CJSMWHnF7TITqla6JnCMzxz0bVixJSkp5C1gBfv3gOjvMT2vw/SfPPGqDAqluaOh +opHUsqYCmm01LBhyDKaQGe6r2r9znOVnvF3ZRgoS2vWuHCjSEamUK/e96qfdsAj EdyoyqPFGxQ2ldrR1s5CYFuVJuDAURnboN0W4cJ7FapUiJ2DQ02fApptteTbaNet oXkNwCZLuTZ7DOE4ja4hEl8XOkW2gAHrwi1BOdh0FIHxNpFP7ygicjbHSsUgJr4H LgVzd6emgkDh/GyfilYKHmRUPF2puY4F+l+FVmKon07t+gmn+7Gh6Wgc8StKLtvd hhZgL0pZvMC6e088Hy5Ipke8nFBo4RkuurmxBwadzENsEtmtDQZkjeiFkULWfeeC gb5LJIyRbRiVzeWEvylGl8lgAiU+n0PyY8WyQh3aJRvh2drr4F0fYSxVm6tzQzq/ Pwli5ldpccGawHwnMzu9G7qBl8RJFuBSmxFaaqwbT8qyY7iCAAAGZh+x/9hcSwyy /Pwc616I7AjTaHj1BROs6YFB+Hb9tjQJGQ6oxFst3nYHyO0zIF6/W1SL1EPfj5Gs qtAOg4IlJamzHdIbyBpcuKujsR8Htako61k1/uE+JFKm4jHrO+MYcJzXVeFqUoEO +31ay71qePb55TthXvUH =ONVj -----END PGP SIGNATURE----- --Ai73DIFQJCxtgua1FTcSOM4MInOfSAp1B--
Hi, On Thu, November 10, 2016 10:35 am, Sven Kieske wrote:
On 09/11/16 18:04, Derek Atkins wrote:
Clicking on it just does nothing. So I cannot seem to set them as highly available. So what am I missing?
AFAIK in order to use HA, you need to have configured power management and another host in the same cluster (new versions also work with another DC) which acts as a power gate.
ovirt ensures your vms run "HA" by being able to fence hosts when they misbehave.
So if you got just one host, you can't fence, and you can't set vms as "HA".
Okay, so is there some way to tell ovirt to auto-start VMs? I thought the way to do that was marking them HA. If that's NOT the case, then other than manually writing a script using ovirt-shell to start the VMs when e.g. the engine starts.... Is there some way to tell ovirt to start a VM automatically when the system starts? (e.g. after a power failure)? Thanks, -derek
HTH
-- Mit freundlichen Grüßen / Regards
Sven Kieske
Systemadministrator Mittwald CM Service GmbH & Co. KG Königsberger Straße 6 32339 Espelkamp T: +495772 293100 F: +495772 293333 https://www.mittwald.de Geschäftsführer: Robert Meyer St.Nr.: 331/5721/1033, USt-IdNr.: DE814773217, HRA 6640, AG Bad Oeynhausen Komplementärin: Robert Meyer Verwaltungs GmbH, HRB 13260, AG Bad Oeynhausen
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
-- Derek Atkins 617-623-3745 derek@ihtfp.com www.ihtfp.com Computer and Internet Security Consultant
Okay, so is there some way to tell ovirt to auto-start VMs? I thought =
This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --mxuTsPNrbvXQ0SJ576AsN7F897rT6LsRw Content-Type: multipart/mixed; boundary="mo0oOCTxktV3eRo9EkwDTGDcFXHUGWlNx"; protected-headers="v1" From: Sven Kieske <svenkieske@gmail.com> To: users@ovirt.org Message-ID: <621e7002-c4dc-ba99-64e3-0b6fb450e120@gmail.com> Subject: Re: [ovirt-users] Cannot mark VMs as highly available? References: <sjmshr0twj8.fsf@securerf.ihtfp.org> <663f53d0-4eab-5e85-f4d6-16c2c8435c03@mittwald.de> <fb10f7d2f009bf02d5daa2bf3c183dd0.squirrel@mail2.ihtfp.org> In-Reply-To: <fb10f7d2f009bf02d5daa2bf3c183dd0.squirrel@mail2.ihtfp.org> --mo0oOCTxktV3eRo9EkwDTGDcFXHUGWlNx Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable On 10.11.2016 16:41, Derek Atkins wrote: the
way to do that was marking them HA. If that's NOT the case, then other=
than manually writing a script using ovirt-shell to start the VMs when e.g. the engine starts.... Is there some way to tell ovirt to start a = VM automatically when the system starts? (e.g. after a power failure)?
I'm afraid there is nothing builtin atm, so you must script your own stuf= f. Feel free to vote for this RFE (request for enhancement): https://bugzilla.redhat.com/show_bug.cgi?id=3D1166657 maybe we can get some traction, you are like the 5th person who wants this feature on this ML. I still haven't given up ;) kind regards Sven --mo0oOCTxktV3eRo9EkwDTGDcFXHUGWlNx-- --mxuTsPNrbvXQ0SJ576AsN7F897rT6LsRw Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQGcBAEBCAAGBQJYJLRuAAoJEAq0kGAWDrqlAaIMAIknJYgbEqbGxkxUMxm+Pbjd nS6Aon/8VGQstvHzke6in2HLiO6AB0KRcGg0KvtTiRn7QLniv9qVQJgLEctow8w8 TzIRQREJgC3zayYoou+A4v1I54e7bfipfSDqvvr26uVt8zO0hO3UF4cumSqHAsDy e1n0m9f3pe6HL8hOIPDoqbwJBEp/+lrvMtU2fjcPVXbPcUzYQs5kP8KaNclcPliF kpX8lflJMOvrDAsM9IY+OrYQ/RbN7K9lVU7sG3afI1VdM6ivLuLkaKq5bvETDejJ 89X9PuorwS9iFah9psIhJmwTIBOfqvfWq7/BEp3nYgfYuBIlNVrjjNRyVwE88hpH l39o3f0ccP6bxNjK7dJB7+aUmsA4JmxntyowKmKJYo+alqafbSZXUbrqHUhdS6fu af1q2ST7dMSvVMfTJ3wCQZHHtx920opKL4F/UVjg/ZWFA9+S9LlsHqhoQx66Xlzo B+FB6iZnQHReOAqlV6huti3rLcGDX1l6IGQq99eOXw== =Dgde -----END PGP SIGNATURE----- --mxuTsPNrbvXQ0SJ576AsN7F897rT6LsRw--
On Thu, November 10, 2016 12:54 pm, Sven Kieske wrote:
On 10.11.2016 16:41, Derek Atkins wrote:
Okay, so is there some way to tell ovirt to auto-start VMs? I thought the way to do that was marking them HA. If that's NOT the case, then other than manually writing a script using ovirt-shell to start the VMs when e.g. the engine starts.... Is there some way to tell ovirt to start a VM automatically when the system starts? (e.g. after a power failure)?
I'm afraid there is nothing builtin atm, so you must script your own stuff.
I'm working on it. I've got all the infrastructure in place to do that. Just need one more thing -- the ability to test when the engine is actually operational.
Feel free to vote for this RFE (request for enhancement):
https://bugzilla.redhat.com/show_bug.cgi?id=1166657
maybe we can get some traction, you are like the 5th person who wants this feature on this ML.
I voted for https://bugzilla.redhat.com/show_bug.cgi?id=1325468 which is a bug that you added as a reference to 1166657. I've commented in both.
I still haven't given up ;)
I'm actually surprised there isn't an autostart mechanism. I would have considered that one of the first things to add. But I guess they don't consider a "startup from scratch" use case.
kind regards
Sven
-derek -- Derek Atkins 617-623-3745 derek@ihtfp.com www.ihtfp.com Computer and Internet Security Consultant
Hi, On Thu, November 10, 2016 2:09 pm, Derek Atkins wrote:
On Thu, November 10, 2016 12:54 pm, Sven Kieske wrote:
I'm afraid there is nothing builtin atm, so you must script your own stuff.
I'm working on it. I've got all the infrastructure in place to do that. Just need one more thing -- the ability to test when the engine is actually operational.
For future reference, here's what I did. First, I set up a user and permissions in ovirt UI. The user has Login and RUN_VM permissions. Then I configured .ovirtshellrc with the user credentials (including password). Then I created the following scripts (obviously you can set the VM names and the wait-time between startup to your own settings). Hopefully these scripts will help the next person who needs to solve this problem. -derek cat > /etc/sysconfig/vm_list <<EOF # List of VMs. Key = VM Name. Value = seconds to wait after starting declare -A vm_list=( [vm-1]=60 [vm-2]=60 ) EOF cat > /usr/local/sbin/start_vms.sh <<EOF #!/bin/bash [ -f /etc/sysconfig/vm_list ] || exit 0 . /etc/sysconfig/vm_list # Wait for the engine to respond while [ `ovirt-shell -I -c -F -E ping 2>/dev/null | grep -c success` != 1 ] do echo "Not ready... Sleeping..." sleep 60 done # Now start all of the VMs in the requested order. for vm in "${!vm_list[@]}" do ovirt-shell -I -c -F -E "action vm $vm start" sleep ${vm_list[$vm]} done EOF chmod +x /usr/local/sbin/start_vms.sh cat >> /etc/rc.d/rc.local <<EOF # Start the list of defined virtual machines /usr/local/sbin/start_vms.sh & EOF chmod +x /etc/rc.d/rc.local -- Derek Atkins 617-623-3745 derek@ihtfp.com www.ihtfp.com Computer and Internet Security Consultant
participants (3)
-
Derek Atkins -
Sven Kieske -
Sven Kieske