Before we start, let's do a quick recap in a few words..
What's oVirt Node?
It's a minimal OS that contains all requirements to become an oVirt hypervisor.
What's Hosted Engine?
It's the ability of having the oVirt Node and oVirt Engine in the same machine. Basically, the oVirt Engine will be a virtual machine in the hypervisor. In case you are wondering, Hosted Engine has high availability.
Why we have a new generation of oVirt Node?
It's has been while since the ovirt-node creation, approximately +8 years and ovirt-node requires an update to make users and developers easier.
Some examples of improvements:
- Installation now is based on CentOs/Fedora
- RHEL/Fedora OS like
- New user interface (integrated with Cockpit)
- It's possible to use tools like yum and rpm
- nodectl command line tool
- No need to persist conf files anymore
- Filesystem layout as LVM making possible snapshot, rollback operations
and much more...
Although, we provide via jenkins job several formats of ovirt-node 4.0, like: .iso, .qcow2, .squashfs for this post we will use the .iso. For the oVirt Engine side, we will use the appliance image that already contains the ovirt-engine ready to use.
What's the requirements for this example?
- NFS storage
- ovirt-node-ng iso
Step by Step::
#1 - Files to download
#2 - Copy the .iso to USB, DVD
# dd if=ovirt-node-ng-installer-ovirt-4.0-sna
#3 - Boot the image
#4 - Select the language
#5 - Adjust the date, keyboard, network and press Begin Installation
Tip: if you configure network in the installer, keep the ip address in mind
#6 - Set root password, optionally create a non root user and reboot the system after installation is complete
#7 - In case, you didn't configure the network in the installer it's time to setup an IP address (via dhclient) or set an ip address
#8 - Install the ovirt appliance rpm in the hypervisor
# yum install ovirt-engine-appliance-4.0-20160610.1.el
#9 - Use a web-browser and connect into the hypervisor via cockpit using the port 9090. To continue check the generated certificate and accept it.
#10 - Login into the cockpit with your root account.
#11 - Select virtualization tab, Hosted Engine and click start
#12 - Answer yes as we want to use the machine as hypervisor and create the engine as virtual machine
#13 - Select the supported storage, in our example nfs3
#14 - Specify the nfs path
#15 - Select the nic the host agent will use for the bridge
#16 - Answer yes for automatic configure iptables
#17 - Set the gateway
#18 - Select the device to boot the vm, in this example disk
#19 - Specify the console type (vnc or spice)
#20 - Specify the path of OVA file
#21 - Answer yes to use cloud-init to customize the appliance
#22 - Answer Generate to generate cloud init ISO
#23 - Specify the engine FQDN
In this step, you can use internal DNS or set in /etc/hosts the node.localdomain and engine.localdomain as resolvable names. It's not only important for this initial setup but for later when adding a second host into the hosted engine setup.
Example (in the hypervisor):
# vi /etc/hosts
Tip: You can also setup hostname of hypervisor via Cockpit in case it's not set yet.
#24 - Automatic execute engine-setup in the appliance, in this example, yes.
#25 - Yes for automatic restart engine vm as monitored service
#26 - Set the domain
#27 - Set or skip the password for the engine appliance
#28 - Confirm the CPU family
#29 - Set number of virtual CPUs of vm
#30 - Set or accept generated MAC for the vm
#31 - Set memory size of VM
#32 - Set VM network
#33 - In this example, answer yes to copy /etc/hosts from hypervisor to engine vm for name resolution in the setup
#34 - Set engine admin password
#35 - Complete the questionnaire with the name to identify the host in engine, smtp, answer the final engine settings
#36 - Confirm settings to start the setup
Wait a litte bit and you will see the conclusion of process and your engine vm will be available soon as well.