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-boun...@ovirt.org [mailto:users-boun...@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-boun...@ovirt.org [mailto:users-boun...@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 signature.asc Description: This is a digitally signed message part ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] Ovirt Node Automated Installation... full unattended installation?
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:fabi...@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-boun...@ovirt.org [mailto:users-boun...@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-boun...@ovirt.org [mailto:users-boun...@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 ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] Ovirt Node Automated Installation... full unattended installation?
No comments? J This has to be an important feature of oVirt no? From: users-boun...@ovirt.org [mailto:users-boun...@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-boun...@ovirt.org [mailto:users-boun...@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
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-boun...@ovirt.org [mailto:users-boun...@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
