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(a)redhat.com
Internal: 8588287
Mobile: +61 4 666 25242
IRC: thildred
----- Original Message -----
From: "No Reply" <no-reply(a)dc.rr.com>
To: users(a)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(a)ovirt.org [mailto:users-bounces@ovirt.org] On
Behalf Of Schorschi
Sent: Saturday, February 02, 2013 20:07
To: users(a)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(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/users