[Users] Ovirt Node Automated Installation... full unattended installation?
This is a multi-part message in MIME format. ------=_NextPart_000_0004_01CE0180.E6D73BF0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Ok, reading the RHEV-H node automated installation, given the oVirt documentation states the same automated installation parameters are supported, I can't see to resolve one key issue. First boot of PXE configuration does an 'uninstall' to ensure no past installation of oVirt node exists. this works 100% unattended. However using install or reinstall or local_boot (a.k.a. upgrade) or even firstboot option, and even no option, on the APPEND command line via PXE, the automated installation stops. Waiting for interactive response? Is this the expected behavior? Even just using init_storage and BOOTIF, the only two required parameters, the automated process stops for interactive input? So how do you do a completely automated installation with zero human interactive action required? Uninstall. This works as expected. KERNEL images/oVirt/2.5.5-0.1/vmlinuz0 APPEND rootflags=loop initrd=images/oVirt/2.5.5-0.1/initrd0.img root=live:/ovirt-node-iso-2.5.5-0.1.fc17.iso rootfstype=auto ro liveimg check rootflags=ro crashkernel=512M-2G:64M,2G-:128M elevator=deadline uninstall Install. This does not work as expected, per how the documentation implies it should? KERNEL images/oVirt/2.5.5-0.1/vmlinuz0 APPEND rootflags=loop initrd=images/oVirt/2.5.5-0.1/initrd0.img root=live:/ovirt-node-iso-2.5.5-0.1.fc17.iso rootfstype=auto ro liveimg check rootflags=ro crashkernel=512M-2G:64M,2G-:128M elevator=deadline rd_NO_LVM rd.luks=0 rd.md=0 rd.dm=0 storage_init=/dev/sda BOOTIF=<FF:FF:FF:FF:FF:FF> ------=_NextPart_000_0004_01CE0180.E6D73BF0 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 12 = (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","sans-serif";} a:link, span.MsoHyperlink {mso-style-priority:99; color:blue; text-decoration:underline;} a:visited, span.MsoHyperlinkFollowed {mso-style-priority:99; color:purple; text-decoration:underline;} span.EmailStyle17 {mso-style-type:personal-compose; font-family:"Calibri","sans-serif"; color:windowtext;} .MsoChpDefault {mso-style-type:export-only; font-size:10.0pt;} @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=3Dblue = vlink=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal>Ok, = reading the RHEV-H node automated installation, given the oVirt = documentation states the same automated installation parameters are = supported, I can’t see to resolve one key = issue…<o:p></o:p></p><p class=3DMsoNormal><o:p> </o:p></p><p = class=3DMsoNormal>First boot of PXE configuration does an = ‘uninstall’ to ensure no past installation of oVirt node = exists… this works 100% unattended. However using install or = reinstall or local_boot (a.k.a. upgrade) or even firstboot option, and = even no option, on the APPEND command line via PXE, the automated = installation stops. Waiting for interactive response? Is = this the expected behavior? Even just using init_storage and = BOOTIF, the only two required parameters, the automated process stops = for interactive input? So how do you do a completely automated = installation with zero human interactive action = required?<o:p></o:p></p><p class=3DMsoNormal><o:p> </o:p></p><p = class=3DMsoNormal>Uninstall… This works as = expected…<o:p></o:p></p><p = class=3DMsoNormal><o:p> </o:p></p><p class=3DMsoNormal>KERNEL = images/oVirt/2.5.5-0.1/vmlinuz0<o:p></o:p></p><p = class=3DMsoNormal>APPEND rootflags=3Dloop = initrd=3Dimages/oVirt/2.5.5-0.1/initrd0.img = root=3Dlive:/ovirt-node-iso-2.5.5-0.1.fc17.iso rootfstype=3Dauto ro = liveimg check rootflags=3Dro crashkernel=3D512M-2G:64M,2G-:128M = elevator=3Ddeadline uninstall<o:p></o:p></p><p = class=3DMsoNormal><o:p> </o:p></p><p = class=3DMsoNormal>Install… This does not work as expected, = per how the documentation implies it should?<o:p></o:p></p><p = class=3DMsoNormal><o:p> </o:p></p><p class=3DMsoNormal>KERNEL = images/oVirt/2.5.5-0.1/vmlinuz0<o:p></o:p></p><p = class=3DMsoNormal>APPEND rootflags=3Dloop = initrd=3Dimages/oVirt/2.5.5-0.1/initrd0.img = root=3Dlive:/ovirt-node-iso-2.5.5-0.1.fc17.iso rootfstype=3Dauto ro = liveimg check rootflags=3Dro crashkernel=3D512M-2G:64M,2G-:128M = elevator=3Ddeadline rd_NO_LVM rd.luks=3D0 rd.md=3D0 rd.dm=3D0 = storage_init=3D/dev/sda = BOOTIF=3D<FF:FF:FF:FF:FF:FF><o:p></o:p></p><p = class=3DMsoNormal><o:p> </o:p></p></div></body></html> ------=_NextPart_000_0004_01CE0180.E6D73BF0--
This is a multi-part message in MIME format. ------=_NextPart_000_000F_01CE0184.1BA349C0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit The plot thickens. I removed BOOTIF and used IPAPPEND 2 directive which per the documentation does automatic append of BOOTIF parameter using the MAC of the adapter that PXE used, and received the DHCPOFFER. then the automated installation worked as the documentation suggests. Does this make sense, or is this some type of odd quirk or bug? Does not work. (FF:FF:FF:FF:FF:FF is not the real MAC used, just redacted the real MAC). KERNEL images/oVirt/2.5.5-0.1/vmlinuz0 APPEND rootflags=loop initrd=images/oVirt/2.5.5-0.1/initrd0.img root=live:/ovirt-node-iso-2.5.5-0.1.fc17.iso rootfstype=auto ro liveimg check rootflags=ro crashkernel=512M-2G:64M,2G-:128M elevator=deadline rd_NO_LVM rd.luks=0 rd.md=0 rd.dm=0 storage_init=/dev/sda BOOTIF=<FF:FF:FF:FF:FF:FF> Works. KERNEL images/oVirt/2.5.5-0.1/vmlinuz0 IPAPPEND 2 APPEND rootflags=loop initrd=images/oVirt/2.5.5-0.1/initrd0.img root=live:/ovirt-node-iso-2.5.5-0.1.fc17.iso rootfstype=auto ro liveimg check rootflags=ro crashkernel=512M-2G:64M,2G-:128M elevator=deadline rd_NO_LVM rd.luks=0 rd.md=0 rd.dm=0 storage_init=/dev/sda From: users-bounces@ovirt.org [mailto:users-bounces@ovirt.org] On Behalf Of Schorschi Sent: Saturday, February 02, 2013 20:07 To: users@ovirt.org Subject: [Users] Ovirt Node Automated Installation... full unattended installation? Ok, reading the RHEV-H node automated installation, given the oVirt documentation states the same automated installation parameters are supported, I can't see to resolve one key issue. First boot of PXE configuration does an 'uninstall' to ensure no past installation of oVirt node exists. this works 100% unattended. However using install or reinstall or local_boot (a.k.a. upgrade) or even firstboot option, and even no option, on the APPEND command line via PXE, the automated installation stops. Waiting for interactive response? Is this the expected behavior? Even just using init_storage and BOOTIF, the only two required parameters, the automated process stops for interactive input? So how do you do a completely automated installation with zero human interactive action required? Uninstall. This works as expected. KERNEL images/oVirt/2.5.5-0.1/vmlinuz0 APPEND rootflags=loop initrd=images/oVirt/2.5.5-0.1/initrd0.img root=live:/ovirt-node-iso-2.5.5-0.1.fc17.iso rootfstype=auto ro liveimg check rootflags=ro crashkernel=512M-2G:64M,2G-:128M elevator=deadline uninstall Install. This does not work as expected, per how the documentation implies it should? KERNEL images/oVirt/2.5.5-0.1/vmlinuz0 APPEND rootflags=loop initrd=images/oVirt/2.5.5-0.1/initrd0.img root=live:/ovirt-node-iso-2.5.5-0.1.fc17.iso rootfstype=auto ro liveimg check rootflags=ro crashkernel=512M-2G:64M,2G-:128M elevator=deadline rd_NO_LVM rd.luks=0 rd.md=0 rd.dm=0 storage_init=/dev/sda BOOTIF=<FF:FF:FF:FF:FF:FF> ------=_NextPart_000_000F_01CE0184.1BA349C0 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 12 = (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;} @font-face {font-family:Tahoma; panose-1:2 11 6 4 3 5 4 4 2 4;} /* Style Definitions */ p.MsoNormal, li.MsoNormal, div.MsoNormal {margin:0in; margin-bottom:.0001pt; font-size:11.0pt; font-family:"Calibri","sans-serif";} a:link, span.MsoHyperlink {mso-style-priority:99; color:blue; text-decoration:underline;} a:visited, span.MsoHyperlinkFollowed {mso-style-priority:99; color:purple; text-decoration:underline;} span.EmailStyle17 {mso-style-type:personal; font-family:"Calibri","sans-serif"; color:windowtext;} span.EmailStyle18 {mso-style-type:personal-reply; font-family:"Calibri","sans-serif"; color:#1F497D;} .MsoChpDefault {mso-style-type:export-only; font-size:10.0pt;} @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=3Dblue = vlink=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal><span = style=3D'color:#1F497D'>The plot thickens… I removed BOOTIF = and used IPAPPEND 2 directive which per the documentation does automatic = append of BOOTIF parameter using the MAC of the adapter that PXE used, = and received the DHCPOFFER… then the automated installation worked = as the documentation suggests. Does this make sense, or is this = some type of odd quirk or bug?<o:p></o:p></span></p><p = class=3DMsoNormal><span = style=3D'color:#1F497D'><o:p> </o:p></span></p><p = class=3DMsoNormal><span style=3D'color:#1F497D'>Does not work… = (FF:FF:FF:FF:FF:FF is not the real MAC used, just redacted the real = MAC)…<o:p></o:p></span></p><p class=3DMsoNormal><span = style=3D'color:#1F497D'><o:p> </o:p></span></p><p = class=3DMsoNormal>KERNEL = images/oVirt/2.5.5-0.1/vmlinuz0<o:p></o:p></p><p = class=3DMsoNormal>APPEND rootflags=3Dloop = initrd=3Dimages/oVirt/2.5.5-0.1/initrd0.img = root=3Dlive:/ovirt-node-iso-2.5.5-0.1.fc17.iso rootfstype=3Dauto ro = liveimg check rootflags=3Dro crashkernel=3D512M-2G:64M,2G-:128M = elevator=3Ddeadline rd_NO_LVM rd.luks=3D0 rd.md=3D0 rd.dm=3D0 = storage_init=3D/dev/sda = BOOTIF=3D<FF:FF:FF:FF:FF:FF><o:p></o:p></p><p = class=3DMsoNormal><span = style=3D'color:#1F497D'><o:p> </o:p></span></p><p = class=3DMsoNormal><span = style=3D'color:#1F497D'>Works…<o:p></o:p></span></p><p = class=3DMsoNormal><span = style=3D'color:#1F497D'><o:p> </o:p></span></p><p = class=3DMsoNormal><span style=3D'color:#1F497D'>KERNEL = images/oVirt/2.5.5-0.1/vmlinuz0<o:p></o:p></span></p><p = class=3DMsoNormal><span style=3D'color:#1F497D'>IPAPPEND = 2<o:p></o:p></span></p><p class=3DMsoNormal><span = style=3D'color:#1F497D'>APPEND rootflags=3Dloop = initrd=3Dimages/oVirt/2.5.5-0.1/initrd0.img = root=3Dlive:/ovirt-node-iso-2.5.5-0.1.fc17.iso rootfstype=3Dauto ro = liveimg check rootflags=3Dro crashkernel=3D512M-2G:64M,2G-:128M = elevator=3Ddeadline rd_NO_LVM rd.luks=3D0 rd.md=3D0 rd.dm=3D0 = storage_init=3D/dev/sda<o:p></o:p></span></p><p class=3DMsoNormal><span = style=3D'color:#1F497D'><o:p> </o:p></span></p><p = class=3DMsoNormal><span = style=3D'color:#1F497D'><o:p> </o:p></span></p><p = class=3DMsoNormal><span = style=3D'color:#1F497D'><o:p> </o:p></span></p><div><div = style=3D'border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in = 0in 0in'><p class=3DMsoNormal><b><span = style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span>= </b><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> = users-bounces@ovirt.org [mailto:users-bounces@ovirt.org] <b>On Behalf Of = </b>Schorschi<br><b>Sent:</b> Saturday, February 02, 2013 = 20:07<br><b>To:</b> users@ovirt.org<br><b>Subject:</b> [Users] Ovirt = Node Automated Installation... full unattended = installation?<o:p></o:p></span></p></div></div><p = class=3DMsoNormal><o:p> </o:p></p><p class=3DMsoNormal>Ok, reading = the RHEV-H node automated installation, given the oVirt documentation = states the same automated installation parameters are supported, I = can’t see to resolve one key issue…<o:p></o:p></p><p = class=3DMsoNormal><o:p> </o:p></p><p class=3DMsoNormal>First = boot of PXE configuration does an ‘uninstall’ to = ensure no past installation of oVirt node exists… this works 100% = unattended. However using install or reinstall or local_boot = (a.k.a. upgrade) or even firstboot option, and even no option, on the = APPEND command line via PXE, the automated installation stops. = Waiting for interactive response? Is this the expected = behavior? Even just using init_storage and BOOTIF, the only two = required parameters, the automated process stops for interactive = input? So how do you do a completely automated installation with = zero human interactive action required?<o:p></o:p></p><p = class=3DMsoNormal><o:p> </o:p></p><p = class=3DMsoNormal>Uninstall… This works as = expected…<o:p></o:p></p><p = class=3DMsoNormal><o:p> </o:p></p><p class=3DMsoNormal>KERNEL = images/oVirt/2.5.5-0.1/vmlinuz0<o:p></o:p></p><p = class=3DMsoNormal>APPEND rootflags=3Dloop = initrd=3Dimages/oVirt/2.5.5-0.1/initrd0.img = root=3Dlive:/ovirt-node-iso-2.5.5-0.1.fc17.iso rootfstype=3Dauto ro = liveimg check rootflags=3Dro crashkernel=3D512M-2G:64M,2G-:128M = elevator=3Ddeadline uninstall<o:p></o:p></p><p = class=3DMsoNormal><o:p> </o:p></p><p = class=3DMsoNormal>Install… This does not work as expected, = per how the documentation implies it should?<o:p></o:p></p><p = class=3DMsoNormal><o:p> </o:p></p><p class=3DMsoNormal>KERNEL = images/oVirt/2.5.5-0.1/vmlinuz0<o:p></o:p></p><p = class=3DMsoNormal>APPEND rootflags=3Dloop = initrd=3Dimages/oVirt/2.5.5-0.1/initrd0.img = root=3Dlive:/ovirt-node-iso-2.5.5-0.1.fc17.iso rootfstype=3Dauto ro = liveimg check rootflags=3Dro crashkernel=3D512M-2G:64M,2G-:128M = elevator=3Ddeadline rd_NO_LVM rd.luks=3D0 rd.md=3D0 rd.dm=3D0 = storage_init=3D/dev/sda = BOOTIF=3D<FF:FF:FF:FF:FF:FF><o:p></o:p></p><p = class=3DMsoNormal><o:p> </o:p></p></div></body></html> ------=_NextPart_000_000F_01CE0184.1BA349C0--
The plot thickens… I removed BOOTIF and used IPAPPEND 2 directive which per the documentation does automatic append of BOOTIF parameter using the MAC of the adapter that PXE used, and received the DHCPOFFER… then the automated installation worked as the documentation suggests.
Can you provide the docs link please? Tim Hildred, RHCE Content Author II - Engineering Content Services, Red Hat, Inc. Brisbane, Australia Email: thildred@redhat.com Internal: 8588287 Mobile: +61 4 666 25242 IRC: thildred ----- Original Message -----
From: "No Reply" <no-reply@dc.rr.com> To: users@ovirt.org Sent: Sunday, February 3, 2013 2:30:14 PM Subject: Re: [Users] Ovirt Node Automated Installation... full unattended installation?
The plot thickens… I removed BOOTIF and used IPAPPEND 2 directive which per the documentation does automatic append of BOOTIF parameter using the MAC of the adapter that PXE used, and received the DHCPOFFER… then the automated installation worked as the documentation suggests. Does this make sense, or is this some type of odd quirk or bug?
Does not work… (FF:FF:FF:FF:FF:FF is not the real MAC used, just redacted the real MAC)…
KERNEL images/oVirt/2.5.5-0.1/vmlinuz0
APPEND rootflags=loop initrd=images/oVirt/2.5.5-0.1/initrd0.img root=live:/ovirt-node-iso-2.5.5-0.1.fc17.iso rootfstype=auto ro liveimg check rootflags=ro crashkernel=512M-2G:64M,2G-:128M elevator=deadline rd_NO_LVM rd.luks=0 rd.md=0 rd.dm=0 storage_init=/dev/sda BOOTIF=<FF:FF:FF:FF:FF:FF>
Works…
KERNEL images/oVirt/2.5.5-0.1/vmlinuz0
IPAPPEND 2
APPEND rootflags=loop initrd=images/oVirt/2.5.5-0.1/initrd0.img root=live:/ovirt-node-iso-2.5.5-0.1.fc17.iso rootfstype=auto ro liveimg check rootflags=ro crashkernel=512M-2G:64M,2G-:128M elevator=deadline rd_NO_LVM rd.luks=0 rd.md=0 rd.dm=0 storage_init=/dev/sda
From: users-bounces@ovirt.org [mailto:users-bounces@ovirt.org] On Behalf Of Schorschi Sent: Saturday, February 02, 2013 20:07 To: users@ovirt.org Subject: [Users] Ovirt Node Automated Installation... full unattended installation?
Ok, reading the RHEV-H node automated installation, given the oVirt documentation states the same automated installation parameters are supported, I can’t see to resolve one key issue…
First boot of PXE configuration does an ‘uninstall’ to ensure no past installation of oVirt node exists… this works 100% unattended. However using install or reinstall or local_boot (a.k.a. upgrade) or even firstboot option, and even no option, on the APPEND command line via PXE, the automated installation stops. Waiting for interactive response? Is this the expected behavior? Even just using init_storage and BOOTIF, the only two required parameters, the automated process stops for interactive input? So how do you do a completely automated installation with zero human interactive action required?
Uninstall… This works as expected…
KERNEL images/oVirt/2.5.5-0.1/vmlinuz0
APPEND rootflags=loop initrd=images/oVirt/2.5.5-0.1/initrd0.img root=live:/ovirt-node-iso-2.5.5-0.1.fc17.iso rootfstype=auto ro liveimg check rootflags=ro crashkernel=512M-2G:64M,2G-:128M elevator=deadline uninstall
Install… This does not work as expected, per how the documentation implies it should?
KERNEL images/oVirt/2.5.5-0.1/vmlinuz0
APPEND rootflags=loop initrd=images/oVirt/2.5.5-0.1/initrd0.img root=live:/ovirt-node-iso-2.5.5-0.1.fc17.iso rootfstype=auto ro liveimg check rootflags=ro crashkernel=512M-2G:64M,2G-:128M elevator=deadline rd_NO_LVM rd.luks=0 rd.md=0 rd.dm=0 storage_init=/dev/sda BOOTIF=<FF:FF:FF:FF:FF:FF>
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
] <b>On Behalf Of </b>Schorschi<br><b>Sent:</b> Saturday, February 02, = 2013 20:07<br><b>To:</b> <a =
This is a multi-part message in MIME format. ------=_NextPart_000_0077_01CE03BA.2E3EA1A0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit No comments? J This has to be an important feature of oVirt no? From: users-bounces@ovirt.org [mailto:users-bounces@ovirt.org] On Behalf Of No Reply Sent: Saturday, February 02, 2013 20:30 To: users@ovirt.org Subject: Re: [Users] Ovirt Node Automated Installation... full unattended installation? The plot thickens. I removed BOOTIF and used IPAPPEND 2 directive which per the documentation does automatic append of BOOTIF parameter using the MAC of the adapter that PXE used, and received the DHCPOFFER. then the automated installation worked as the documentation suggests. Does this make sense, or is this some type of odd quirk or bug? Does not work. (FF:FF:FF:FF:FF:FF is not the real MAC used, just redacted the real MAC). KERNEL images/oVirt/2.5.5-0.1/vmlinuz0 APPEND rootflags=loop initrd=images/oVirt/2.5.5-0.1/initrd0.img root=live:/ovirt-node-iso-2.5.5-0.1.fc17.iso rootfstype=auto ro liveimg check rootflags=ro crashkernel=512M-2G:64M,2G-:128M elevator=deadline rd_NO_LVM rd.luks=0 rd.md=0 rd.dm=0 storage_init=/dev/sda BOOTIF=<FF:FF:FF:FF:FF:FF> Works. KERNEL images/oVirt/2.5.5-0.1/vmlinuz0 IPAPPEND 2 APPEND rootflags=loop initrd=images/oVirt/2.5.5-0.1/initrd0.img root=live:/ovirt-node-iso-2.5.5-0.1.fc17.iso rootfstype=auto ro liveimg check rootflags=ro crashkernel=512M-2G:64M,2G-:128M elevator=deadline rd_NO_LVM rd.luks=0 rd.md=0 rd.dm=0 storage_init=/dev/sda From: users-bounces@ovirt.org [mailto:users-bounces@ovirt.org] On Behalf Of Schorschi Sent: Saturday, February 02, 2013 20:07 To: users@ovirt.org Subject: [Users] Ovirt Node Automated Installation... full unattended installation? Ok, reading the RHEV-H node automated installation, given the oVirt documentation states the same automated installation parameters are supported, I can't see to resolve one key issue. First boot of PXE configuration does an 'uninstall' to ensure no past installation of oVirt node exists. this works 100% unattended. However using install or reinstall or local_boot (a.k.a. upgrade) or even firstboot option, and even no option, on the APPEND command line via PXE, the automated installation stops. Waiting for interactive response? Is this the expected behavior? Even just using init_storage and BOOTIF, the only two required parameters, the automated process stops for interactive input? So how do you do a completely automated installation with zero human interactive action required? Uninstall. This works as expected. KERNEL images/oVirt/2.5.5-0.1/vmlinuz0 APPEND rootflags=loop initrd=images/oVirt/2.5.5-0.1/initrd0.img root=live:/ovirt-node-iso-2.5.5-0.1.fc17.iso rootfstype=auto ro liveimg check rootflags=ro crashkernel=512M-2G:64M,2G-:128M elevator=deadline uninstall Install. This does not work as expected, per how the documentation implies it should? KERNEL images/oVirt/2.5.5-0.1/vmlinuz0 APPEND rootflags=loop initrd=images/oVirt/2.5.5-0.1/initrd0.img root=live:/ovirt-node-iso-2.5.5-0.1.fc17.iso rootfstype=auto ro liveimg check rootflags=ro crashkernel=512M-2G:64M,2G-:128M elevator=deadline rd_NO_LVM rd.luks=0 rd.md=0 rd.dm=0 storage_init=/dev/sda BOOTIF=<FF:FF:FF:FF:FF:FF> ------=_NextPart_000_0077_01CE03BA.2E3EA1A0 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=3D"Content-Type" CONTENT=3D"text/html; = charset=3Dus-ascii"><meta name=3DGenerator content=3D"Microsoft Word 12 = (filtered medium)"><style><!-- /* Font Definitions */ @font-face {font-family:Wingdings; panose-1:5 0 0 0 0 0 0 0 0 0;} @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;} @font-face {font-family:Tahoma; panose-1:2 11 6 4 3 5 4 4 2 4;} /* Style Definitions */ p.MsoNormal, li.MsoNormal, div.MsoNormal {margin:0in; margin-bottom:.0001pt; font-size:11.0pt; font-family:"Calibri","sans-serif";} a:link, span.MsoHyperlink {mso-style-priority:99; color:blue; text-decoration:underline;} a:visited, span.MsoHyperlinkFollowed {mso-style-priority:99; color:purple; text-decoration:underline;} p.MsoAcetate, li.MsoAcetate, div.MsoAcetate {mso-style-priority:99; mso-style-link:"Balloon Text Char"; margin:0in; margin-bottom:.0001pt; font-size:8.0pt; font-family:"Tahoma","sans-serif";} span.EmailStyle17 {mso-style-type:personal; font-family:"Calibri","sans-serif"; color:windowtext;} span.EmailStyle18 {mso-style-type:personal; font-family:"Calibri","sans-serif"; color:#1F497D;} span.BalloonTextChar {mso-style-name:"Balloon Text Char"; mso-style-priority:99; mso-style-link:"Balloon Text"; font-family:"Tahoma","sans-serif";} span.EmailStyle21 {mso-style-type:personal-reply; font-family:"Calibri","sans-serif"; color:#1F497D;} .MsoChpDefault {mso-style-type:export-only; font-size:10.0pt;} @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=3Dblue = vlink=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal><span = style=3D'color:#1F497D'>No comments? </span><span = style=3D'font-family:Wingdings;color:#1F497D'>J</span><span = style=3D'color:#1F497D'> This has to be an important feature of = oVirt no?<o:p></o:p></span></p><p class=3DMsoNormal><span = style=3D'color:#1F497D'><o:p> </o:p></span></p><div><div = style=3D'border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in = 0in 0in'><p class=3DMsoNormal><b><span = style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span>= </b><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> = users-bounces@ovirt.org [mailto:users-bounces@ovirt.org] <b>On Behalf Of = </b>No Reply<br><b>Sent:</b> Saturday, February 02, 2013 = 20:30<br><b>To:</b> users@ovirt.org<br><b>Subject:</b> Re: [Users] Ovirt = Node Automated Installation... full unattended = installation?<o:p></o:p></span></p></div></div><p = class=3DMsoNormal><o:p> </o:p></p><p class=3DMsoNormal><span = style=3D'color:#1F497D'>The plot thickens… I removed BOOTIF = and used IPAPPEND 2 directive which per the documentation does automatic = append of BOOTIF parameter using the MAC of the adapter that PXE used, = and received the DHCPOFFER… then the automated installation worked = as the documentation suggests. Does this make sense, or is this = some type of odd quirk or bug?<o:p></o:p></span></p><p = class=3DMsoNormal><span = style=3D'color:#1F497D'><o:p> </o:p></span></p><p = class=3DMsoNormal><span style=3D'color:#1F497D'>Does not work… = (FF:FF:FF:FF:FF:FF is not the real MAC used, just redacted the real = MAC)…<o:p></o:p></span></p><p class=3DMsoNormal><span = style=3D'color:#1F497D'><o:p> </o:p></span></p><p = class=3DMsoNormal>KERNEL = images/oVirt/2.5.5-0.1/vmlinuz0<o:p></o:p></p><p = class=3DMsoNormal>APPEND rootflags=3Dloop = initrd=3Dimages/oVirt/2.5.5-0.1/initrd0.img = root=3Dlive:/ovirt-node-iso-2.5.5-0.1.fc17.iso rootfstype=3Dauto ro = liveimg check rootflags=3Dro crashkernel=3D512M-2G:64M,2G-:128M = elevator=3Ddeadline rd_NO_LVM rd.luks=3D0 rd.md=3D0 rd.dm=3D0 = storage_init=3D/dev/sda = BOOTIF=3D<FF:FF:FF:FF:FF:FF><o:p></o:p></p><p = class=3DMsoNormal><span = style=3D'color:#1F497D'><o:p> </o:p></span></p><p = class=3DMsoNormal><span = style=3D'color:#1F497D'>Works…<o:p></o:p></span></p><p = class=3DMsoNormal><span = style=3D'color:#1F497D'><o:p> </o:p></span></p><p = class=3DMsoNormal><span style=3D'color:#1F497D'>KERNEL = images/oVirt/2.5.5-0.1/vmlinuz0<o:p></o:p></span></p><p = class=3DMsoNormal><span style=3D'color:#1F497D'>IPAPPEND = 2<o:p></o:p></span></p><p class=3DMsoNormal><span = style=3D'color:#1F497D'>APPEND rootflags=3Dloop = initrd=3Dimages/oVirt/2.5.5-0.1/initrd0.img = root=3Dlive:/ovirt-node-iso-2.5.5-0.1.fc17.iso rootfstype=3Dauto ro = liveimg check rootflags=3Dro crashkernel=3D512M-2G:64M,2G-:128M = elevator=3Ddeadline rd_NO_LVM rd.luks=3D0 rd.md=3D0 rd.dm=3D0 = storage_init=3D/dev/sda<o:p></o:p></span></p><p class=3DMsoNormal><span = style=3D'color:#1F497D'><o:p> </o:p></span></p><p = class=3DMsoNormal><span = style=3D'color:#1F497D'><o:p> </o:p></span></p><p = class=3DMsoNormal><span = style=3D'color:#1F497D'><o:p> </o:p></span></p><div><div = style=3D'border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in = 0in 0in'><p class=3DMsoNormal><b><span = style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span>= </b><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> = <a href=3D"mailto:users-bounces@ovirt.org">users-bounces@ovirt.org</a> = [<a = href=3D"mailto:users-bounces@ovirt.org">mailto:users-bounces@ovirt.org</a= href=3D"mailto:users@ovirt.org">users@ovirt.org</a><br><b>Subject:</b> = [Users] Ovirt Node Automated Installation... full unattended = installation?<o:p></o:p></span></p></div></div><p = class=3DMsoNormal><o:p> </o:p></p><p class=3DMsoNormal>Ok, reading = the RHEV-H node automated installation, given the oVirt documentation = states the same automated installation parameters are supported, I = can’t see to resolve one key issue…<o:p></o:p></p><p = class=3DMsoNormal><o:p> </o:p></p><p class=3DMsoNormal>First = boot of PXE configuration does an ‘uninstall’ to = ensure no past installation of oVirt node exists… this works 100% = unattended. However using install or reinstall or local_boot = (a.k.a. upgrade) or even firstboot option, and even no option, on the = APPEND command line via PXE, the automated installation stops. = Waiting for interactive response? Is this the expected = behavior? Even just using init_storage and BOOTIF, the only two = required parameters, the automated process stops for interactive = input? So how do you do a completely automated installation with = zero human interactive action required?<o:p></o:p></p><p = class=3DMsoNormal><o:p> </o:p></p><p = class=3DMsoNormal>Uninstall… This works as = expected…<o:p></o:p></p><p = class=3DMsoNormal><o:p> </o:p></p><p class=3DMsoNormal>KERNEL = images/oVirt/2.5.5-0.1/vmlinuz0<o:p></o:p></p><p = class=3DMsoNormal>APPEND rootflags=3Dloop = initrd=3Dimages/oVirt/2.5.5-0.1/initrd0.img = root=3Dlive:/ovirt-node-iso-2.5.5-0.1.fc17.iso rootfstype=3Dauto ro = liveimg check rootflags=3Dro crashkernel=3D512M-2G:64M,2G-:128M = elevator=3Ddeadline uninstall<o:p></o:p></p><p = class=3DMsoNormal><o:p> </o:p></p><p = class=3DMsoNormal>Install… This does not work as expected, = per how the documentation implies it should?<o:p></o:p></p><p = class=3DMsoNormal><o:p> </o:p></p><p class=3DMsoNormal>KERNEL = images/oVirt/2.5.5-0.1/vmlinuz0<o:p></o:p></p><p = class=3DMsoNormal>APPEND rootflags=3Dloop = initrd=3Dimages/oVirt/2.5.5-0.1/initrd0.img = root=3Dlive:/ovirt-node-iso-2.5.5-0.1.fc17.iso rootfstype=3Dauto ro = liveimg check rootflags=3Dro crashkernel=3D512M-2G:64M,2G-:128M = elevator=3Ddeadline rd_NO_LVM rd.luks=3D0 rd.md=3D0 rd.dm=3D0 = storage_init=3D/dev/sda = BOOTIF=3D<FF:FF:FF:FF:FF:FF><o:p></o:p></p><p = class=3DMsoNormal><o:p> </o:p></p></div></body></html> ------=_NextPart_000_0077_01CE03BA.2E3EA1A0--
--=-sdXd90bCEO73avACzFJ0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Am Dienstag, den 05.02.2013, 16:02 -0800 schrieb No Reply:
No comments? J This has to be an important feature of oVirt no?
Hey, does it basically work - e.g. when booting from USB - when you add the BOOTIF=3Deth0 storage_init parameters? So using a device name instead of a mac address? Greetings fabian
From: users-bounces@ovirt.org [mailto:users-bounces@ovirt.org] On Behalf Of No Reply Sent: Saturday, February 02, 2013 20:30 To: users@ovirt.org Subject: Re: [Users] Ovirt Node Automated Installation... full unattended installation? =20 =20 =20 =20 The plot thickens=E2=80=A6 I removed BOOTIF and used IPAPPEND 2 directiv= e which per the documentation does automatic append of BOOTIF parameter using the MAC of the adapter that PXE used, and received the DHCPOFFER=E2=80=A6 then the automated installation worked as the document= ation suggests. Does this make sense, or is this some type of odd quirk or bug? =20 =20 =20 Does not work=E2=80=A6 (FF:FF:FF:FF:FF:FF is not the real MAC used, just redacted the real MAC)=E2=80=A6 =20 =20 =20 KERNEL images/oVirt/2.5.5-0.1/vmlinuz0 =20 APPEND rootflags=3Dloop initrd=3Dimages/oVirt/2.5.5-0.1/initrd0.img root=3Dlive:/ovirt-node-iso-2.5.5-0.1.fc17.iso rootfstype=3Dauto ro liveimg check rootflags=3Dro crashkernel=3D512M-2G:64M,2G-:128M elevator=3Ddeadline rd_NO_LVM rd.luks=3D0 rd.md=3D0 rd.dm=3D0 storage_init=3D/dev/sda BOOTIF=3D<FF:FF:FF:FF:FF:FF> =20 =20 =20 Works=E2=80=A6 =20 =20 =20 KERNEL images/oVirt/2.5.5-0.1/vmlinuz0 =20 IPAPPEND 2 =20 APPEND rootflags=3Dloop initrd=3Dimages/oVirt/2.5.5-0.1/initrd0.img root=3Dlive:/ovirt-node-iso-2.5.5-0.1.fc17.iso rootfstype=3Dauto ro liveimg check rootflags=3Dro crashkernel=3D512M-2G:64M,2G-:128M elevator=3Ddeadline rd_NO_LVM rd.luks=3D0 rd.md=3D0 rd.dm=3D0 storage_init=3D/dev/sda =20 =20 =20 =20 =20 =20 =20 From: users-bounces@ovirt.org [mailto:users-bounces@ovirt.org] On Behalf Of Schorschi Sent: Saturday, February 02, 2013 20:07 To: users@ovirt.org Subject: [Users] Ovirt Node Automated Installation... full unattended installation? =20 =20 =20 =20 Ok, reading the RHEV-H node automated installation, given the oVirt documentation states the same automated installation parameters are supported, I can=E2=80=99t see to resolve one key issue=E2=80=A6 =20 =20 =20 First boot of PXE configuration does an =E2=80=98uninstall=E2=80=99 to e= nsure no past installation of oVirt node exists=E2=80=A6 this works 100% unattended. However using install or reinstall or local_boot (a.k.a. upgrade) or even firstboot option, and even no option, on the APPEND command line via PXE, the automated installation stops. Waiting for interactive response? Is this the expected behavior? Even just using init_storage and BOOTIF, the only two required parameters, the automated process stops for interactive input? So how do you do a completely automated installation with zero human interactive action required? =20 =20 =20 Uninstall=E2=80=A6 This works as expected=E2=80=A6 =20 =20 =20 KERNEL images/oVirt/2.5.5-0.1/vmlinuz0 =20 APPEND rootflags=3Dloop initrd=3Dimages/oVirt/2.5.5-0.1/initrd0.img root=3Dlive:/ovirt-node-iso-2.5.5-0.1.fc17.iso rootfstype=3Dauto ro liveimg check rootflags=3Dro crashkernel=3D512M-2G:64M,2G-:128M elevator=3Ddeadline uninstall =20 =20 =20 Install=E2=80=A6 This does not work as expected, per how the documentati= on implies it should? =20 =20 =20 KERNEL images/oVirt/2.5.5-0.1/vmlinuz0 =20 APPEND rootflags=3Dloop initrd=3Dimages/oVirt/2.5.5-0.1/initrd0.img root=3Dlive:/ovirt-node-iso-2.5.5-0.1.fc17.iso rootfstype=3Dauto ro liveimg check rootflags=3Dro crashkernel=3D512M-2G:64M,2G-:128M elevator=3Ddeadline rd_NO_LVM rd.luks=3D0 rd.md=3D0 rd.dm=3D0 storage_init=3D/dev/sda BOOTIF=3D<FF:FF:FF:FF:FF:FF> =20 =20 =20 =20 _______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
--=-sdXd90bCEO73avACzFJ0 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part Content-Transfer-Encoding: 7bit -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.13 (GNU/Linux) iQIcBAABAgAGBQJREhhcAAoJEC9+uOgSHVGUWpYQALbuozSd7ixUelSMkkFd1Gzo KbrIGSLhkHIUg8uJ8TSvhDyo/NDieUQeRCERobshENZ3eVIDiqJ4ofkwAsXp1hw8 DLLl2WDbLlqUcHvUCDUR7dAoCOJwFjCq/JKmahnJQxPRpAhPknAUCQfK0XgegYwc 6t9FfaQT7j1Yr79TLTNz3cwToQlE0mLxsKypHvi8PbTJ3Lydcj8tcizOLp1crgAB U26SaaozLIm6ZaXFU/+cZVWX510H2TnRm/GFCPAjX0aYBrpRODvV+pwO2TlJPjrV 0shv9xFaCb1IfBnIoJOflNCszDpuOsaP2EXhiJeWgxEy7Y1mlhoQ78Cc+EDEVD4L OT9MOW8vOtBmnQ42bg1KE7IujJr89ZgdD9Aq20VfGA2V9MOZocuJxyHS2h2uJTdR 0j6OiWvD1LdCC80Uo7+6JRKQuA2mf8wEYMtyW3JFeyPke3t6x9HmsjgNyuTDjLAX /Syqg9XoE1msp4KEe0Pf9pd0u3/XVKp3MCfsWAQMCzGVrI+827SH7fFkwGu0XDeP arR10KTdmoRW0DLnlQORACcTTqPZcbEUkzAQch6yRwQVNep1fwvBpNCXLiFupPLr Ga7Hpv1u/LCPx74oRzkVp3aaQz500p13jv/36XHZiFJ5VNW7jYmZ6Jg9vUCh5kww zmg0s83mAMwa4tUSelJZ =IM82 -----END PGP SIGNATURE----- --=-sdXd90bCEO73avACzFJ0--
I am doing this from PXE. Not USB. The question is, is what I found the expected behavior? This entire area of oVirt seems to need some serious enhancement. The same issues exist in RHEV, which is not a surprise, but automated installation is key to enterprise adoption of either oVirt or especially RHEV, so I have the impression this feature set should have a high priority? VMware for example has a very polished and deep deployment methodology, include full stateless deploy of ESXi. Would like to see oVirt/RHEV reach peer stability, consistency and behavior for automated installation to what VMware does, as well as Hyper-V, and even XenServer. I get the impression, no many are using PXE based deployment of oVirt? -----Original Message----- From: Fabian Deutsch [mailto:fabiand@redhat.com] Sent: Wednesday, February 06, 2013 00:46 To: No Reply Cc: users@ovirt.org Subject: Re: [Users] Ovirt Node Automated Installation... full unattended installation? Am Dienstag, den 05.02.2013, 16:02 -0800 schrieb No Reply:
No comments? J This has to be an important feature of oVirt no?
Hey, does it basically work - e.g. when booting from USB - when you add the BOOTIF=eth0 storage_init parameters? So using a device name instead of a mac address? Greetings fabian
From: users-bounces@ovirt.org [mailto:users-bounces@ovirt.org] On Behalf Of No Reply Sent: Saturday, February 02, 2013 20:30 To: users@ovirt.org Subject: Re: [Users] Ovirt Node Automated Installation... full unattended installation?
The plot thickens… I removed BOOTIF and used IPAPPEND 2 directive which per the documentation does automatic append of BOOTIF parameter using the MAC of the adapter that PXE used, and received the DHCPOFFER… then the automated installation worked as the documentation suggests. Does this make sense, or is this some type of odd quirk or bug?
Does not work… (FF:FF:FF:FF:FF:FF is not the real MAC used, just redacted the real MAC)…
KERNEL images/oVirt/2.5.5-0.1/vmlinuz0
APPEND rootflags=loop initrd=images/oVirt/2.5.5-0.1/initrd0.img root=live:/ovirt-node-iso-2.5.5-0.1.fc17.iso rootfstype=auto ro liveimg check rootflags=ro crashkernel=512M-2G:64M,2G-:128M elevator=deadline rd_NO_LVM rd.luks=0 rd.md=0 rd.dm=0 storage_init=/dev/sda BOOTIF=<FF:FF:FF:FF:FF:FF>
Works…
KERNEL images/oVirt/2.5.5-0.1/vmlinuz0
IPAPPEND 2
APPEND rootflags=loop initrd=images/oVirt/2.5.5-0.1/initrd0.img root=live:/ovirt-node-iso-2.5.5-0.1.fc17.iso rootfstype=auto ro liveimg check rootflags=ro crashkernel=512M-2G:64M,2G-:128M elevator=deadline rd_NO_LVM rd.luks=0 rd.md=0 rd.dm=0 storage_init=/dev/sda
From: users-bounces@ovirt.org [mailto:users-bounces@ovirt.org] On Behalf Of Schorschi Sent: Saturday, February 02, 2013 20:07 To: users@ovirt.org Subject: [Users] Ovirt Node Automated Installation... full unattended installation?
Ok, reading the RHEV-H node automated installation, given the oVirt documentation states the same automated installation parameters are supported, I can’t see to resolve one key issue…
First boot of PXE configuration does an ‘uninstall’ to ensure no past installation of oVirt node exists… this works 100% unattended. However using install or reinstall or local_boot (a.k.a. upgrade) or even firstboot option, and even no option, on the APPEND command line via PXE, the automated installation stops. Waiting for interactive response? Is this the expected behavior? Even just using init_storage and BOOTIF, the only two required parameters, the automated process stops for interactive input? So how do you do a completely automated installation with zero human interactive action required?
Uninstall… This works as expected…
KERNEL images/oVirt/2.5.5-0.1/vmlinuz0
APPEND rootflags=loop initrd=images/oVirt/2.5.5-0.1/initrd0.img root=live:/ovirt-node-iso-2.5.5-0.1.fc17.iso rootfstype=auto ro liveimg check rootflags=ro crashkernel=512M-2G:64M,2G-:128M elevator=deadline uninstall
Install… This does not work as expected, per how the documentation implies it should?
KERNEL images/oVirt/2.5.5-0.1/vmlinuz0
APPEND rootflags=loop initrd=images/oVirt/2.5.5-0.1/initrd0.img root=live:/ovirt-node-iso-2.5.5-0.1.fc17.iso rootfstype=auto ro liveimg check rootflags=ro crashkernel=512M-2G:64M,2G-:128M elevator=deadline rd_NO_LVM rd.luks=0 rd.md=0 rd.dm=0 storage_init=/dev/sda BOOTIF=<FF:FF:FF:FF:FF:FF>
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
participants (4)
-
Fabian Deutsch -
No Reply -
Schorschi -
Tim Hildred