oVirt is a virtualization management application. Mostly used to manage KVM hypervisors,storage(glusterfs),network etc.
RHEV-M is a customized version of oVirt, released by Redhat for enterprise level support.Some of the features of oVirt includes

Live migration of VMs from one hypervisor to another
snapshot for VM’s
Template creation
Quotas for resources like storage,compute,network
Monitor resource usage on VMs
Self-service console for simple and advanced use cases
Open source, you are welcome to participate in the design and development of project

You can see the link for more details .

In this series i will go through different topics about configuring virtualization with oVirt. My first post in this series is about how to install oVirt manager in centos7 server.

Step 1:

Following configuration should be done before starting the oVirt installation.I am not going to explain this in details.

Set the IP address in server
Set fully qualified domain name for the server(host1.vikki.in)
Add /etc/hosts entry for the hostname pointing to the server IP address
DNS to resolve your hostname
Memory should be of minimum 4GB
Note : I don’t have DNS for my hostname(host1.vikki.in) and my server is having only 1GB of RAM.You can see the warning message displayed during my oVirt engine setup

Step 2:

Download the repositories for oVirt and install it.
oVirt 3.6.1 Release as of December 16th, 2015. I am downloading the latest repo to install oVirt 3.6

[root@host1 ~]#yum install centos-release-ovirt36[root@host1 ~]# sudo rpm -ivh http://plain.resources.ovirt.org/pub/yum-repo/ovirt-release36.rpm
-Retrieving http://plain.resources.ovirt.org/pub/yum-repo/ovirt-release36.rpm
Preparing… ################################# [100%]
Updating / installing…
1:ovirt-release36-002-2 ################################# [100%]

Step 3:

Install the ovirt manager.
Once we installed the yum rpm for ovirt ,we can proceed with installing the oVirt engine

[root@host1 ~]# yum install ovirt-engine

Engine setup explained

Few things about engine setup.

otopi(oVirt Task Oriented Pluggable Installer/Implementation) is a plugin based installation framework used to setup system components. oVirt engine-setup is basically a bash script under /usr/bin/engine-setup ,which call the otopi plugin .

You can see the sample engine-setup script here

Installation sequence of the otopi is below
OTOPI maintains an Environment – key-value-pair store of data and configuration

Simple command line to manipulate environment.

syntax : DIALOG/customization=bool:True

example : OVESETUP_SYSTEM/memCheckEnabled=bool:False – will disble minimum memory check during installation.
we can also parse the environment during installation as below

[root@host1 ~]#engine-setup –otopi-environment=’OVESETUP_SYSTEM/memCheckEnabled=bool:False’

