Red Hat Virtualization

Confirm that the self-hosted RHV-M meets certain prerequisites and familiarize yourself with some of the configuration settings.

1. From workstation, open a terminal and use ssh to log in to rhvm.lab.example.com using the username root and the password redhat.

   [student@workstation ~]$ ssh root@rhvm.lab.example.com

2. Verify that forward and reverse DNS records exist for rhvm.lab.example.com and that the rhvm.lab.example.com eth0 interface is assigned that address.

   [root@rhvm ~]# host rhvm.lab.example.com
   rhvm.lab.example.com has address 172.25.250.14
   [root@rhvm ~]# host -t PTR 172.25.250.14
   9.250.25.172.in-addr.arpa domain name pointer rhvm.lab.example.com.
   [root@rhvm ~]# ip add show eth0
   2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
       link/ether 52:54:00:00:fa:09 brd ff:ff:ff:ff:ff:ff
       inet 172.25.250.14/24 brd 172.25.250.255 scope global noprefixroute eth0
          valid_lft forever preferred_lft forever
       inet6 fe80::5054:ff:fe00:fa09/64 scope link
          valid_lft forever preferred_lft forever

3. Identify the amount of available memory and CPU. At a minimum, RHV-M should have a dual core CPU with 4 GB of available system RAM. Your output may be different.

   [root@rhvm ~]# free
                 total        used        free   ...
   Mem:        3870976     2860780      122144   ...
   Swap:       8388604        2824     8385780
   [root@rhvm ~]# lscpu | grep 'CPU(s)'
   CPU(s):                2
   On-line CPU(s) list:   0,1
   NUMA node0 CPU(s):     0,1

4. Your self-hosted RHV-M installation created local databases for the engine and data warehouse. Verify that the databases exist on the localhost and that the localhost is listening on the specified port.

   [root@rhvm ~]# grep -A1 localhost /usr/share/ovirt-engine-dwh/\
   services/ovirt-engine-dwhd/ovirt-engine-dwhd.conf | \
   grep -v '^#'
   --
   DWH_DB_HOST="localhost"
   DWH_DB_PORT="5432"
   --
   ENGINE_DB_HOST="localhost"
   ENGINE_DB_PORT="5432"
   [root@rhvm ~]# ss -tln | grep -w 5432
   LISTEN     0      128          *:5432                     *:*
   LISTEN     0      128         :::5432                    :::*

5. The RHV-M REST API needs to be running to access the RHV-M Administration Portal. Verify that ovirt-engine.service is both running and enabled on RHV-M. Exit the SSH session when you are done.

   [root@rhvm ~]# systemctl is-active ovirt-engine.service
   active
   [root@rhvm ~]# systemctl is-enabled ovirt-engine.service
   enabled
   [root@rhvm ~]# exit

Download and install the local CA certificate.

1. On workstation, open http://rhvm.lab.example.com/ovirt-engine/services/pki-resource?resource=ca-certificate&format=X509-PEM-CA in a web browser to download and install the local CA certificate.

2. When prompted, select the option to Trust this CA to identify websites and click the OK button.

Using the Administration Portal, examine the resources created during the self-hosted engine installation.

1. On workstation, open https://rhvm.lab.example.com in a web browser to access the landing page for the RHV Manager.

2. On the landing page, click Administration Portal under the Portals section to be redirected to the Administration Portal login page.

3. Log in using the user name admin, the password redhat, and the Profile set to internal. Upon successful login, you reach the dashboard for the Administration Portal.

4. Identify the data centers that exist by going to: Compute → Data Centers. You should see a data center named Default. The Default data center should have a Status of Up.

5. Identify the clusters that exist by going to: Compute → Clusters. You should see a cluster named Default. The Default cluster belongs to the Default data center.

6. Identify the hosts that exist by going to: Compute → Hosts. Only one host is required for a self-hosted installation, but four hosts exist in your classroom environment to provide high availability. All four hosts belong to the Default data center and the Default cluster.

7. Identify the storage that exists by going to: Storage → Domains. You should see a storage domain with the name of hosted_storage. The domain type should be Data (Master) and the storage type should be NFS. Hovering over the crown icon indicates that the hosted_storage storage domain contains the hosted engine VM data.

8. Verify that the RHV-M guest is running as a virtual machine within the RHV environment by going to: Compute → Virtual Machines. You should see a virtual machine with the name of HostedEngine. Notice how the IP address matches the DNS entry for rhvm.lab.example.com. Hovering over the crown icon indicates that this machine is the Hosted Engine VM.