In this video, I'll show you how to deploy a hyper-converged architecture.
Oracle Linux Virtualization Manager has been integrated with Gluster 6, an open source,
distributed file system, to provide a hyperconverged solution where both compute and storage are
provided from the same hosts. Gluster volumes residing on the hosts are
used as storage domains in the Manager to store the virtual machine images.
Oracle Linux Virtualization Manager is run as a self-hosted engine within a virtual machine
on these hosts. To deploy this hyperconverged solution, you
must satisfy the following prerequisites. There must be a minimum of 3 Oracle Linux
7 Servers with Minimal Installation. Currently, this configuration is supported
with Oracle Linux 7 only. The minimal release is the same as specified
in Oracle Linux Virtualization Manager documentation. For this demonstration, I'll call my 3 Oracle
Linux 7 Servers a.us.oracle.com, b.us.oracle.com, and c.us.oracle.com.
These 3 systems are physical servers on the Oracle network.
Host a is a Netra Server X5-2 and hosts b and c are Oracle Server X5-2.
Host a will be our deployment hosts, that is, I'll initiate the deployment from host
a. Ensure that the firewalld service is enabled
and started on all 3 Oracle Linux 7 servers. If you are using a proxy server for Internet
access, configure Yum with the proxy server settings.
You must have configured password-less ssh between the first server to itself and to
the other 2 servers. This is needed for Gluster deployment.
The fully qualified domain names of the 3 Oracle Linux 7 servers can be resolved using
DNS or through the /etc/hosts file on the servers.
Continuing on with the prerequisites, you must have a fully qualified domain name prepared
for your self-hosted engine. For this demonstration, I'll call my self
hosted engine book.us.oracle.com Forward and reverse lookup records must both
be set in the DNS. And the self-hosted engine should use the
same subnet as the management network. Install the required software packages.
On all 3 hosts, install the oracle-ovirt-release-el7 package.
This package is provided by the ol7_latest yum repository.
Install the cockpit-ovirt-dashboard package. This provides a UI for the installation.
And install the vdsm-gluster package. This is a plugin to manage gluster services.
Both the cockpit-ovirt-dashboard package and the vdsm-gluster package are provided by the
ovirt-4.3 yum repository. On the deployment host only, install the following
packages: ovirt-engine-appliance
This is for the engine virtual machine installation. This package is provided by ovirt-4.3 yum
repository. And gluster-ansible-roles
This is for deploying, configuring, and maintaining GlusterFS clusters and is provided by ol7_gluster6
yum repository. Set up the hyperconverged environment.
On the deployment host, start the Cockpit service and enable Cockpit on firewalld by
running the commands shown. systemctl enable --now cockpit
firewall-cmd --permanent --add-service=cockpit And then firewall-cmd --reload
From a web browser, log in to Cockpit management interface of your Oracle Linux 7 deployment
host, at port 9090. In this demonstration, host a.us.oracle.com
is our deployment hosts. From the Cockput UI on the deployment host,
start the deployment wizard by clicking Virtualization, then Hosted Manager, then click the Start
button under Hyperconverged. We'll now begin the demonstration portion
of this video. I've accessed the Cockpit management interface
on our deployment host a at port 9090. I'll log in as root and provide the root password.
Now I'll start the deployment wizard by clicking the V in the left-hand menu for Virtualization.
Then I'll click Hosted Manager, then I'll scroll down and click the Start button under
Hyperconverged. This allows us to configure gluster storage
which is the first step of this deployment. An existing gluster configuration exists so
I'm going to click the "Clean Existing Gluster Deployment" button.
This deletes the volumes, removes the brick directories, unmounts the disks, wipes the
file system from the logical volumes, deletes the volume groups, removes the physical volumes,
and performs a number of other cleanup tasks. We'll see later in this demonstration that
we select /dev/sdb as the device to be used to create the gluster brick.
But I've logged on to our host a to show that /dev/sdb is clean and available for use.
Now I'll click the "Run Gluster Wizard" button and I'm first asked to provide the Gluster
hosts. I'll enter our 3 Oracle Linux 7 servers, a.us.oracle.com,
b.us.oracle.com, and c.us.oracle.com. As you have noticed, I'm masking out the full
hostnames for security purposes. I'll click Next and for the Additional Hosts,
I'll click the "Use same hostnames as in previous step" checkbox.
I'll click Next and for the Packages window, no entries are required since we already installed
the required packages. Additional packages can optionally be installed
on all hosts but click Next for this demonstration. On the Volumes window, you define the gluster
volumes that need to be created. These gluster volumes will be used later in
the wizard, to create storage domains in Oracle Linux Virtualization Manager.
3 gluster volumes are defined by default. The first volume in the list named engine,
is used to host the Hosted Engine virtual disk.
The second volume named data, is used to host the data disks of the virtual machines.
The third volume named vmstore, is used to host the OS disks of the virtual machines.
Separating the volumes as shown eases backup, assuming only data volume will need to be
backed up. All 3 gluster volumes will be created as Data
storage domains. I'll click Next to move to the Bricks tab.
Here you configure the devices to use for the gluster volumes defined in the previous
step. If the devices used for bricks are configured
as RAID devices, provide the information in the RAID information section.
I'll just take the default and scroll down to the Brick configuration section.
Brick configuration allows for per-host definition of bricks.
This is useful in case the device names are not uniform across the hosts.
I'm going to use /dev/sdb for creating gluster volumes.
The only change I'll make is to change the default size of 500 GB for data and vmstore
to 200 GB. I'll click Next and from here you can review
the generated ansible inventory and deploy gluster.
I'm going to click the "Enable Debug Logging" checkbox just in case the deployment fails,
I'll have more information for troubleshooting. Now I'll click the Deploy button.
In this demonstration, the deployment takes a couple minutes but I'll speed through this.
Gluster successfully deployed. I'll log into our 3 Oracle Linux 7 hosts and
view the configuration on /dev/sdb. Here's is the gluster configuration on host
a for /dev/sdb. We used /dev/sdb on all hosts for creating
gluster volumes so here is the configuration for /dev/sdb on host b.
And here is the gluster volume configuration on host c.
Once Gluster deployment is finished, click the “Continue to Hosted Engine Deployment”
button to begin configuring your hosted engine. This results in Oracle Linux Virtualization
Manager running as a virtual machine on the first physical machine in your deployment.
In this VM window, provide the Engine VM FQDN. Recall from the prerequisites mentioned earlier
in this video, you must have prepared a fully qualified domain name for your self-hosted
engine. For this demonstration, I created an DNS entry
for my self hosted engine named book.us.oracle.com I'm also going to change the Network Configuration
from the default of DHCP to static and provide the IP addresses for the VM, the Gateway,
and the DNS Server. I'm going to provide the root password and
take the remaining defaults for the VM settings. I'll scroll down and click Advanced to view
more settings. The only thing I'll change here is to use
Ping for the Network Test, rather than the default of DNS.
I'll click Next. On the Engine window, I'll provide an Admin
Portal Password and keep the remaining defaults. I'll click Next and I'm presented with opportunity
to review the configuration. You can click Back and make make changes.
The configuration looks good to me so I'll scroll down and click Prepare VM.
This will create a local hosted engine VM. In this demonstration, it took about 20 minutes
to prepare the hosted engine VM but I'll speed through this.
Execution completed successfully. I'll click next to configure the storage domain
that will be used to host the self-hosted engine disk.
The only change I'll make here is under the advanced settings.
I'll increase the disk size to 80 GB. I'll click Next.
You can now review the configuration and go back if any changes are needed.
I'll click the Finish Deployment button. Now, the local self-hosted engine will be
transferred to the configured Gluster storage domain.
In this demonstration, it took about 14 minutes to finish the deployment but I'll speed through
this. The hosted engine deployment completed.
I'll click the close button and now I can exit this Cockpit management interface.
Now we can access the self hosted engine. I'll browse to book.us.oracle.com/ovirt-engine
and log in to the Administration Portal. The dashboard shows we have 3 hosts, 3 data
storage domains, 3 gluster volumes, and 1 virtual machine.
I'll view our 3 Oracle Linux 7 hosts. I'll view our 3 GlusterFS storage domains.
I'll view our 3 Gluster volumes. And I'll view our 1 hosted engine virtual
machine. This concludes the demonstration portion of
this video. For more information, you can refer to the
Oracle Linux Virtualization Manager Getting Started Guide, the uUpstream oVirt documentation,
the GlusterFS documentation, and the Oracle Communities page on deploying Oracle Linux
Virtualization Manager and Gluster Hyperconverged. This concludes this video.
Thank you for watching.