alternate method of fencing

------=_NextPart_000_001C_01D015FC.D2B58E00 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Is there a way to force oVirt to place a host into maintenance mode automatically when a problem occurs? The problem we have is separate networks for everything: 2 public nics which are bonded active/backup for internet access 4 bonded gigabit nics for our Gluster network 1 IPMI The ipmi is on a completely different network, not attached to anything else other than a VPN. /// Our cluster servers shared Gluster & hypervisor on the same hosts, which works great however, all are 1U servers so we don't have room for another NIC to dedicate to just an ipmi network connection in addition to the ipmi card itself. Even if the PSU on a host fails, then the ipmi power management is useless anyhow and the VM's on that host will not be moved. I've tested putting a host into maintenance mode with running VM's and it will auto-migrate the VM's without issue. Is there a way to make oVirt just force a host into maintenance mode if there's some sort of problem or some other fencing mechanism that will allow the VM's to be migrated to another host? ------=_NextPart_000_001C_01D015FC.D2B58E00 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable <html xmlns:v=3D"urn:schemas-microsoft-com:vml" = xmlns:o=3D"urn:schemas-microsoft-com:office:office" = xmlns:w=3D"urn:schemas-microsoft-com:office:word" = xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" = xmlns=3D"http://www.w3.org/TR/REC-html40"><head><meta = http-equiv=3DContent-Type content=3D"text/html; = charset=3Dus-ascii"><meta name=3DGenerator content=3D"Microsoft Word 15 = (filtered medium)"><style><!-- /* Font Definitions */ @font-face {font-family:"Cambria Math"; panose-1:2 4 5 3 5 4 6 3 2 4;} @font-face {font-family:Calibri; panose-1:2 15 5 2 2 2 4 3 2 4;} /* Style Definitions */ p.MsoNormal, li.MsoNormal, div.MsoNormal {margin:0in; margin-bottom:.0001pt; font-size:11.0pt; font-family:"Calibri",serif;} a:link, span.MsoHyperlink {mso-style-priority:99; color:#0563C1; text-decoration:underline;} a:visited, span.MsoHyperlinkFollowed {mso-style-priority:99; color:#954F72; text-decoration:underline;} span.EmailStyle17 {mso-style-type:personal-compose; font-family:"Calibri",serif; color:windowtext;} .MsoChpDefault {mso-style-type:export-only; font-family:"Calibri",serif;} @page WordSection1 {size:8.5in 11.0in; margin:1.0in 1.0in 1.0in 1.0in;} div.WordSection1 {page:WordSection1;} --></style><!--[if gte mso 9]><xml> <o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" /> </xml><![endif]--><!--[if gte mso 9]><xml> <o:shapelayout v:ext=3D"edit"> <o:idmap v:ext=3D"edit" data=3D"1" /> </o:shapelayout></xml><![endif]--></head><body lang=3DEN-US = link=3D"#0563C1" vlink=3D"#954F72"><div class=3DWordSection1><p = class=3DMsoNormal>Is there a way to force oVirt to place a host into = maintenance mode automatically when a problem occurs? The problem we = have is separate networks for everything:<o:p></o:p></p><p = class=3DMsoNormal><o:p> </o:p></p><p class=3DMsoNormal>2 public = nics which are bonded active/backup for internet access<o:p></o:p></p><p = class=3DMsoNormal>4 bonded gigabit nics for our Gluster = network<o:p></o:p></p><p class=3DMsoNormal>1 IPMI <o:p></o:p></p><p = class=3DMsoNormal><o:p> </o:p></p><p class=3DMsoNormal>The ipmi is = on a completely different network, not attached to anything else other = than a VPN. <o:p></o:p></p><p class=3DMsoNormal><o:p> </o:p></p><p = class=3DMsoNormal>///<o:p></o:p></p><p = class=3DMsoNormal><o:p> </o:p></p><p class=3DMsoNormal>Our cluster = servers shared Gluster & hypervisor on the same hosts, which works = great however, all are 1U servers so we don’t have room for = another NIC to dedicate to just an ipmi network connection in addition = to the ipmi card itself. Even if the PSU on a host fails, then the ipmi = power management is useless anyhow and the VM’s on that host will = not be moved.<o:p></o:p></p><p class=3DMsoNormal><o:p> </o:p></p><p = class=3DMsoNormal>I’ve tested putting a host into maintenance mode = with running VM’s and it will auto-migrate the VM’s without = issue. Is there a way to make oVirt just force a host into maintenance = mode if there’s some sort of problem or some other fencing = mechanism that will allow the VM’s to be migrated to another = host?<o:p></o:p></p><p class=3DMsoNormal><o:p> </o:p></p><p = class=3DMsoNormal><o:p> </o:p></p></div></body></html> ------=_NextPart_000_001C_01D015FC.D2B58E00--

----- Original Message -----
From: "Brent Hartzell" <brent.hartzell@outlook.com> To: users@ovirt.org Sent: Friday, December 12, 2014 6:14:40 PM Subject: [ovirt-users] alternate method of fencing
Is there a way to force oVirt to place a host into maintenance mode automatically when a problem occurs? The problem we have is separate networks for everything:
2 public nics which are bonded active/backup for internet access
4 bonded gigabit nics for our Gluster network
1 IPMI
The ipmi is on a completely different network, not attached to anything else other than a VPN.
///
Our cluster servers shared Gluster & hypervisor on the same hosts, which works great however, all are 1U servers so we don’t have room for another NIC to dedicate to just an ipmi network connection in addition to the ipmi card itself. Even if the PSU on a host fails, then the ipmi power management is useless anyhow and the VM’s on that host will not be moved.
I’ve tested putting a host into maintenance mode with running VM’s and it will auto-migrate the VM’s without issue. Is there a way to make oVirt just force a host into maintenance mode if there’s some sort of problem or some other fencing mechanism that will allow the VM’s to be migrated to another host?
I think this is a scheduling issue rather than fencing , please take a look at http://www.ovirt.org/Features/oVirtScheduler http://www.ovirt.org/Features/oVirtSchedulerAPI http://www.ovirt.org/Features/oVirt_External_Scheduling_Proxy
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
participants (2)
-
Brent Hartzell
-
Eli Mesika