inst.stage2 = This specifies the location to fetch ONLY the installer runtime image; packages will be ignored. I think it is helping to streamline ovirt-node build, as installation part is untouch OS and we deploy 2nd squash as image of node. On Mon, Apr 23, 2018 at 9:38 PM, Justin Zygmont <jzygmont@proofpoint.com> wrote:
Thanks, but I still don’t understand why there are 2 squash images though.
*From:* Gianluca Cecchi [mailto:gianluca.cecchi@gmail.com] *Sent:* Saturday, April 21, 2018 12:59 AM *To:* Justin Zygmont <jzygmont@proofpoint.com> *Cc:* users@ovirt.org *Subject:* Re: [ovirt-users] ovirt question
On Sat, Apr 21, 2018 at 3:11 AM, Justin Zygmont <jzygmont@proofpoint.com> wrote:
I was wondering why there has to be 2 node squash images? A LiveOS/squash.img and a ovirt-node-ng-image.squashfs.img in the ISO for download, and which one should be used?
When doing a kickstart installation I noticed it uses the Live OS image from the inst.stage2= and in the kickstart.cfg it would reference the other node image from liveimg --url
Is there any documentation around doing kickstart installs with oVirt?
Thanks,
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 <https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_oVirt_ovirt-2Dnode-2Dng_blob_master_docs_book_install.md&d=DwMFaQ&c=Vxt5e0Osvvt2gflwSlsJ5DmPGcPvTRKLJyp031rXjhg&r=FiPhL0Cl1ymZlnTyAIIL75tE4L0reHcDdD-7wUtUGHA&m=rgnKzgcbneUduKTLB3TK11-C0nujZ9pmv5fb29w3P6M&s=7e2QHo5p940uHfpIDVGgpWYEmvdU_hv19H4TzdDSdP0&e=>
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/ <https://urldefense.proofpoint.com/v2/url?u=http-3A__jenkins.ovirt.org_job_ovirt-2Dnode-2Dng-5Fovirt-2D4.2-5Fbuild-2Dartifacts-2Del7-2Dx86-5F64_lastStableBuild_artifact_exported-2Dartifacts_&d=DwMFaQ&c=Vxt5e0Osvvt2gflwSlsJ5DmPGcPvTRKLJyp031rXjhg&r=FiPhL0Cl1ymZlnTyAIIL75tE4L0reHcDdD-7wUtUGHA&m=rgnKzgcbneUduKTLB3TK11-C0nujZ9pmv5fb29w3P6M&s=hd2ex3r30up9YjbMif_YZQkk6ONU9wynqDjXAaxXVbE&e=>
--> 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 <https://urldefense.proofpoint.com/v2/url?u=http-3A__192.168.122.1_ovnode42.ks&d=DwMFaQ&c=Vxt5e0Osvvt2gflwSlsJ5DmPGcPvTRKLJyp031rXjhg&r=FiPhL0Cl1ymZlnTyAIIL75tE4L0reHcDdD-7wUtUGHA&m=rgnKzgcbneUduKTLB3TK11-C0nujZ9pmv5fb29w3P6M&s=2j4G8J91YRcAtTH5JYykwQauX3-YYwuAVOf_As5FMjs&e=> inst.stage2=http://192.168.122.1/ovnode42_stage2/ <https://urldefense.proofpoint.com/v2/url?u=http-3A__192.168.122.1_ovnode42-5Fstage2_&d=DwMFaQ&c=Vxt5e0Osvvt2gflwSlsJ5DmPGcPvTRKLJyp031rXjhg&r=FiPhL0Cl1ymZlnTyAIIL75tE4L0reHcDdD-7wUtUGHA&m=rgnKzgcbneUduKTLB3TK11-C0nujZ9pmv5fb29w3P6M&s=bgorHrFZRlkzBi4oljt0NO2kH8OsuS3Wpr8cj51lSdk&e=> 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 <https://urldefense.proofpoint.com/v2/url?u=http-3A__192.168.122.1_ovnode42_ovirt-2Dnode-2Dng-2Dimage.squashfs.img&d=DwMFaQ&c=Vxt5e0Osvvt2gflwSlsJ5DmPGcPvTRKLJyp031rXjhg&r=FiPhL0Cl1ymZlnTyAIIL75tE4L0reHcDdD-7wUtUGHA&m=rgnKzgcbneUduKTLB3TK11-C0nujZ9pmv5fb29w3P6M&s=1bhy8J4Y7Il6RBc8WYH0tD_35B2H-syyR9QGJsIBaSI&e=>
# 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
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
-- PAVOL BRILLA RHV QUALITY ENGINEER, CLOUD Red Hat Czech Republic, Brno <https://www.redhat.com/> <https://red.ht/sig> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>