9:54 a.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--
10:15 a.m.
Il 14/11/2014 15:54, mots ha scritto:
Hello,
I'm building a small demonstration system for our sales team to take to a customer so
that they can show them our solutions.
Hardware: Two Intel NUC's, a 4 port switch and a laptop.
Engine: Runs as a VM on one of the NUCs, which one it runs on is determined by
pacemaker.
Storage: Also managed by pacemaker, it's drbd backed and accessed with iscsi.
oVirt version: 3.5
OS: CentOS 6.6
Just for curiosity, any reason for using pacemaker instead on oVirt Hosted Engine
solution?
The idea is to have our sales representative (or the potential customer himself) randomly
pull the plug on one of the NUCs to show that the system
stays operational when part of the hardware fails.
My problem is that 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 which lost power. In pacemaker I can just configure fencing over SSH or even
disable the requirement to do so completely. Is there something
similar for oVirt, so that the Engine will consider a node which it can't connect to
to be powered down?
Regards,
mots
_______________________________________________
Users mailing list
Users(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
--
Sandro Bonazzola
Better technology. Faster innovation. Powered by community collaboration.
See how it works at redhat.com
9:01 p.m.
----- Original Message -----
From: "Sandro Bonazzola" <sbonazzo(a)redhat.com>
To: "mots" <mots(a)nepu.moe>, users(a)ovirt.org
Sent: Friday, November 14, 2014 5:15:25 PM
Subject: Re: [ovirt-users] Fake power management?
Il 14/11/2014 15:54, mots ha scritto:
> Hello,
>
> I'm building a small demonstration system for our sales team to take to a
> customer so that they can show them our solutions.
> Hardware: Two Intel NUC's, a 4 port switch and a laptop.
> Engine: Runs as a VM on one of the NUCs, which one it runs on is determined
> by pacemaker.
> Storage: Also managed by pacemaker, it's drbd backed and accessed with
> iscsi.
> oVirt version: 3.5
> OS: CentOS 6.6
Just for curiosity, any reason for using pacemaker instead on oVirt Hosted
Engine solution?
>
> The idea is to have our sales representative (or the potential customer
> himself) randomly pull the plug on one of the NUCs to show that the system
> stays operational when part of the hardware fails.
> My problem is that 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 which lost power. In pacemaker I can just configure fencing over
> SSH or even disable the requirement to do so completely. Is there
> something
> similar for oVirt, so that the Engine will consider a node which it can't
> connect to to be powered down?
Well, we are thinking of adding such ability (Fake power management) mainly for testing
purpose...
Meanwhile, I think I have a work-around that may help you.
When we have a connectivity issue with a node, we first try (after a grace period) to
restart its VDSM via SSH
this is always done before the hard-fencing (restart via the PM card) and can be done no
matter if the host has PM configured or not.
So basically when a connectivity issue is found, you can custom the SSH command that
restarts VDSM to do whatever you want, even a script or a power-down command
look at the result of
psql -U engine -c "select * from vdc_options where option_name
ilike 'SshSoftFencingCommand'" engine
option_id | option_name | option_value | version
-----------+-----------------------+------------------------------------------+---------
558 | SshSoftFencingCommand | service vdsmd restart | 3.0
559 | SshSoftFencingCommand | service vdsmd restart | 3.1
560 | SshSoftFencingCommand | service vdsmd restart | 3.2
561 | SshSoftFencingCommand | /usr/bin/vdsm-tool service-restart vdsmd | 3.3
562 | SshSoftFencingCommand | /usr/bin/vdsm-tool service-restart vdsmd | 3.4
563 | SshSoftFencingCommand | /usr/bin/vdsm-tool service-restart vdsmd | 3.5
Please note:
1) change only the value that match your cluster version
2) restart engine so change can take place
3) restore to default value again after you are done
Does this may be useful for you ?
>
> Regards,
>
> mots
>
>
> _______________________________________________
> Users mailing list
> Users(a)ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>
--
Sandro Bonazzola
Better technology. Faster innovation. Powered by community collaboration.
See how it works at redhat.com
_______________________________________________
Users mailing list
Users(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
5:36 a.m.
----- Original Message -----
From: "mots" <mots(a)nepu.moe>
To: users(a)ovirt.org
Sent: Friday, November 14, 2014 4:54:08 PM
Subject: [ovirt-users] Fake power management?
Fake power management? Hello,
I'm building a small demonstration system for our sales team to take to a
customer so that they can show them our solutions.
Hardware: Two Intel NUC's, a 4 port switch and a laptop.
Engine: Runs as a VM on one of the NUCs, which one it runs on is determined
by pacemaker.
Storage: Also managed by pacemaker, it's drbd backed and accessed with iscsi.
oVirt version: 3.5
OS: CentOS 6.6
The idea is to have our sales representative (or the potential customer
himself) randomly pull the plug on one of the NUCs to show that the system
stays operational when part of the hardware fails.
I assume you are aware that the engine might fence the node it is running on ...
Or do you use pacemaker to run the engine as well ?
My problem is that 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 which lost power. In pacemaker I can just configure fencing over SSH or
even disable the requirement to do so completely. Is there something similar
for oVirt, so that the Engine will consider a node which it can't connect to
to be powered down?
Regards,
mots
_______________________________________________
Users mailing list
Users(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
3689
days inactive
3692
days old
3 comments
4 participants
participants (4)
-
Barak Azulay -
Eli Mesika -
mots -
Sandro Bonazzola