=20=0D=0A> > Fake power management=3F Hello,=0D=0A> >=20=0D=0A> > I'm bu= ilding a small demonstration system for our sales team to take to a=0D=0A=
customer so that they can show them our solutions.=0D=0A> > Hardware:= Two Intel NUC's, a 4 port switch and a laptop.=0D=0A> > Engine: Runs as = a VM on one of the NUCs, which one it runs on is determined=0D=0A> > by p= acemaker.=0D=0A> > Storage: Also managed by pacemaker, it's drbd backed a= nd accessed with iscsi.=0D=0A> > oVirt version: 3.5=0D=0A> > OS: CentOS 6= =2E6=0D=0A> >=20=0D=0A> > The idea is to have our sales representative (o= r the potential customer=0D=0A> > himself) randomly pull the plug on one = of the NUCs to show that the system=0D=0A> > stays operational when part = of the hardware fails.=0D=0A>=20=0D=0A> I assume you are aware that the e= ngine might fence the node it is running on ...=20=0D=0A> Or do you use p= acemaker to run the engine as well =3F=0D=0A>=20=0D=0A> > My problem is t= hat I don't have any way to implement power management, so the=0D=0A> > E= ngine can't fence nodes and won't restart guests that were running on the= =0D=0A> > node which lost power. In pacemaker I can just configure fencin= g over SSH or=0D=0A> > even disable the requirement to do so completely. = Is there something similar=0D=0A> > for oVirt, so that the Engine will co= nsider a node which it can't connect to=0D=0A> > to be powered down=3F=0D= =0A> >=20=0D=0A> > Regards,=0D=0A> >=20=0D=0A> > mots=0D=0A> >=20=0D=0A> = _______________________________________________=0D=0A> > Users mailing =
<br>> Betreff: Re: [ovirt-users] Fake power management=3F<br>> <br= > <br>> <br>> ----- Original Message -----<br>> > From: "= mots" <<a href=3D"mailto:mots@nepu.moe">mots@nepu.moe</a>><br>> = > To: <a href=3D"mailto:users@ovirt.org">users@ovirt.org</a><br>> &= gt; Sent: Friday, November 14, 2014 4:54:08 PM<br>> > Subject: [ovi= rt-users] Fake power management=3F<br>> > <br>> > Fake power = management=3F Hello,<br>> > <br>> > I'm building a small demo= nstration system for our sales team to take to a<br>> > customer so=
------=_Part_31_861888835.1416222010953 Content-Type: multipart/alternative; boundary="=_cjtqlQp4QSYnJhuKs0Xg4VLTs9O15oco497qtVs9HKP3duB5" This is a multi-part message in MIME format. Your mail reader does not understand MIME message format. --=_cjtqlQp4QSYnJhuKs0Xg4VLTs9O15oco497qtVs9HKP3duB5 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Yes, pacemaker manages the engine. That part is working fine, the engine = restarts on the remaining node without problems.=20=0D=0AIt's just that t= he guests don't come back up until the powered down node has been fenced = manually.=0D=0A=0D=0A-----Urspr=C3=BCngliche Nachricht-----=0D=0A> Von:Ba= rak Azulay <bazulay@redhat.com <mailto:bazulay@redhat.com> >=0D=0A> Gesen= det: Mon 17 November 2014 11:35=0D=0A> An: Patrick Lottenbach <pl@a-bot.c= h <mailto:pl@a-bot.ch> >=0D=0A> CC: users@ovirt.org <mailto:users@ovirt.o= rg>=20=0D=0A> Betreff: Re: [ovirt-users] Fake power management=3F=0D=0A>=20= =0D=0A>=20=0D=0A>=20=0D=0A> ----- Original Message -----=0D=0A> > From: "= mots" <mots@nepu.moe <mailto:mots@nepu.moe> >=0D=0A> > To: users@ovirt.or= g <mailto:users@ovirt.org>=20=0D=0A> > Sent: Friday, November 14, 2014 4:= 54:08 PM=0D=0A> > Subject: [ovirt-users] Fake power management=3F=0D=0A> = list=0D=0A> > Users@ovirt.org <mailto:Users@ovirt.org>=20=0D=0A> > http:/= /lists.ovirt.org/mailman/listinfo/users <http://lists.ovirt.org/mailman/l= istinfo/users>=20=0D=0A> >=20=0D=0A>=20=0D=0A=0D=0A --=_cjtqlQp4QSYnJhuKs0Xg4VLTs9O15oco497qtVs9HKP3duB5 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://ww= w.w3.org/TR/html4/loose.dtd"><html>=0A<head>=0A <meta name=3D"Generator"= content=3D"Zarafa WebApp v7.1.10-44973">=0A <meta http-equiv=3D"Content= -Type" content=3D"text/html; charset=3Dutf-8">=0A <title>AW: [ovirt-user= s] Fake power management=3F</title>=0A</head>=0A<body>=0A<font face=3D"ta= homa" size=3D"2">Yes, pacemaker manages the engine. That part is working = fine, the engine restarts on the remaining node without problems. <br>It'= s just that the guests don't come back up until the powered down node has= been fenced manually.</font><br><pre style=3D"white-space: -moz-pre-wrap= ; white-space: -pre-wrap; white-space: -o-pre-wrap; white-space: pre-wrap= ; word-wrap: break-word;" wrap=3D"">-----Urspr=C3=BCngliche Nachricht----= -<br>> Von:Barak Azulay <<a href=3D"mailto:bazulay@redhat.com">bazu= lay@redhat.com</a>><br>> Gesendet: Mon 17 November 2014 11:35<br>&g= t; An: Patrick Lottenbach <<a href=3D"mailto:pl@a-bot.ch">pl@a-bot.ch<= /a>><br>> CC: <a href=3D"mailto:users@ovirt.org">users@ovirt.org</a= that they can show them our solutions.<br>> > Hardware: Two Intel = NUC's, a 4 port switch and a laptop.<br>> > Engine: Runs as a VM on= one of the NUCs, which one it runs on is determined<br>> > by pace= maker.<br>> > Storage: Also managed by pacemaker, it's drbd backed = and accessed with iscsi.<br>> > oVirt version: 3.5<br>> > OS:= CentOS 6.6<br>> > <br>> > The idea is to have our sales repr= esentative (or the potential customer<br>> > himself) randomly pull= the plug on one of the NUCs to show that the system<br>> > stays o= perational when part of the hardware fails.<br>> <br>> I assume you= are aware that the engine might fence the node it is running on ... <br>= > Or do you use pacemaker to run the engine as well =3F<br>> <br>&g= t; > My problem is that I don't have any way to implement power manage= ment, so the<br>> > Engine can't fence nodes and won't restart gues= ts that were running on the<br>> > node which lost power. In pacema= ker I can just configure fencing over SSH or<br>> > even disable th= e requirement to do so completely. Is there something similar<br>> >= ; for oVirt, so that the Engine will consider a node which it can't conne= ct to<br>> > to be powered down=3F<br>> > <br>> > Regar= ds,<br>> > <br>> > mots<br>> > <br>> > __________= _____________________________________<br>> > Users mailing list<br>= > > <a href=3D"mailto:Users@ovirt.org">Users@ovirt.org</a><br>> = > <a href=3D"http://lists.ovirt.org/mailman/listinfo/users" target=3D"= _blank">http://lists.ovirt.org/mailman/listinfo/users</a><br>>; > <b= r>> </pre>=0A</body>=0A</html> --=_cjtqlQp4QSYnJhuKs0Xg4VLTs9O15oco497qtVs9HKP3duB5-- ------=_Part_31_861888835.1416222010953 Content-Type: application/pgp-signature; name=signature.asc Content-Transfer-Encoding: 7bit Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: CIPHERMAIL (2.8.6-4) iQEcBAEBCAAGBQJUadU6AAoJELfzdzVzTtoKVGUH/2KQF6ZTNH7DpnXmG7K4wo9c nB924coImSQfGkFJjvIisRSG6vTnwk+z0uFjptulLl4o3NoPaDLs0IlvjpSvyGwf zFXLbOOls/SBVKOY5Nx7iAjEwIH4DXe06v2dYwJngQGnuyQv7pMDNUAz4uMXCup8 QjV39XbOYXQoLIfHUcGOJB824f2+LgRTrDr4HdZcyE0SHUfJaque3jdCDveXZFkB d0c0RKgB/r8wYBz+T7zIfutxtvKHYp1P5WmpbQ1J1Fr8XZKWgC7l3f7ubJyeldvK wyqZqokR+s1yptnUfLJUJEthnqFK0l+Fq2Vm9vuVpZsvwcn5QgQg+Kn1hmWCT7A= =qpmj -----END PGP SIGNATURE----- ------=_Part_31_861888835.1416222010953--