Next, you can configure a CIM server. This not required, so feel free to enable this is you wish to do so.
Moving on we have the most important part of the configuration. RHEV-M
Enter the hostname of your RHEV-M server. Mine is rhevm.example.com.
You will also need to specify your admin user password so that your new hypervisor can log into your RHEV-M portal.
The last option you have, is the ability to connect your RHEV Hypervisor to connect to RHN for patches and updates.
From personal experience, I don’t enable RHN. I do this because I wish to maintain complete control over what versions of RHEV-H I am running. You will have the ability to push updates from RHEV-M, so I recommend using RHEV-M to do your RHEV-H updates.
Once you’ve finished all the options you wish to configure, reboot your hypervisor.
The last step in deploying a RHEV-H node, is you need to add the hypervisor to the desired cluster. If you log into the RHEV-M Web Admin portal again, you will see that your new node is waiting for approval.
If you right click on the new node, you can select “Approve”. You will be presented with the below options, where you can change the hostname, and most importantly, configure which Datacenter and Cluster you with your new node to become a member of.
Before clicking OK, don’t forget to configure Power Management. This is used for fencing the server in the event it has a problem.
Don’t worry if you haven’t got all your details right now, you can still click OK, we can confirm the power management later.
Once you click OK, RHEV-M will push the cluster configuration to the hypervisor and install any necessary components. Once it has completed all the necessary items, it will give you a green arrow pointing up, which will report back as being in an “Up” state.
Once the node is in an up state, it will also report back to RHEV-M a whole bunch of details about the host. E.g Kernel version, CPU speed and type, Available memory etc.
You’ll notice all the details in the above screen shot.
This is it. If you wish to deploy all your hypervisors with RHEV-H, just repeat this process.