
On 07/30/2012 08:56 AM, Karli Sj=F6berg wrote:<br></blockquote></blockquot= e><blockquote type=3D"cite"><blockquote type=3D"cite"><blockquote type=3D"c= ite"><br></blockquote></blockquote></blockquote><blockquote type=3D"cite"><=
</blockquote></blockquote></blockquote></blockquote><blockquote type=3D"ci= te"><blockquote type=3D"cite"><blockquote type=3D"cite"><blockquote type=3D= "cite"><blockquote type=3D"cite">hostC<br></blockquote></blockquote></block= quote></blockquote></blockquote><blockquote type=3D"cite"><blockquote type= =3D"cite"><blockquote type=3D"cite"><blockquote type=3D"cite"><blockquote t= ype=3D"cite"><br></blockquote></blockquote></blockquote></blockquote></bloc= kquote><blockquote type=3D"cite"><blockquote type=3D"cite"><blockquote type= =3D"cite"><blockquote type=3D"cite"><blockquote type=3D"cite">I want a way = to force only to use hostA as a proxy for power commands.<br></blockquote><= /blockquote></blockquote></blockquote></blockquote><blockquote type=3D"cite= "><blockquote type=3D"cite"><blockquote type=3D"cite"><blockquote type=3D"c= ite"><br></blockquote></blockquote></blockquote></blockquote><blockquote ty=
<blockquote type=3D"cite">from<br></blockquote></blockquote></blockquote><= /blockquote><blockquote type=3D"cite"><blockquote type=3D"cite"><blockquote= type=3D"cite"><blockquote type=3D"cite">ovirt-engine/backend/manager/modul= es/bll/src/main/java/org/ovirt/engine/core/bll/FencingExecutor.java<br></bl= ockquote></blockquote></blockquote></blockquote><blockquote type=3D"cite"><=
--_000_B3844C3FAAB14C54AEA5A34ACFE02BDDsluse_ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable 30 jul 2012 kl. 12.26 skrev Itamar Heim: On 07/30/2012 12:03 PM, Karli Sj=F6berg wrote: 30 jul 2012 kl. 11.01 skrev Itamar Heim: On 07/30/2012 08:56 AM, Karli Sj=F6berg wrote: 28 jul 2012 kl. 14.11 skrev Moti Asayag: On 07/26/2012 02:53 PM, Karli Sj=F6berg wrote: Hi, In my DC, I have three hosts added: hostA hostB hostC I want a way to force only to use hostA as a proxy for power commands. The algorithm of selection a host to act as a proxy for PM commands is quite naive: any host from the system with status UP. You can see how it is being selected in FencingExecutor.FindVdsToFence() from ovirt-engine/backend/manager/modules/bll/src/main/java/org/ovirt/engine/cor= e/bll/FencingExecutor.java There is no other algorithm for the selection at the moment. How would you handle a case in which hostA isn't responsive ? Wouldn't you prefer trying to perform the fencing using other available host ? Let me explain a little to make you better understand my reasoning behind this configuration. We work with segmented, separated networks. One network for public access, one for storage traffic, one for management and so on. That means that if the nodes themselves have to do their own power-management, the nodes would require three interfaces each, and the metal we are using for hosts just don=B4t have that. But if we can use the engine to do that, the hosts would only require two interfaces, which most 1U servers are equipped with as standard (plus one iLO/IPMI/whatev), so we can use them as hosts without issue. Then the backend has one extra interface that it can use to communicate over the power management network to the respective service processor with. Is there a "better" way to achieve what we are aiming for? Ideally, I would like to set up the two NICs in a bond and create VLAN-interfaces on top of that bond. That way, I can have as many virtual interfaces as I want without having more than two physical NICs, but I haven=B4t been able to find a good HOWTO explaining the process. I think there is a difference between: 1. allowing engine to fence 2. allowing to choose fencing host per cluster (or per host) it sounds like you actually want #1, but can live with #2, by installing the engine as a host as well. Exactly, I can live with #2, as I have the engine added as hostA in my DC well, the question is if choosing another host to use for fencing would/should be limited to hosts from same DC, then engine can only be used to fence one DC. I=B4m quoting you here: "1. power management is DC wide, not cluster." So this wouldn=B4t be any different from it=B4s current state. also, for any host other than engine, question is what to do if it is down... Med V=E4nliga H=E4lsningar ---------------------------------------------------------------------------= ---- Karli Sj=F6berg Swedish University of Agricultural Sciences Box 7079 (Visiting Address Kron=E5sv=E4gen 8) S-750 07 Uppsala, Sweden Phone: +46-(0)18-67 15 66 karli.sjoberg@slu.se<mailto:karli.sjoberg@adm.slu.se> --_000_B3844C3FAAB14C54AEA5A34ACFE02BDDsluse_ Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable <html><head></head><body style=3D"word-wrap: break-word; -webkit-nbsp-mode:= space; -webkit-line-break: after-white-space; "><br><div><div>30 jul 2012 = kl. 12.26 skrev Itamar Heim:</div><br class=3D"Apple-interchange-newline"><= blockquote type=3D"cite"><div>On 07/30/2012 12:03 PM, Karli Sj=F6berg wrote= :<br><blockquote type=3D"cite"><br></blockquote><blockquote type=3D"cite">3= 0 jul 2012 kl. 11.01 skrev Itamar Heim:<br></blockquote><blockquote type=3D= "cite"><br></blockquote><blockquote type=3D"cite"><blockquote type=3D"cite"= blockquote type=3D"cite"><blockquote type=3D"cite">28 jul 2012 kl. 14.11 sk= rev Moti Asayag:<br></blockquote></blockquote></blockquote><blockquote type= =3D"cite"><blockquote type=3D"cite"><blockquote type=3D"cite"><br></blockqu= ote></blockquote></blockquote><blockquote type=3D"cite"><blockquote type=3D= "cite"><blockquote type=3D"cite"><blockquote type=3D"cite">On 07/26/2012 02= :53 PM, Karli Sj=F6berg wrote:<br></blockquote></blockquote></blockquote></= blockquote><blockquote type=3D"cite"><blockquote type=3D"cite"><blockquote = type=3D"cite"><blockquote type=3D"cite"><blockquote type=3D"cite">Hi,<br></= blockquote></blockquote></blockquote></blockquote></blockquote><blockquote = type=3D"cite"><blockquote type=3D"cite"><blockquote type=3D"cite"><blockquo= te type=3D"cite"><blockquote type=3D"cite"><br></blockquote></blockquote></= blockquote></blockquote></blockquote><blockquote type=3D"cite"><blockquote = type=3D"cite"><blockquote type=3D"cite"><blockquote type=3D"cite"><blockquo= te type=3D"cite">In my DC, I have three hosts added:<br></blockquote></bloc= kquote></blockquote></blockquote></blockquote><blockquote type=3D"cite"><bl= ockquote type=3D"cite"><blockquote type=3D"cite"><blockquote type=3D"cite">= <blockquote type=3D"cite"><br></blockquote></blockquote></blockquote></bloc= kquote></blockquote><blockquote type=3D"cite"><blockquote type=3D"cite"><bl= ockquote type=3D"cite"><blockquote type=3D"cite"><blockquote type=3D"cite">= hostA<br></blockquote></blockquote></blockquote></blockquote></blockquote><= blockquote type=3D"cite"><blockquote type=3D"cite"><blockquote type=3D"cite= "><blockquote type=3D"cite"><blockquote type=3D"cite">hostB<br></blockquote= pe=3D"cite"><blockquote type=3D"cite"><blockquote type=3D"cite"><blockquote= type=3D"cite">The algorithm of selection a host to act as a proxy for PM c= ommands is<br></blockquote></blockquote></blockquote></blockquote><blockquo= te type=3D"cite"><blockquote type=3D"cite"><blockquote type=3D"cite"><block= quote type=3D"cite">quite naive: any host from the system with status UP.<b= r></blockquote></blockquote></blockquote></blockquote><blockquote type=3D"c= ite"><blockquote type=3D"cite"><blockquote type=3D"cite"><blockquote type= =3D"cite"><br></blockquote></blockquote></blockquote></blockquote><blockquo= te type=3D"cite"><blockquote type=3D"cite"><blockquote type=3D"cite"><block= quote type=3D"cite">You can see how it is being selected in FencingExecutor= .FindVdsToFence()<br></blockquote></blockquote></blockquote></blockquote><b= lockquote type=3D"cite"><blockquote type=3D"cite"><blockquote type=3D"cite"= blockquote type=3D"cite"><blockquote type=3D"cite"><blockquote type=3D"cite= "><br></blockquote></blockquote></blockquote></blockquote><blockquote type= =3D"cite"><blockquote type=3D"cite"><blockquote type=3D"cite"><blockquote t= ype=3D"cite">There is no other algorithm for the selection at the moment.<b= r></blockquote></blockquote></blockquote></blockquote><blockquote type=3D"c= ite"><blockquote type=3D"cite"><blockquote type=3D"cite"><blockquote type= =3D"cite"><br></blockquote></blockquote></blockquote></blockquote><blockquo= te type=3D"cite"><blockquote type=3D"cite"><blockquote type=3D"cite"><block= quote type=3D"cite">How would you handle a case in which hostA isn't respon= sive ? Wouldn't<br></blockquote></blockquote></blockquote></blockquote><blo= ckquote type=3D"cite"><blockquote type=3D"cite"><blockquote type=3D"cite"><= blockquote type=3D"cite">you prefer trying to perform the fencing using oth= er available host ?<br></blockquote></blockquote></blockquote></blockquote>= <blockquote type=3D"cite"><blockquote type=3D"cite"><blockquote type=3D"cit= e"><br></blockquote></blockquote></blockquote><blockquote type=3D"cite"><bl= ockquote type=3D"cite"><blockquote type=3D"cite"><br></blockquote></blockqu= ote></blockquote><blockquote type=3D"cite"><blockquote type=3D"cite"><block= quote type=3D"cite">Let me explain a little to make you better understand m= y reasoning<br></blockquote></blockquote></blockquote><blockquote type=3D"c= ite"><blockquote type=3D"cite"><blockquote type=3D"cite">behind this config= uration.<br></blockquote></blockquote></blockquote><blockquote type=3D"cite= "><blockquote type=3D"cite"><blockquote type=3D"cite"><br></blockquote></bl= ockquote></blockquote><blockquote type=3D"cite"><blockquote type=3D"cite"><= blockquote type=3D"cite">We work with segmented, separated networks. One ne= twork for public<br></blockquote></blockquote></blockquote><blockquote type= =3D"cite"><blockquote type=3D"cite"><blockquote type=3D"cite">access, one f= or storage traffic, one for management and so on. That<br></blockquote></bl= ockquote></blockquote><blockquote type=3D"cite"><blockquote type=3D"cite"><= blockquote type=3D"cite">means that if the nodes themselves have to do thei= r own<br></blockquote></blockquote></blockquote><blockquote type=3D"cite"><= blockquote type=3D"cite"><blockquote type=3D"cite">power-management, the no= des would require three interfaces each, and the<br></blockquote></blockquo= te></blockquote><blockquote type=3D"cite"><blockquote type=3D"cite"><blockq= uote type=3D"cite">metal we are using for hosts just don=B4t have that. But= if we can use the<br></blockquote></blockquote></blockquote><blockquote ty= pe=3D"cite"><blockquote type=3D"cite"><blockquote type=3D"cite">engine to d= o that, the hosts would only require two interfaces, which<br></blockquote>= </blockquote></blockquote><blockquote type=3D"cite"><blockquote type=3D"cit= e"><blockquote type=3D"cite">most 1U servers are equipped with as standard = (plus one<br></blockquote></blockquote></blockquote><blockquote type=3D"cit= e"><blockquote type=3D"cite"><blockquote type=3D"cite">iLO/IPMI/whatev), so= we can use them as hosts without issue. Then the<br></blockquote></blockqu= ote></blockquote><blockquote type=3D"cite"><blockquote type=3D"cite"><block= quote type=3D"cite">backend has one extra interface that it can use to comm= unicate over the<br></blockquote></blockquote></blockquote><blockquote type= =3D"cite"><blockquote type=3D"cite"><blockquote type=3D"cite">power managem= ent network to the respective service processor with.<br></blockquote></blo= ckquote></blockquote><blockquote type=3D"cite"><blockquote type=3D"cite"><b= lockquote type=3D"cite"><br></blockquote></blockquote></blockquote><blockqu= ote type=3D"cite"><blockquote type=3D"cite"><blockquote type=3D"cite">Is th= ere a "better" way to achieve what we are aiming for? Ideally, I<br></block= quote></blockquote></blockquote><blockquote type=3D"cite"><blockquote type= =3D"cite"><blockquote type=3D"cite">would like to set up the two NICs in a = bond and create VLAN-interfaces<br></blockquote></blockquote></blockquote><= blockquote type=3D"cite"><blockquote type=3D"cite"><blockquote type=3D"cite= ">on top of that bond. That way, I can have as many virtual interfaces as<b= r></blockquote></blockquote></blockquote><blockquote type=3D"cite"><blockqu= ote type=3D"cite"><blockquote type=3D"cite">I want without having more than= two physical NICs, but I haven=B4t been<br></blockquote></blockquote></blo= ckquote><blockquote type=3D"cite"><blockquote type=3D"cite"><blockquote typ= e=3D"cite">able to find a good HOWTO explaining the process.<br></blockquot= e></blockquote></blockquote><blockquote type=3D"cite"><blockquote type=3D"c= ite"><blockquote type=3D"cite"><br></blockquote></blockquote></blockquote><= blockquote type=3D"cite"><blockquote type=3D"cite"><br></blockquote></block= quote><blockquote type=3D"cite"><blockquote type=3D"cite">I think there is = a difference between:<br></blockquote></blockquote><blockquote type=3D"cite= "><blockquote type=3D"cite">1. allowing engine to fence<br></blockquote></b= lockquote><blockquote type=3D"cite"><blockquote type=3D"cite">2. allowing t= o choose fencing host per cluster (or per host)<br></blockquote></blockquot= e><blockquote type=3D"cite"><blockquote type=3D"cite"><br></blockquote></bl= ockquote><blockquote type=3D"cite"><blockquote type=3D"cite">it sounds like= you actually want #1, but can live with #2, by installing<br></blockquote>= </blockquote><blockquote type=3D"cite"><blockquote type=3D"cite">the engine= as a host as well.<br></blockquote></blockquote><blockquote type=3D"cite">= <br></blockquote><blockquote type=3D"cite">Exactly, I can live with #2, as = I have the engine added as hostA in my DC<br></blockquote><br>well, the que= stion is if choosing another host to use for fencing <br>would/should be li= mited to hosts from same DC, then engine can only be <br>used to fence one = DC.<br></div></blockquote><div><br></div>I=B4m quoting you here:</div><div>= "1. power management is DC wide, not cluster."</div><div><br></div><div>So = this wouldn=B4t be any different from it=B4s current state.</div><div><br><= /div><div><br><blockquote type=3D"cite"><div>also, for any host other than = engine, question is what to do if it is <br>down...<br></div></blockquote><= /div><br><div> <span class=3D"Apple-style-span" style=3D"border-collapse: separate; color:= rgb(0, 0, 0); font-family: Helvetica; font-style: normal; font-variant: no= rmal; font-weight: normal; letter-spacing: normal; line-height: normal; orp= hans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; = white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizonta= l-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorati= ons-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-wi= dth: 0px; font-size: medium; "><div><br class=3D"Apple-interchange-newline"=
<br></div><div>Med V=E4nliga H=E4lsningar<br>-----------------------------= --------------------------------------------------<br>Karli Sj=F6berg<br>Sw= edish University of Agricultural Sciences<br>Box 7079 (Visiting Address Kro= n=E5sv=E4gen 8)<br>S-750 07 Uppsala, Sweden<br>Phone: +46-(0)18-67 15= 66</div><div><a href=3D"mailto:karli.sjoberg@adm.slu.se">karli.sjoberg@slu= .se</a></div></span> </div> <br></body></html>=
--_000_B3844C3FAAB14C54AEA5A34ACFE02BDDsluse_--