Engine-setup reads /etc/ovirt-engine-setup.conf.d/*.conf, so you can add there a file with answers to questions you do not want to be asked about

We can also generate a answer file and use it for other installation . By default the answer file will be saved under “/var/lib/ovirt-engine/setup/answers/” after every installation.

[root@host1 ~]# engine-setup –generate-answer=answer_file.txt
[ INFO ] Stage: Initializing
[ INFO ] Stage: Environment setup
Configuration files: [‘/etc/ovirt-engine-setup.conf.d/10-packaging-jboss.conf’, ‘/etc/ovirt-engine-setup.conf.d/10-packaging.conf’, ‘/etc/ovirt-engine-setup.conf.d/20-setup-ovirt-post.conf’]
Log file: /var/log/ovirt-engine/setup/ovirt-engine-setup-20151218120448-lphbd4.log
Version: otopi-1.4.0 (otopi-1.4.0-1.el7.centos)
[ INFO ] Stage: Environment packages setup
–output truncated

The anwer file generate is here
To know more you can check the official page here
In step 4 i will run the engine-setup without any options and parse all the answers interactively.

Step 4:

Configure the oVirt engine.
I have highlighted the lines where the user input is required ,For others we can go with the default option.

[root@host1 ~]# engine-setup
[ INFO ] Stage: Initializing
[ INFO ] Stage: Environment setup
Configuration files: [‘/etc/ovirt-engine-setup.conf.d/10-packaging-jboss.conf’, ‘/etc/ovirt-engine-setup.conf.d/10-packaging.conf’]
Log file: /var/log/ovirt-engine/setup/ovirt-engine-setup-20151216172324-th25rp.log
Version: otopi-1.4.0 (otopi-1.4.0-1.el7.centos)
[ INFO ] Stage: Environment packages setup
[ INFO ] Yum Status: Downloading Packages
[ INFO ] Yum Download/Verify: iproute-3.10.0-54.el7.x86_64
[ INFO ] Yum Status: Check Package Signatures
[ INFO ] Yum Status: Running Test Transaction
[ INFO ] Yum Status: Running Transaction
[ INFO ] Yum update: 1/2: iproute-3.10.0-54.el7.x86_64
[ INFO ] Yum updated: 2/2: iproute
[ INFO ] Yum Verify: 1/2: iproute.x86_64 0:3.10.0-54.el7 – u
[ INFO ] Yum Verify: 2/2: iproute.x86_64 0:3.10.0-13.el7 – ud
[ INFO ] Stage: Programs detection
[ INFO ] Stage: Environment setup
[ INFO ] Stage: Environment customization–== PRODUCT OPTIONS ==–Configure Engine on this host (Yes, No) [Yes]:
Configure VM Console Proxy on this host (Yes, No) [Yes]:
Configure WebSocket Proxy on this host (Yes, No) [Yes]:–== PACKAGES ==–[ INFO ] Checking for product updates…
[ INFO ] No product updates found
Host fully qualified DNS name of this server [host1.vikki.in]:
[WARNING] Failed to resolve host1.vikki.in using DNS, it can be resolved only locally
Setup can automatically configure the firewall on this system.
Note: automatic configuration of the firewall may overwrite current settings.
Do you want Setup to configure the firewall? (Yes, No) [Yes]:
The following firewall managers were detected on this system: firewalld, iptables
Firewall manager to configure (firewalld, iptables): firewalld
[ INFO ] firewalld will be configured as firewall manager.
[WARNING] Failed to resolve host1.vikki.in using DNS, it can be resolved only locally
[WARNING] Failed to resolve host1.vikki.in using DNS, it can be resolved only locally

Where is the Engine database located? (Local, Remote) [Local]:
Setup can configure the local postgresql server automatically for the engine to run. This may conflict with existing applications.
Would you like Setup to automatically configure postgresql and create Engine database, or prefer to perform that manually? (Automatic, Manual) [Automatic]:

Application mode (Virt, Gluster, Both) [Both]:
Engine admin password:
Confirm engine admin password:

Default SAN wipe after delete (Yes, No) [No]:

Organization name for certificate [vikki.in]:

Setup can configure apache to use SSL using a certificate issued from the internal CA.
Do you wish Setup to configure that, or prefer to perform that manually? (Automatic, Manual) [Automatic]:
Setup can configure the default page of the web server to present the application home page. This may conflict with existing applications.
Do you wish to set the application as the default page of the web server? (Yes, No) [Yes]:

Configure an NFS share on this server to be used as an ISO Domain? (Yes, No) [Yes]:
Local ISO domain path [/var/lib/exports/iso]:

Please provide the ACL for the Local ISO domain.
See the exports(5) manpage for the format.
– To allow access for host1, host2 and host3, input: host1(rw) host2(rw) host3(rw)
– To allow access to the entire Internet, input: *(rw)

For more information, see: http://www.ovirt.org/Troubleshooting_NFS_Storage_Issues

Local ISO domain ACL: *(rw)
Local ISO domain name [ISO_DOMAIN]:

[ INFO ] Stage: Setup validation
[WARNING] Cannot validate host name settings, reason: resolved host does not match any of the local addresses
[WARNING] Warning: Not enough memory is available on the host. Minimum requirement is 4096MB, and 16384MB is recommended.
Do you want Setup to continue, with amount of memory less than recommended? (Yes, No) [No]: Yes

Application mode : both
Default SAN wipe after delete : False
Firewall manager : firewalld
Update Firewall : True
Host FQDN : host1.vikki.in
Engine database secured connection : False
Engine database host : localhost
Engine database user name : engine
Engine database name : engine
Engine database port : 5432
Engine database host name validation : False
Engine installation : True
NFS setup : True
PKI organization : vikki.in
NFS export ACL : *(rw)
NFS mount point : /var/lib/exports/iso
Configure local Engine database : True
Set application as default page : True
Configure Apache SSL : True
Configure VMConsole Proxy : True
Engine Host FQDN : host1.vikki.in
Configure WebSocket Proxy : True

Please confirm installation settings (OK, Cancel) [OK]:
[ INFO ] Stage: Transaction setup
[ INFO ] Stopping engine service
[ INFO ] Stopping ovirt-fence-kdump-listener service
[ INFO ] Stopping websocket-proxy service
[ INFO ] Stage: Misc configuration
[ INFO ] Stage: Package installation
[ INFO ] Stage: Misc configuration
[ INFO ] Initializing PostgreSQL
[ INFO ] Creating PostgreSQL ‘engine’ database
[ INFO ] Configuring PostgreSQL
[ INFO ] Creating/refreshing Engine database schema
[ INFO ] Creating/refreshing Engine ‘internal’ domain database schema
[ INFO ] Upgrading CA
[ INFO ] Creating CA
[ INFO ] Setting up ovirt-vmconsole proxy helper PKI artifacts
[ INFO ] Setting up ovirt-vmconsole SSH PKI artifacts
[ INFO ] Configuring WebSocket Proxy
[ INFO ] Generating post install configuration file ‘/etc/ovirt-engine-setup.conf.d/20-setup-ovirt-post.conf’
[ INFO ] Stage: Transaction commit
[ INFO ] Stage: Closing up
[ INFO ] Restarting nfs services
–== SUMMARY ==–

[WARNING] Warning: Not enough memory is available on the host. Minimum requirement is 4096MB, and 16384MB is recommended.
SSH fingerprint: 6b:76:c5:48:8e:cd:9d:83:29:ee:4c:a7:4f:db:91:f1
Internal CA DA:80:7C:E1:B0:CC:D6:06:8C:2B:D5:ED:D6:57:B0:4E:90:33:50:41
Note! If you want to gather statistical information you can install Reports and/or DWH:
Web access is enabled at:
Please use the user ‘admin@internal’ and password specified in order to login

[ INFO ] Starting engine service
[ INFO ] Restarting httpd
[ INFO ] Restarting ovirt-vmconsole proxy service
[ INFO ] Stage: Clean up
Log file is located at /var/log/ovirt-engine/setup/ovirt-engine-setup-20151216172324-th25rp.log
[ INFO ] Generating answer file ‘/var/lib/ovirt-engine/setup/answers/20151216172901-setup.conf’
[ INFO ] Stage: Pre-termination
[ INFO ] Stage: Termination
[ INFO ] Execution of setup completed successfully

Step 5:

oVirt installation is completed now, open the serverIP/hostname from your browser. You can see the oVirt default page . Click the “Administrative portal” link and enter the admin password configured during ovirt engine setup(highlighted).