Re: [ovirt-users] ovirt question

On Sat, Apr 21, 2018 at 3:11 AM, Justin Zygmont <jzygmont(a)proofpoint.com&gt; wrote: I too tried some weeks ago (4.2.1 if I remeber correctly) and was confused.... I was able to succesfully deploy, with these steps and pxe, also taking "inspiration" on what written at this link: https://github.com/oVirt/ovirt-node-ng/blob/master/docs/book/install.md note: my pxe server makes also as dhcp server and http server for install - iso of node-ng-installer mounted (via loop in my case) under /var/www/html/ovnode42 of pxe server -under /var/www/html created directory ovnode2_stage2 containing product.img (6k of file) downloaded here: http://jenkins.ovirt.org/job/ovirt-node-ng_ovirt-4.2_build- artifacts-el7-x86_64/lastStableBuild/artifact/exported-artifacts/ --> why not included..? I think in theory one can downoad here also the file updates.img and it should update the base version of the iso... TBV (not tested by me) ---> where to get the updates.img? Perhaps inside ovirt-node-ng-image-update-x.y.z.rpm? - inside ovnode2_stage2 created directory LiveOS and inside it created the link ln -sf /var/www/html/ovnode42/LiveOS/squashfs.img /var/www/html/ovnode42_stage2/LiveOS/squashfs.img - the pxe file It contains default pxeboot timeout 50 label pxeboot kernel vmlinuz.ovnode42 append initrd=initrd.ovnode42.img inst.ks=http://192.168.122.1/ovnode42.ks inst.stage2=http://192.168.122.1/ovnode42_stage2/ verbose - kickstart file in /var/www/html created file ovnode42.ks it contains install lang en_US.UTF-8 keyboard us rootpw --plaintext my_password network --bootproto=dhcp timezone --utc Europe/Rome firewall --service=ssh liveimg --url=http://192.168.122.1/ovnode42/ovirt-node-ng-image.squashfs.img # partitioning - nuke and start fresh zerombr clearpart --all --initlabel autopart --type=thinp bootloader --location=mbr #reboot last line left commented to cross-check before reboot at pxe boot the graphical install comes up and completes the install without any prompt It only asks to reboot as I commented out the line above verified that after reboot I was able to connect to the server at https on port 9090 and getting the node dashboard any validation comment? HIH, Gianluca