4:54 p.m.
------=_Part_24_2062496813.1415976955949
Content-Type: multipart/alternative;
boundary="=_guxpNXeBU0NQ8OsPUiLb8M5NU4xt8e7pVmeTMitrhXCFoJlJ"
This is a multi-part message in MIME format. Your mail reader does not
understand MIME message format.
--=_guxpNXeBU0NQ8OsPUiLb8M5NU4xt8e7pVmeTMitrhXCFoJlJ
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Hello,=0D=0A=0D=0AI'm building a small demonstration system for our sales=
team to take to a customer so that they can show them our solutions.=20=0D=
=0AHardware: Two Intel NUC's, a 4 port switch and a laptop.=0D=0AEngine: =
Runs as a VM on one of the NUCs, which one it runs on is determined by pa=
cemaker.=0D=0AStorage: Also managed by pacemaker, it's drbd backed and ac=
cessed with iscsi.=0D=0AoVirt version: 3.5=0D=0AOS: CentOS 6.6=0D=0A=0D=0A=
The idea is to have our sales representative (or the potential customer h=
imself) randomly pull the plug on one of the NUCs to show that the system=
stays operational when part of the hardware fails.=0D=0AMy problem is th=
at I don't have any way to implement power management, so the Engine can'=
t fence nodes and won't restart guests that were running on the node whic=
h lost power. In pacemaker I can just configure fencing over SSH or even =
disable the requirement to do so completely. Is there something similar f=
or oVirt, so that the Engine will consider a node which it can't connect =
to to be powered down=3F=0D=0A=0D=0ARegards,=0D=0A=0D=0Amots=0D=0A
--=_guxpNXeBU0NQ8OsPUiLb8M5NU4xt8e7pVmeTMitrhXCFoJlJ
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: quoted-printable
=0D=0A<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"htt=
p://www.w3.org/TR/html4/loose.dtd"><html>=0D=0A<head>... <meta
name=3D=
"Generator" content=3D"Zarafa WebApp v7.1.10-44973">=0D=0A
<meta http-eq=
uiv=3D"Content-Type" content=3D"text/html; charset=3Dutf-8">=0D=0A
<titl=
e>Fake power
management=3F</title>=0D=0A</head>=0D=0A<body>=0D=0A<font fa=
ce=3D"tahoma" size=3D"2">Hello,<br><br>I'm building
a small demonstration=
system for our sales team to take to a customer so that they can show th=
em our solutions. <br>Hardware: Two Intel NUC's, a 4 port switch and a la=
ptop.<br>Engine: Runs as a VM on one of the NUCs, which one it runs on is=
determined by pacemaker.<br>Storage: Also managed by pacemaker, it's drb=
d backed and accessed with iscsi.<br>oVirt version: 3.5<br>OS: CentOS 6.6=
<br><br>The idea is to have our sales representative (or the potential cu=
stomer himself) randomly pull the plug on one of the NUCs to show that th=
e system stays operational when part of the hardware fails.<br>My problem=
is that I don't have any way to implement power management, so the Engin=
e can't fence nodes and won't restart guests that were running on the nod=
e which lost power. In pacemaker I can just configure fencing over SSH or=
even disable the requirement to do so completely. Is there something sim=
ilar for oVirt, so that the Engine will consider a node which it can't co=
nnect to to be powered
down=3F<br><br>Regards,<br><br>mots<br></font>=0D=0A=
</body>=0D=0A</html>
--=_guxpNXeBU0NQ8OsPUiLb8M5NU4xt8e7pVmeTMitrhXCFoJlJ--
------=_Part_24_2062496813.1415976955949
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)
iQEcBAEBCAAGBQJUZhf7AAoJELfzdzVzTtoK5+gH/0ImEE6PmTvdHBYohT3KcdGc
5k4nCOYW/lZxVmT6w15Dkd0xMm/5v7BX52sn6GyXxq5JYbzRaz+wEz5WaTJma46N
R9Rd659xWJz6gofjsGZRLzRM0/RLSiX65l0s1XzBlsmwtx2S9yVK0liSKJSeQEiV
9y9sTQj9HHTg3abyPYGWr86VNtUCwTYY6Ln1i/FxvSeJi/C3Ltlc27BBOHc1anrn
fXBdLZCm5WZxpw3Np1mWqWKEN+8ZF+P88PhdJBBY2TljpPcpyCbVdzaKwyrZ7ZNV
rmCjpMN72dpvbhTM7fUjiF+/LFB0yAnt1RGcEcBXlLR7OnKaYuuvIME0FU7r/Bg=
=OgRe
-----END PGP SIGNATURE-----
------=_Part_24_2062496813.1415976955949--