5:25 p.m.
------=_Part_25_1292789217.1415978809325
Content-Type: multipart/alternative;
boundary="=_dXxpYi2sBaXuAWm3Y3JSB1BPzr10m4FTrJP1udtOi1Yk-tQt"
This is a multi-part message in MIME format. Your mail reader does not
understand MIME message format.
--=_dXxpYi2sBaXuAWm3Y3JSB1BPzr10m4FTrJP1udtOi1Yk-tQt
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Well, I haven't found a way to make sure the Engines storage comes up bef=
ore the Engine is attemting to start.=0D=0A=0D=0A=0D=0A=20=0D=0A-----Ursp=
r=C3=BCngliche Nachricht-----=0D=0A> Von:Sandro Bonazzola <sbonazzo@redha=
t.com <mailto:sbonazzo@redhat.com> >=0D=0A> Gesendet: Fre 14 November 201=
4 16:13=0D=0A> An: Patrick Lottenbach <pl(a)a-bot.ch <mailto:pl@a-bot.ch> >=
; users(a)ovirt.org <mailto:users@ovirt.org>=20=0D=0A> Betreff: Re: [ovirt-=
users] Fake power management=3F=0D=0A>=20=0D=0A> Il 14/11/2014 15:54, mot=
s ha scritto:=0D=0A> > Hello,=0D=0A> >=20=0D=0A> > I'm building a
small d=
emonstration system for our sales team to take to a customer so that they=
can show them our solutions.=0D=0A> > Hardware: Two Intel NUC's, a 4 por=
t switch and a laptop.=0D=0A> > Engine: Runs as a VM on one of the NUCs, =
which one it runs on is determined by pacemaker.=0D=0A> > Storage: Also m=
anaged by pacemaker, it's drbd backed and accessed with iscsi.=0D=0A> > o=
Virt version: 3.5=0D=0A> > OS: CentOS 6.6=0D=0A>=20=0D=0A> Just for curio=
sity, any reason for using pacemaker instead on oVirt Hosted Engine solut=
ion=3F=0D=0A>=20=0D=0A> >=20=0D=0A> > The idea is to have our sales repre=
sentative (or the potential customer himself) randomly pull the plug on o=
ne of the NUCs to show that the system=0D=0A> > stays operational when pa=
rt of the hardware fails.=0D=0A> > My problem is that I don't have any wa=
y to implement power management, so the Engine can't fence nodes and won'=
t restart guests that were running on=0D=0A> > the node which lost power.=
In pacemaker I can just configure fencing over SSH or even disable the r=
equirement to do so completely. Is there something=0D=0A> > similar for o=
Virt, so that the Engine will consider a node which it can't connect to t=
o be powered down=3F=0D=0A> >=20=0D=0A> > Regards,=0D=0A> >=20=0D=0A>
> m=
ots=0D=0A> >=20=0D=0A> >=20=0D=0A> >
____________________________________=
___________=0D=0A> > Users mailing list=0D=0A> > Users(a)ovirt.org <mailto:=
Users(a)ovirt.org>=20=0D=0A> > http://lists.ovirt.org/mailman/listinfo/user=
s <http://lists.ovirt.org/mailman/listinfo/users>=20=0D=0A>
>=20=0D=0A>=20=
=0D=0A>=20=0D=0A> --=20=0D=0A> Sandro Bonazzola=0D=0A> Better technology.=
Faster innovation. Powered by community collaboration.=0D=0A> See how it=
works at redhat.com=0D=0A>=20=0D=0A=0D=0A
--=_dXxpYi2sBaXuAWm3Y3JSB1BPzr10m4FTrJP1udtOi1Yk-tQt
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>AW: [ovirt-users] Fake power
management=3F</title>=0D=0A</head>=0D=0A<b=
ody>=0D=0A<font face=3D"tahoma" size=3D"2">Well, I
haven't found a way to=
make sure the Engines storage comes up before the Engine is attemting to=
start.</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: br=
eak-word;" wrap=3D""><br> <br>-----Urspr=C3=BCngliche
Nachricht-----<br>&=
gt; Von:Sandro Bonazzola <<a
href=3D"mailto:sbonazzo@redhat.com">sbona=
zzo(a)redhat.com</a>&gt;<br>&gt; Gesendet: Fre 14 November 2014
16:13<br>&g=
t; An: Patrick Lottenbach <<a
href=3D"mailto:pl@a-bot.ch">pl@a-bot.ch<=
/a>>; <a
href=3D"mailto:users@ovirt.org">users@ovirt.org</a><br>>
B=
etreff: Re: [ovirt-users] Fake power management=3F<br>> <br>> Il
14=
/11/2014 15:54, mots ha scritto:<br>> > Hello,<br>>
> <br>>=
; > I'm building a small demonstration system for our sales team to ta=
ke to a customer so that they can show them our solutions.<br>> > H=
ardware: Two Intel NUC's, a 4 port switch and a laptop.<br>> >
Engi=
ne: Runs as a VM on one of the NUCs, which one it runs on is determined b=
y pacemaker.<br>> > Storage: Also managed by pacemaker, it's drbd
b=
acked and accessed with iscsi.<br>> > oVirt version:
3.5<br>> &g=
t; OS: CentOS 6.6<br>> <br>> Just for curiosity, any reason for
usi=
ng pacemaker instead on oVirt Hosted Engine solution=3F<br>>
<br>> =
> <br>> > The idea is to have our sales representative (or the
p=
otential customer himself) randomly pull the plug on one of the NUCs to s=
how that the system<br>> > stays operational when part of the hardw=
are fails.<br>> > My problem is that I don't have any way to
implem=
ent power management, so the Engine can't fence nodes and won't restart g=
uests that were running on<br>> > the node which lost power. In pac=
emaker I can just configure fencing over SSH or even disable the requirem=
ent to do so completely. Is there something<br>> > similar for oVir=
t, so that the Engine will consider a node which it can't connect to to b=
e powered down=3F<br>> > <br>> >
Regards,<br>> > <br>&g=
t; > mots<br>> > <br>> > <br>>
> ___________________=
____________________________<br>> > Users mailing
list<br>> >=
<a
href=3D"mailto:Users@ovirt.org">Users@ovirt.org</a><br>>
> <a h=
ref=3D"http://lists.ovirt.org/mailman/listinfo/users"
target=3D"_blank">h=
ttp://lists.ovirt.org/mailman/listinfo/users</a><br>> >
<br>> <b=
r>> <br>> -- <br>> Sandro Bonazzola<br>>
Better technology. F=
aster innovation. Powered by community collaboration.<br>> See how it =
works at redhat.com<br>> </pre>=0D=0A</body>=0D=0A</html>
--=_dXxpYi2sBaXuAWm3Y3JSB1BPzr10m4FTrJP1udtOi1Yk-tQt--
------=_Part_25_1292789217.1415978809325
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)
iQEcBAEBCAAGBQJUZh85AAoJELfzdzVzTtoKW3wH/R4ghG+gWyYIx7/wKIf3mp0y
ltsqd2tbMzxPocCpG+Ri2iZ7TueFK+FNYcj7XMOQ3ZoJT/5S0ubDisqEm42Zomu/
FgAtXL4eIKIlKotKf90aQhMD12JHJstAEqsN8QmIh1QOiCRDLgpSlGR17M4aWoxk
IBhD29EdguDaZ2PW4EvwmCRZNTDWzk3TAgtSiERuxU+A+NKbji2idxoR6I92rN8I
q/80dXdbUPVQuOLg9QF+v/NTT+vyB67HY+vJyMV7qMHWk5H6s8eH6DwkCPgNGDAM
TDuqMfZ9nT1KDKaDkfST6xyhXmHYrPPmf/UnQEW0pkpduAAxXgS+XLHOtwm05ss=
=IvGN
-----END PGP SIGNATURE-----
------=_Part_25_1292789217.1415978809325--
3661
days inactive
3661
days old
0 comments
1 participants
participants (1)
-
mots