Storage: Also managed by pacemaker, it's drbd backed and accessed w= ith=0D=0A> > > iscsi.=0D=0A> > > oVirt version: 3.5=0D=0A> > > OS: CentOS= 6.6=0D=0A> >=20=0D=0A> > Just for curiosity, any reason for using pacema= ker instead on oVirt Hosted=0D=0A> > Engine solution=3F=0D=0A> >=20=0D=0A= =20=0D=0A> > > The idea is to have our sales representative (or the =
------=_Part_28_89981195.1416135341935 Content-Type: multipart/alternative; boundary="=_198qEBTfpHVegONcN73CTkIZxTp38X1-UNdH8FALVPH+LZ7a" This is a multi-part message in MIME format. Your mail reader does not understand MIME message format. --=_198qEBTfpHVegONcN73CTkIZxTp38X1-UNdH8FALVPH+LZ7a Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Hello Eli,=0D=0A=0D=0AIf I replace "/usr/bin/vdsm-tool service-restart vd= smd" with "echo b > /proc/sysrc-trigger", will the Engine consider the no= de to be fenced and restart the VMs that were running on it on another no= de=3F I don't see a mechanism to inform the engine that this was a "hard"= fencing operation and that it's save to restart the guests.=0D=0A=20=0D=0A= Regards,=0D=0A=0D=0Amots=0D=0A=C2=A0=0D=0A-----Urspr=C3=BCngliche Nachric= ht-----=0D=0A> Von:Eli Mesika <emesika@redhat.com <mailto:emesika@redhat.= com> >=0D=0A> Gesendet: Son 16 November 2014 03:00=0D=0A> An: Patrick Lot= tenbach <pl@a-bot.ch <mailto:pl@a-bot.ch> >=0D=0A> CC: users@ovirt.org <m= ailto:users@ovirt.org>=20=0D=0A> Betreff: Re: [ovirt-users] Fake power ma= nagement=3F=0D=0A>=20=0D=0A>=20=0D=0A>=20=0D=0A> ----- Original Message -= ----=0D=0A> > From: "Sandro Bonazzola" <sbonazzo@redhat.com <mailto:sbona= zzo@redhat.com> >=0D=0A> > To: "mots" <mots@nepu.moe <mailto:mots@nepu.mo= e> >, users@ovirt.org <mailto:users@ovirt.org>=20=0D=0A> > Sent: Friday, = November 14, 2014 5:15:25 PM=0D=0A> > Subject: Re: [ovirt-users] Fake pow= er management=3F=0D=0A> >=20=0D=0A> > Il 14/11/2014 15:54, mots ha scritt= o:=0D=0A> > > Hello,=0D=0A> > >=20=0D=0A> > > I'm building a small demons= tration system for our sales team to take to a=0D=0A> > > customer so tha= t 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 pacemaker.=0D=0A= potential customer=0D=0A> > > himself) randomly pull the plug on one of t= he NUCs to show that the system=0D=0A> > > stays operational when part of= the hardware fails.=0D=0A> > > My problem is that I don't have any way t= o implement power management, so=0D=0A> > > the Engine can't fence nodes = and won't restart guests that were running on=0D=0A> > > the node which l= ost power. In pacemaker I can just configure fencing over=0D=0A> > > SSH = or even disable the requirement to do so completely. Is there=0D=0A> > > = something=0D=0A> > > similar for oVirt, so that the Engine will consider = a node which it can't=0D=0A> > > connect to to be powered down=3F=0D=0A>=20= =0D=0A> Well, we are thinking of adding such ability (Fake power manageme= nt) mainly for testing purpose...=0D=0A> Meanwhile, I think I have a work= -around that may help you.=0D=0A>=20=0D=0A> When we have a connectivity i= ssue with a node, we first try (after a grace period) to restart its VDSM= via SSH=20=0D=0A> this is always done before the hard-fencing (restart v= ia the PM card) and can be done no matter if the host has PM configured o= r not.=0D=0A> So basically when a connectivity issue is found, you can cu= stom the SSH command that restarts VDSM to do whatever you want, even a s= cript or a power-down command=20=0D=0A>=20=0D=0A> look at the result of=20= =0D=0A>=20=0D=0A> > psql -U engine -c "select * from vdc_options where o= ption_name ilike 'SshSoftFencingCommand'" engine=0D=0A>=20=0D=0A> optio= n_id | option_name | option_value |= version=0D=0A> -----------+-----------------------+---------------------= ---------------------+---------=0D=0A> 558 | SshSoftFencingCommand= | service vdsmd restart | 3.0=0D=0A> 559 | Ssh= SoftFencingCommand | service vdsmd restart | 3.1=0D=0A=
560 | SshSoftFencingCommand | service vdsmd restart =
| 3.2=0D=0A> 561 | SshSoftFencingCommand | /usr/bin/vdsm-to= ol service-restart vdsmd | 3.3=0D=0A> 562 | SshSoftFencingCommand = | /usr/bin/vdsm-tool service-restart vdsmd | 3.4=0D=0A> 563 | SshS= oftFencingCommand | /usr/bin/vdsm-tool service-restart vdsmd | 3.5=0D=0A>= =20=0D=0A>=20=0D=0A> Please note:=0D=0A>=20=0D=0A> 1) change only the val= ue that match your cluster version=0D=0A> 2) restart engine so change can= take place=20=0D=0A> 3) restore to default value again after you are don= e=20=0D=0A>=20=0D=0A> Does this may be useful for you =3F=0D=0A>=20=0D=0A=
=20=0D=0A>=20=0D=0A> > >=20=0D=0A> > > Regards,=0D=0A> > >=20=0D=0A> > >= mots=0D=0A> > >=20=0D=0A> > >=20=0D=0A> > > ____________________________= ___________________=0D=0A> > > Users mailing 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/listinfo/users>=20=0D=0A>=
=20=0D=0A> >=20=0D=0A> >=20=0D=0A> > --=0D=0A> > Sandro Bonazzola=0D=0A= Better technology. Faster innovation. Powered by community collaborat= ion.=0D=0A> > See how it works at redhat.com=0D=0A> > ___________________= ____________________________=0D=0A> > Users mailing list=0D=0A> > Users@o= virt.org <mailto:Users@ovirt.org>=20=0D=0A> > http://lists.ovirt.org/mail= man/listinfo/users <http://lists.ovirt.org/mailman/listinfo/users>=20=0D=0A= =20=0D=0A>=20=0D=0A=0D=0A --=_198qEBTfpHVegONcN73CTkIZxTp38X1-UNdH8FALVPH+LZ7a Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable
<br>If I replace "/usr/bin/vdsm-tool service-restart vdsmd" with "echo b= > /proc/sysrc-trigger", will the Engine consider the node to be fence= d and restart the VMs that were running on it on another node=3F I don't = see a mechanism to inform the engine that this was a "hard" fencing opera= tion and that it's save to restart the guests.<br> <br>Regards,<br><br>mo= ts<br> <br>-----Urspr=C3=BCngliche Nachricht-----<br>> Von:Eli Me= sika <<a href=3D"mailto:emesika@redhat.com">emesika@redhat.com</a>>= <br>> Gesendet: Son 16 November 2014 03:00<br>> An: Patrick Lottenb= ach <<a href=3D"mailto:pl@a-bot.ch">pl@a-bot.ch</a>><br>> CC: <a=
> > > I'm building a small demonstration system for our sales t= eam to take to a<br>> > > customer so that they can show them ou= r 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 pacemaker.<br>&g= t; > > Storage: Also managed by pacemaker, it's drbd backed and acc= essed with<br>> > > iscsi.<br>> > > oVirt version: 3.5<= br>> > > OS: CentOS 6.6<br>> > <br>> > Just for curi= osity, any reason for using pacemaker instead on oVirt Hosted<br>> >= ; Engine solution=3F<br>> > <br>> > > <br>> > > T= he idea is to have our sales representative (or the potential customer<br= > > > himself) randomly pull the plug on one of the NUCs to sho= w that the system<br>> > > stays operational when part of the ha= rdware fails.<br>> > > My problem is that I don't have any way t= o implement power management, so<br>> > > the Engine can't fence= nodes and won't restart guests that were running on<br>> > > th= e node which lost power. In pacemaker I can just configure fencing over<b= r>> > > SSH or even disable the requirement to do so completely.= Is there<br>> > > something<br>> > > similar for oVirt= , so that the Engine will consider a node which it can't<br>> > >= ; connect to to be powered down=3F<br>> <br>> Well, we are thinking= of adding such ability (Fake power management) mainly for testing purpos= e...<br>> Meanwhile, I think I have a work-around that may help you.<b= r>> <br>> When we have a connectivity issue with a node, we first t= ry (after a grace period) to restart its VDSM via SSH <br>> this is al= ways done before the hard-fencing (restart via the PM card) and can be do= ne no matter if the host has PM configured or not.<br>> So basically w= hen a connectivity issue is found, you can custom the SSH command that re= starts VDSM to do whatever you want, even a script or a power-down comman= d <br>> <br>> look at the result of <br>> <br>> > psql -U = engine -c "select * from vdc_options where option_name ilike 'SshSoftFe= ncingCommand'" engine<br>> <br>> option_id | option_name = | option_value | version<br>> -----------= +-----------------------+------------------------------------------+-----= ----<br>> 558 | SshSoftFencingCommand | service vdsmd restart = | 3.0<br>> 559 | SshSoftFencingCommand | serv= ice vdsmd restart | 3.1<br>> 560 | SshSoftFe= ncingCommand | service vdsmd restart | 3.2<br>> = 561 | SshSoftFencingCommand | /usr/bin/vdsm-tool service-restart vdsm= d | 3.3<br>> 562 | SshSoftFencingCommand | /usr/bin/vdsm-tool s= ervice-restart vdsmd | 3.4<br>> 563 | SshSoftFencingCommand | /= usr/bin/vdsm-tool service-restart vdsmd | 3.5<br>> <br>> <br>> P= lease note:<br>> <br>> 1) change only the value that match your clu= ster version<br>> 2) restart engine so change can take place <br>> =
<!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<pre style=3D"wh= ite-space: -moz-pre-wrap; white-space: -pre-wrap; white-space: -o-pre-wra= p; white-space: pre-wrap; word-wrap: break-word;" wrap=3D"">Hello Eli,<br= href=3D"mailto:users@ovirt.org">users@ovirt.org</a><br>> Betreff: Re:= [ovirt-users] Fake power management=3F<br>> <br>> <br>> <br>>= ; ----- Original Message -----<br>> > From: "Sandro Bonazzola" <= <a href=3D"mailto:sbonazzo@redhat.com">sbonazzo@redhat.com</a>><br>>= ; > To: "mots" <<a href=3D"mailto:mots@nepu.moe">mots@nepu.moe</a>&= gt;, <a href=3D"mailto:users@ovirt.org">users@ovirt.org</a><br>> > = Sent: Friday, November 14, 2014 5:15:25 PM<br>> > Subject: Re: [ovi= rt-users] Fake power management=3F<br>> > <br>> > Il 14/11/20= 14 15:54, mots ha scritto:<br>> > > Hello,<br>> > > <br= 3) restore to default value again after you are done <br>> <br>> Do= es this may be useful for you =3F<br>> <br>> <br>> <br>> >= > <br>> > > Regards,<br>> > > <br>> > > mo= ts<br>> > > <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>&= gt; > > <br>> > <br>> > <br>> > --<br>> > S= andro Bonazzola<br>> > Better technology. Faster innovation. Powere= d by community collaboration.<br>> > See how it works at redhat.com= <br>> > _______________________________________________<br>> >= ; Users mailing list<br>> > <a href=3D"mailto:Users@ovirt.org">User= s@ovirt.org</a><br>> > <a href=3D"http://lists.ovirt.org/mailman/li= stinfo/users" target=3D"_blank">http://lists.ovirt.org/mailman/listinfo/u= sers</a><br>> > <br>> </pre>=0A</body>=0A</html> --=_198qEBTfpHVegONcN73CTkIZxTp38X1-UNdH8FALVPH+LZ7a--
------=_Part_28_89981195.1416135341935 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) iQEcBAEBCAAGBQJUaIKtAAoJELfzdzVzTtoKz3QH/iNvmHQV9aJIwJTQDetgWXhU ju72gR6a4CLyEQdx8hNSwpgxtVHibFTmkkiIR5usnRGAFRfI+hSmZ95qDKgV3BLw pZjRrZd+ryMkrn5D4RocJlX9DO0BfE+9vmfEnmSd579DTwZMPQUUWn20hck8yO+1 crKj096PBx0wCf5i9XTymCx/Zx96SFiLllFyn7z/zEUtlNsLk405iI6PWKfYrv8H kj5Q0Jn9fB1DyN9vROJOS7Mrrl149/MNMv4zRZFOE5yLffZfXEJe6WaGVEfhJkq7 kmv4Z+x/2H/FqzY3dpwxGycpsvPkl+jeVYoG1wZCVxQKTto3FAmsO396/L5awkE= =1WB6 -----END PGP SIGNATURE----- ------=_Part_28_89981195.1416135341935--