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
Re: [Users] Create ISO domain from scratch? Not attached, create!
I have a functional data domain, NFS based. So this is not an issue of where the storage domain is offline, nor is the cluster nor the datacenter. I can create a VM, and start it if so desired. And as Alex asked... there is no existing ISO domain, that is what I am trying to create! I don't want to attach an existing ISO domain, I want to create an ISO domain, and the GUI will not allow that option... not even listed as an option. As I said before in RHEV 3.0 and/or oVirt 3.0... this could be done, but in 3.1 something is blocking any attempt to select the type as ISO or even as an EXPORT domain the type drop down list shows DATA only type, nothing else. The backing store to the data domain is just Fedora 17 based NFS, with several exports, all identical. There is nothing unique or custom in this setup, that is why this is such a mystery. I take it, by SPM you mean the Storage Pool Master? The first data domain, NFS DATA based, is the functional master for the datacenter. I am using the existing DEFAULT datacenter and DEFAULT cluster objects, I did not as yet create any additional objects of said types. Not going to increase the complexity of the environment until I get this issue understood and resolved. -Original Message- From: Haim Ateya [mailto:hat...@redhat.com] Sent: Tuesday, January 22, 2013 09:42 To: No Reply Cc: users@ovirt.org Subject: Re: [Users] Create ISO domain from scratch? Not attached, create! Hi, generally speaking, you should be able to create an EXPORT\ISO domain and attach it to the current data-center, if you can't it just means that there is no working data domain and pool is not initialised. please make sure pool (data-center) status is up and running, one of the hosts is functioning as SPM. Haim - Original Message - From: No Reply no-re...@dc.rr.com To: users@ovirt.org Sent: Monday, January 21, 2013 8:50:43 PM Subject: [Users] Create ISO domain from scratch? Not attached, create! Ok, this one has me scratching my head... Have existing oVirt 3.1 environment, based on Fedora 17, storage resource is NFS, also based on Fedora 17. Can create NFS storage domain, no problem. But when the environment was setup initially, no (local) ISO domain as created. Now, under oVirt engine 3.1, the option to create a storage type under domain function, only allows for creation of data type domain, only type in the drop down list is DATA/NFS? What gives? It used to be 3.0 and older, you could select the storage type as Data or ISO! Anyone have this issue as well? Any help appreciated. ___ 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
[Users] Create ISO domain from scratch? Not attached, create!
Ok, this one has me scratching my head... Have existing oVirt 3.1 environment, based on Fedora 17, storage resource is NFS, also based on Fedora 17. Can create NFS storage domain, no problem. But when the environment was setup initially, no (local) ISO domain as created. Now, under oVirt engine 3.1, the option to create a storage type under domain function, only allows for creation of data type domain, only type in the drop down list is DATA/NFS? What gives? It used to be 3.0 and older, you could select the storage type as Data or ISO! Anyone have this issue as well? Any help appreciated. ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users