
--=-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--