Oracle® Linux Virtualization Manager - Getting Started Guide
Oracle® Linux Virtualization Manager - Getting Started Guide
Oracle® Linux Virtualization Manager - Getting Started Guide
Getting Started
F52194-07
May 2023
Oracle Linux Virtualization Manager Getting Started,
F52194-07
1 Preface
Conventions 1-1
Documentation Accessibility 1-2
Access to Oracle Support for Accessibility 1-2
Diversity and Inclusion 1-2
iii
Next Steps 3-11
Logging Out 3-11
Configuring a KVM Host 3-11
Preparing a KVM Host 3-11
Adding a KVM Host 3-13
4 Quick Start
Before You Begin 4-1
Adding a KVM Host to the Manager 4-2
Adding Storage 4-2
Attaching an iSCSI Data Domain 4-2
Uploading Images to the Data Domain 4-3
Before You Begin 4-3
Uploading an ISO Image to the Data Domain 4-4
Creating a Logical Network 4-5
Creating a Virtual Machine Network 4-5
Assigning the Virtual Machine Network to a KVM Host 4-6
Creating a New Virtual Machine 4-9
Installing Remote Viewer on Client Machine 4-9
Creating a New Oracle Linux Virtual Machine 4-10
Installing the Oracle Linux Guest OS 4-13
Installing the Oracle Linux Guest Agent 4-13
Creating a New Microsoft Windows Virtual Machine 4-14
Before You Begin 4-14
Creating a New Microsoft Windows Virtual Machine 4-15
Installing the Microsoft Windows Guest OS 4-18
Installing the VirtIO Drivers 4-19
Installing the QEMU Guest Agent 4-20
Creating a Template 4-22
Sealing an Oracle Linux Virtual Machine for Use as a Template 4-22
Creating an Oracle Linux Template 4-23
Creating a Cloud-Init Enabled Template 4-25
Before You Begin 4-25
Using Cloud-Init to Automate the Initial Setup of a Virtual Machine 4-26
Creating a Virtual Machine from a Template 4-27
Creating an Oracle Linux Virtual Machine from a Template 4-27
Backing Up and Restoring the Manager 4-28
Backing Up the Manager 4-29
Restoring a Full Backup of the Manager 4-29
iv
5 Self-Hosted Engine Deployment
Self-Hosted Engine Prerequisites 5-1
Deploying the Self-Hosted Engine 5-2
Using the Command Line to Deploy 5-4
Using the Cockpit Portal to Deploy 5-9
Enabling High-Availability 5-11
Configuring a Highly Available Host 5-11
Configuring Power Management and Fencing on a Host 5-12
Preventing Host Fencing During Boot 5-14
Checking Fencing Parameters 5-14
Installing Additional Self-Hosted Engine Hosts 5-14
Cleaning up the Deployment 5-15
Upgrading Or Updating the Self-Hosted Engine 5-15
v
1
Preface
Oracle Linux Virtualization Manager Release 4.4 is based on oVirt, which is a free, open-
source virtualization solution. The product documentation comprises:
• Release Notes - A summary of the new features, changes, fixed bugs, and known issues
in the Oracle Linux Virtualization Manager. It contains last-minute information, which
might not be included in the main body of documentation.
• Architecture and Planning Guide - An architectural overview of Oracle Linux
Virtualization Manager, prerequisites, and planning information for your environment.
• Getting Started Guide - How to install, configure, and get started with the Oracle Linux
Virtualization Manager. The document includes an example scenario covering basic
procedures for setting up the environment, such as adding hosts and storage, creating
virtual machines, configuring networks, working with templates, and backup and restore
tasks. In addition, there is information on upgrading your engine and hosts as well as
deploying a self-hosted configuration.
• Administration Guide - Provides common administrative tasks for Oracle Linux
Virtualization Manager and information on setting up users and groups, configuring high-
availability, memory and CPUs, configuring and using event notifications, configuring
vCPUs and virtual memory.
You can also refer to:
• REST API Guide, which you can access from the Welcome Dashboard or directly
through its URL https://manager-fqdn/ovirt-engine/apidoc.
• Upstream oVirt Documentation.
To access the Release 4.3.10 documentation, PDFs are available at:
• https://www.oracle.com/a/ocom/docs/olvm43/olvm-43-releasenotes.pdf
• https://www.oracle.com/a/ocom/docs/olvm43/olvm-43-gettingstarted.pdf
• https://www.oracle.com/a/ocom/docs/olvm43/olvm-43-architecture-planning.pdf
• https://www.oracle.com/a/ocom/docs/olvm43/olvm-43-administration.pdf
Conventions
The following text conventions are used in this document:
Convention Meaning
boldface Boldface type indicates graphical user interface elements associated
with an action, or terms defined in text or the glossary.
italic Italic type indicates book titles, emphasis, or placeholder variables for
which you supply particular values.
monospace Monospace type indicates commands within a paragraph, URLs, code
in examples, text that appears on the screen, or text that you enter.
1-1
Chapter 1
Documentation Accessibility
Documentation Accessibility
For information about Oracle's commitment to accessibility, visit the Oracle
Accessibility Program website at http://www.oracle.com/pls/topic/lookup?
ctx=acc&id=docacc.
For information about the accessibility of the Oracle Help Center, see the Oracle
Accessibility Conformance Report at https://www.oracle.com/corporate/accessibility/
templates/t2-11535.html.
1-2
2
Requirements and Scalability Limits
Before you begin the tasks in this guide, you should review Oracle Linux Virtualization
Manager Release 4.4 concepts, environment requirements, and scalability limitations in the
Oracle Linux Virtualization Manager: Architecture and Planning Guide.
2-1
3
Installation and Configuration
To deploy Oracle Linux Virtualization Manager, you install and configure the engine on a host
with Oracle Linux 8.5 (or later), configure KVM hosts, storage, and networks, and create
virtual machines. Thoroughly review the Requirements and Scalability Limits as the
requirements for the engine host are different than the KVM hosts.
To review conceptual information and help to plan your installation, see the Oracle Linux
Virtualization Manager: Architecture and Planning Guide.
Note:
You can install the Manager in a virtual machine as long as it is not managing that
virtual machine, or in a self-hosted engine configuration. For more information, see
Self-Hosted Engine Deployment. Do not configure the same host as a
standalone engine and a KVM host.
You can download the installation ISO for Oracle Linux 8.5 (or later) from the Oracle Software
Delivery Cloud at https://edelivery.oracle.com.
1. Install Oracle Linux 8.5 (or later) on the host using the Minimal Install base environment.
Follow the instructions in the Oracle® Linux 8: Installing Oracle Linux.
Important:
Do not install any additional packages until after you have installed the
Manager packages, because they may cause dependency issues.
2. (Optional) If you use a proxy server for Internet access, configure Yum with the proxy
server settings. For more information, see the Oracle® Linux: Managing Software on
Oracle Linux.
3. Complete one of the following sets of steps:
• For ULN registered hosts or using Oracle Linux Manager
Subscribe the system to the required channels.
3-1
Chapter 3
Installing the Engine
Important:
Before you execute dnf config-manager ensure the dnf-utils
package is installed on your system. For more information, see
Yum DNF in Oracle® Linux: Managing Software on Oracle
Linux .
3-2
Chapter 3
Installing the Engine
d. Use the dnf command to verify that the required repositories are enabled.
i. Clear the dnf cache.
# dnf clean all
ii. List the configured repositories and verify that the required repositories are
enabled.
# dnf repolist
3-3
Chapter 3
Installing the Engine
Note:
Run engine-setup --accept-defaults to automatically accept all
questions that have default answers.
If you enter No, the configuration stops. To restart, rerun the engine-setup
command.
4. For the remaining configuration questions, provide input or accept default values,
which are in square brackets after each question. To accept the default value for a
given question, press Enter.
Note:
Setup asks you for the fully qualified DNS name (FQDN) of the Manager
host. Although Setup tries to automatically detect the name, you must
ensure the FQDN is correct.
For detailed information on the configuration options, see Engine
Configuration Options.
5. Once you have answered all the questions, Setup displays a list of the values you
entered. Review the list carefully and then press Enter to configure the Manager.
Your answers are saved to a file that can be used to reconfigure the Manager
using the same values. Setup also displays the location of the log file for the
configuration process.
6. When the configuration is complete, details about how to log in to the
Administration Portal are displayed. To verify that the configuration was
successful, log into the Administration Portal, as described in Logging in to the
Administration Portal.
3-4
Chapter 3
Installing the Engine
Note:
Some of the configuration option are in technology preview; Oracle recommends
that you accept the default values for these features. For more information, see
Technology Preview in the Oracle Linux Virtualization Manager: Release Notes.
OVN Provider
Configuring ovirt-provider-ovn also sets the Default cluster's default network
provider to ovirt-provider-ovn.
Non-Default clusters may be configured with an OVN after installation.
Configure ovirt-provider-ovn (Yes, No) [Yes]:
Install the Open Virtual Network (OVN) provider on the Manager host and add it as an
external network provider. The default cluster is automatically configured to use OVN as its
network provider.
OVN is an OVS (Open vSwitch) extension which enables you to configure virtual networks.
Using external providers, including the OVN provider, is a technology preview feature.
WebSocket Proxy
Configure WebSocket Proxy on this machine? (Yes, No) [Yes]:
The WebSocket Proxy enables you to connect to virtual machines using the noVNC or HTML
5 consoles.
For security and performance reasons, you can configure the WebSocket Proxy on a remote
host.
Data Warehouse
Please note: Data Warehouse is required for the engine.
If you choose to not configure it on this host, you have to configure
it on a remote host, and then configure the engine on this host so that it can
access the database of the remote Data Warehouse host.
Configure Data Warehouse on this host (Yes, No) [Yes]:
The Data Warehouse feature can run on the Manager host or on a remote host. Running
Data Warehouse on a remote host reduces the load on the Manager host.
Running the Data Warehouse on a remote host is a technology preview feature.
VM Console Proxy
Configure VM Console Proxy on this host (Yes, No) [Yes]:
The VM Console Proxy enables you to access virtual machine serial consoles from a
command line. To use this feature, serial consoles must be enabled in the virtual machines.
Grafana
Use Engine admin password as initial Grafana admin password (Yes, No) [Yes]:
3-5
Chapter 3
Installing the Engine
Grafana can be configured to to use the Engine password to make signing in easier.
The fully qualified DNS name of the Manager host. Check that the automatically
detected DNS name is correct.
Configure the firewall on the host to open the ports used for external communication
between Oracle Linux Virtualization Manager and the components it manages.
If Setup configures the firewall, and no firewall managers are active, you are prompted
to select a firewall manager from a list.
If you enter No, you must manually configure the firewall. When the Manager
configuration is complete, Setup displays a list of ports that need to be opened, see for
details.
The Data Warehouse database (the history database) can run on the Manager host or
on a remote host. Running the database on a remote host reduces the load on the
Manager host.
Running the database on a remote host is a technology preview feature.
Caution:
In this step you configure the name of the database, and the user name and
password for connecting to it. Make a note of these details.
3-6
Chapter 3
Installing the Engine
Enter Automatic to have Setup configure a local database server, or Manual to connect to an
existing local database server. If you enter Manual, you are prompted for the details for
connecting to the database:
DWH database secured connection (Yes, No) [No]:
DWH database name [ovirt_engine_history]:
DWH database user [ovirt_engine_history]:
DWH database password:
If you enter Remote to connect to an existing PostgreSQL server running on a remote host,
you are prompted for the details for connecting to the database:
DWH database host [localhost]:
DWH database port [5432]:
DWH database secured connection (Yes, No) [No]:
DWH database name [ovirt_engine_history]:
DWH database user [ovirt_engine_history]:
DWH database password:
Engine Database
Where is the Engine database located? (Local, Remote) [Local]:
The Oracle Linux Virtualization Manager database (the engine database) can run on the
Manager host or on a remote host. Running the database on a remote host reduces the load
on the Manager host.
Running the database on a remote host is a technology preview feature.
Caution:
In this step you configure the name of the database, and the user name and
password for connecting to it. Make a note of these details.
Enter Automatic to have Setup configure a local database server, or Manual to connect to an
existing local database server. If you enter Manual, you are prompted for the details for
connecting to the database:
Engine database secured connection (Yes, No) [No]:
Engine database name [engine]:
Engine database user [engine]:
Engine database password:
If you enter Remote to connect to an existing PostgreSQL server running on a remote host,
you are prompted for the details for connecting to the database:
3-7
Chapter 3
Installing the Engine
Enter a password for the default administrative user (admin@internal). Make a note of
the password. If you use a simple password, you might get the following warning:
[WARNING] Password is weak: The password fails the dictionary check - it is
based on a dictionary word
Use weak password? (Yes, No) [No]: Yes
Application Mode
Application mode (Both, Virt, Gluster) [Both]:
The Manager can be configured to manage virtual machines (Virt) or manage Gluster
clusters (Gluster), or Both.
If you installed the OVN provider, configure the credentials for connecting to the OVN
(Open vSwitch) databases.
Using external providers, including the OVN provider, is a technology preview feature.
Enter Yes to set the default value for the wipe_after_delete flag to true, which wipes
the blocks of a virtual disk when it is deleted.
Using the wipe after delete functionality is a technology preview feature.
Provide the organization name to use for the automatically generated self-signed SSL
certificate used by the Manager web server.
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 web page of the server? (Yes,
No) [Yes]:
3-8
Chapter 3
Installing the Engine
Enter Yes to make the Oracle Linux Virtualization Manager landing page the default page
presented by the web server.
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]:
Enter Automatic to generate a self-signed SSL certificate for the web server. Only use self-
signed certificates for testing purposes.
Enter Manual to provide the location of the SSL certificate and private key to use the web
server.
Set the Data Warehouse sampling scale, either Basic or Full. This step is skipped the Data
Warehouse is not configured to run on the Manager host.
Enter 1 for Basic, which reduces the values of DWH_TABLES_KEEP_HOURLY to 720 and
DWH_TABLES_KEEP_DAILY to 0. Enter 2 for Full.
If the Manager and the Data Warehouse run on the same host, Basic is the recommended
sample scale because this reduces the load on the Manager host. Full is recommended only
if the Data Warehouse runs on a remote host.
The Full sampling scale is a technology preview feature.
Grafana
Use Engine admin password as initial Grafana admin password (Yes, No) [Yes]:
Grafana can be configured to to use the Engine password to make signing in easier.
Preparing to Log in
It is recommended that you use the latest version one of the following browsers to access the
Administration Portal
• Mozilla Firefox
• Google Chrome
• Apple Safari
• Microsoft Internet Explorer 11
• Microsoft Edge
3-9
Chapter 3
Installing the Engine
Usually you access the Administration Portal using the fully qualified domain name of
the Manager host that you provided during installation. However, you can access the
Administration Portal using an alternate host name(s). To do this, you need to add a
configuration file to the Manager as follows:
1. Log in to the Manager host as root.
2. Create the file /etc/ovirt-engine/engine.conf.d/99-custom-sso-
setup.conf with the following content:
SSO_ALTERNATE_ENGINE_FQDNS="alias1.example.com alias2.example.com"
Logging in
You log in to the Administration Portal using a web browser and the default
admin@internal user.
1. Go to https://manager-fqdn/ovirt-engine. The Welcome page displays.
2. (Optional) Change the preferred language from the drop-down list on the
Welcome page.
You can view the Administration Portal in multiple languages. The default
language is based on the locale of your web browser.
3. Click Administration Portal. The Login page displays.
4. Enter admin for the Username and the password you specified when you
configured the Manager.
5. From the Profile list, select internal and click Log In.
Important:
From the Welcome dashboard, you also have the option of logging into two
additional portals:
• The VM Portal
• The Monitoring Portal
For more information, see Access Portals in the Oracle Linux Virtualization
Manager: Architecture and Planning Guide
3-10
Chapter 3
Configuring a KVM Host
Next Steps
Now that you have configured and logged into the Manager, the next step is to add Oracle
Linux KVM hosts, as described in Configuring a KVM Host.
You also need to add storage and configure logical networks. See Adding Storage and
Creating a Logical Network.
Logging Out
To log out of the Administration Portal, click the person icon in the header bar and click
Sign Out. You are returned to the Login page.
Caution:
Do NOT select any other base environment than Minimal Install for the
installation or your hosts will have incorrect qemu and libvirt versions,
incorrect repositories configured, and no access to virtual machine
consoles.
• Do not install any additional packages until after you have added the host to the
Manager, because they may cause dependency issues.
2. (Optional) If you use a proxy server for Internet access, configure Yum with the proxy
server settings. For more information, see the Oracle® Linux: Managing Software on
Oracle Linux.
3. Complete one of the following sets of steps:
• For ULN registered hosts or using Oracle Linux Manager
3-11
Chapter 3
Configuring a KVM Host
Note:
Installing the Oracle Linux Virtualization Manager Release 4.4
package configures an Oracle Linux KVM host; it does not install the
Manager.
a. (Optional) Make sure the host is using the modular yum repository
configuration. For more information, see Getting Started with Oracle Linux
Yum Server.
b. Enable the ol8_baseos_latest repository.
# dnf config-manager --enable ol8_baseos_latest
3-12
Chapter 3
Configuring a KVM Host
Important:
Before you execute dnf config-manager ensure the dnf-utils package
is installed on your system. For more information, see Yum DNF in
Oracle® Linux: Managing Software on Oracle Linux.
d. Use the dnf command to verify that the required repositories are enabled.
i. Clear the dnf cache.
# dnf clean all
ii. List the configured repositories and verify that the required repositories are
enabled.
# dnf repolist
The Cockpit web interface can be used to monitor the host’s resources and to perform
administrative tasks. You can access the host's Cockpit web interface from the
Administration Portal or by connecting directly to the host.
For more information about configuring firewalld, see Configuring a Packet Filtering
Firewall in the Oracle® Linux 8: Configuring the Firewall.
5. (Optional) Complete the previous steps to prepare additional KVM hosts.
The Oracle Linux KVM host is now ready to be added to the Manager using the
Administration Portal.
3-13
Chapter 3
Configuring a KVM Host
Note:
When you install Oracle Linux Virtualization Manager, a data center and
cluster named Default is created. You can rename and configure this data
center and cluster, or you can add new data centers and clusters, to meet
your needs. See the Data Centers and Clusters tasks in the Oracle Linux
Virtualization Manager: Administration Guide for details of how to do this.
Note:
If you do not want to set any other configuration options now, you can
always make changes later by selecting a host from the Hosts pane and
clicking Edit.
3-14
Chapter 3
Configuring a KVM Host
11. If you do not want to configure power management, click OK. Otherwise, click Configure
Power Management. See Configuring Power Management and Fencing on a Host for
more information.
The host is added to the list of hosts in the Manager. While the Manager is installing the
host agent (VDSM) and other required packages on the host, the status of the host is
shown as Installing. You can view the progress of the installation in the Hosts details
pane. When the installation is complete, the host status changes to Up.
12. (Optional) Complete the previous steps to add more KVM hosts to the Manager.
Important:
Oracle Linux Virtualization Manager allows you to overallocate a KVM host's
memory and CPU resources. As the KVM host itself also needs memory and CPU
in order to run, Oracle recommends that you reserve some memory and CPU for
the KVM host. To do this, go to Administration and set a memory quota and a
vCPU quota.
Now that you have your engine and host(s) configured, you can complete other configuration
and administrative tasks. See Quick Start for information on configuring your environment
with storage, networks, virtual machines and learn how to create templates and back up your
environment. See the Oracle Linux Virtualization Manager: Administration Guide for more
detailed configuration and administrative tasks.
3-15
4
Quick Start
To get you started with Oracle Linux Virtualization Manager, the following example scenario
walks you through the procedures for adding hosts, adding storage, setting up a network,
creating virtual machines, and backing up and restoring the Manager.
Note:
For detailed information on the supported guest operating systems, see the
Oracle® Linux: KVM User's Guide.
– The procedures for creating Oracle Linux and Microsoft Windows virtual machines
assume that you have added the ISO images to the data domain on the storage
device used in Adding Storage.
4-1
Chapter 4
Adding a KVM Host to the Manager
Important:
See See Windows Virtual Machines Lose Functionality Due To
Deprecated Guest Agent in the Known Issues section of the Oracle
Linux Virtualization Manager: Release Notes.
– To use the console to access a virtual machine, you must install the Remote
Viewer application on the client from which you want to access. This
application provides users with a graphical console for connecting to virtual
machines.
1. Install the virt-viewer package.
# dnf install virt-viewer
2. Restart your browser for the changes to effect in the Oracle Linux
Virtualization Manager.
Adding Storage
For this example scenario, you attach an iSCSI storage to your virtualization
environment and then upload an ISO image to the data domain. If you do not have
access to an iSCSI device, refer to Storage in the Oracle Linux Virtualization Manager:
Administration Guide for the procedures for adding other storage types to your
virtualization environment.
4-2
Chapter 4
Adding Storage
5. From the Domain Function drop-down list, select the domain function. By default, the
Data option is selected in the drop-down list.
For this step, leave Data as the domain function because you are creating a data domain
in this example.
6. From the Storage Type drop-down list, select iSCSI.
7. From the Host drop-down list, select the host for which to attach the data domain.
For this example scenario, select the host added in Adding a KVM Host to the Manager.
8. When iSCSI is selected for the Storage Type, the Discover Targets dialog box opens
and the New Domain dialog box automatically displays the known targets with unused
LUNs under the Target Name column.
If the target from which you are adding storage is not listed, complete the following fields
in the Discover Targets dialog box:
a. For the Address field, enter fully qualified domain name or IP address of the iSCSI
host on the storage array.
b. For the Port field, enter the port to connect to on the host when browsing for targets.
By default, this field is automatically populated with the default iSCSI Port, 3260.
After completing these fields, click Discover.
The Target Name column updates to list all the available targets discovered on the
storage array.
9. Under the Target Name column, select the desired target and select the black right-
directional arrow to log in to the target.
The Storage Domains pane refreshes to list only the targets for which you logged in.
10. Click + to expand the desired target.
If you are using ZFS storage, you must uncheck the Discard after Delete option.
13. Click OK.
You can click Tasks to monitor the various processing steps that are completed to attach
the iSCSI data domain to the data center.
After the iSCSI data domain has been added to your virtualization environment, you can
then upload the ISO images that are used for creating virtual machines in Creating a New
Virtual Machine.
4-3
Chapter 4
Adding Storage
1. On the engine host, verify that the ovirt-imageio service has been configured
and is running.
# systemctl status ovirt-imageio.service
This service is automatically configured and is started when you run the engine-
setup command during the installation of the Manager.
2. On the KVM host, verify that the ovirt-imageio service has been configured
and is running. For example:
# systemctl status ovirt-imageio-daemon
ovirt-imageio-daemon.service - oVirt ImageIO Daemon
Loaded: loaded (/usr/lib/systemd/system/ovirt-imageio-daemon.service;
disabled;
vendor preset: disabled)
Active: active (running) since Wed 2019-03-27 18:38:36 EDT; 3 weeks 4
days ago
Main PID: 366 (ovirt-imageio-d)
Tasks: 4
CGroup: /system.slice/ovirt-imageio-daemon.service
└─366 /usr/bin/python /usr/bin/ovirt-imageio-daemon
3. Verify that the certificate authority has been imported into the web browser used to
access the Manager by browsing to the following URL and enabling the trust
settings: https://engine_address/ovirt-engine/services/pki-resource?
resource=ca-certificate&format=X509-PEM-CA
4. Verify that you are using a browser that meets the browser requirement to access
the Administration Portal.
For more information, refer to the Logging in to the Administration Portal.
5. Proceed to Uploading an ISO Image to the Data Domain.
4-4
Chapter 4
Creating a Logical Network
3. Click Upload and then select Start from the drop-down list.
The Upload Image dialog box opens.
4. Click Choose File and navigate to the location where you saved the ISO image.
5. Complete the Disk Options section of the dialog box.
6. Ensure that the prerequisites have been met by clicking Test Connection.
If the test returns a warning or error message, refer to Before You Begin to review the
prerequisites.
7. Click OK to start uploading the ISO image.
The status field on the Disks pane tracks the progress of the upload.
After the ISO image upload is completed successfully, you can attach the image to virtual
machines as CDROMs or use the image to boot virtual machines.
Note:
If you plan to use VLANs on top of bonded interfaces, refer to the My Oracle
Support (MOS) article How to Configure 802.1q VLAN on NIC (Doc ID 1642456.1)
for instructions.
4-5
Chapter 4
Creating a Logical Network
6. (Optional) Configure other settings for the new logical network from the other tabs
on the New Logical Network sidebar.
The default settings are used for this example scenario.
7. Click OK to create the network.
The following screenshot shows the General tab of the New Logical Network
dialog box completed for the new logical network that is being created in this
example:
• From the Data Center drop-down list, the Default option is selected.
• For the Name field, vm_pub is entered.
• Under the Network Parameters section, the VM Network check box is
selected.
4-6
Chapter 4
Creating a Logical Network
After clicking the name of the host, the General tab opens with details about the host.
3. Click the Network Interfaces tab on the horizontal menu.
The Network Interfaces tab opens with details about the network interfaces on the
available host.
4. Highlight the network interface that you want to use for the network being added by
clicking the row for the respective interface.
5. Click Setup Host Networks.
The Setup Host Networks dialog box opens for the host. The physical interfaces on the
host are listed under the Interfaces column and any logical networks assigned to the
interface are displayed under the Assigned Logical Networks column. Unassigned
logical networks are displayed under the Unassigned Logical Networks column.
As shown in the following screenshot, the logical network created in Creating a Logical
Network named vm_pub is displayed under the Unassigned Logical Networks column.
In the next step, you assign this network to the network interface named eno2, which
currently has no network assigned to it.
4-7
Chapter 4
Creating a Logical Network
6. Select the network you want to add from the Unassigned Logical Networks
column by left-clicking the network and, while holding down the mouse, drag the
network over to the box to the right of the available network interface where you
want to add the network.
Alternatively, you can right-click the network and select the available interface from
a drop-down list.
For this example, the logical network named vm_pub is assigned to the available
network interface named eno2. As shown in the following screenshot, after
dragging the network from Unassigned Logical Networks over to this interface,
the network named vm_pub appears under the Assigned Logical Networks
column as assigned to the network interface named eno2.
4-8
Chapter 4
Creating a New Virtual Machine
Note:
In addition to creating virtual machines, you can import an Open Virtual Appliance
(OVA) file into your environment from any host in the data center. For more
information, see oVirt Virtual Machine Management in oVirt Documentation.
4-9
Chapter 4
Creating a New Virtual Machine
Note:
See See Windows Virtual Machines Lose Functionality Due To Deprecated
Guest Agent in the Known Issues section of the Oracle Linux Virtualization
Manager: Release Notes.
For more information, see Consoles in the Oracle Linux Virtualization Manager:
Architecture and Planning Guide.
To install Remote Viewer on Linux:
1. Ensure you have downloaded the virt-viewer installation package.
2. Install the virt-viewer package using one of the following commands depending
on your system.
# yum install virt-viewer
3. Restart your browser for the changes to take effect in the Oracle Linux
Virtualization Manager.
You can now connect to your virtual machines using the VNC protocol.
To install Remote Viewer on Windows:
1. Ensure you have downloaded either the 32-bit or 64-bit virt-viewer installer
depending on the architecture of your system.
2. Go to the folder where you saved the file and double-click the file.
3. If prompted with a security warning, click Run.
4. If prompted by User Account Control, click Yes.
Once installed, you can access Remote Viewer in the VirtViewer folder of All
Programs from the Start menu.
Note:
For detailed information on the supported guest operating systems, see the
Oracle® Linux: KVM User's Guide.
4-10
Chapter 4
Creating a New Virtual Machine
2. Click New.
The New Virtual Machine dialog box opens with the General tab selected on the
sidebar.
3. From the Cluster drop-down list, select the data center and host cluster for the new host.
By default, the Default option is selected in the drop-down list.
For this step, leave Default selected from the drop-down list because the default data
center and cluster are used in this example scenario. For the procedures to create new
data centers or a new clusters, refer to Data Centers or Clusters tasks in the Oracle Linux
Virtualization Manager: Administration Guide.
4. From the Operating System drop-down list, select the operating system for the virtual
machine.
5. For the Name field, enter a name for the new virtual machine.
6. Under Instance Images, add storage to the virtual machine by either using an existing
virtual disk or creating a new virtual desk.
• To use an existing virtual disk, click Attach and select the virtual disk to use for the
virtual machine storage. Then click OK.
• To create a new virtual disk, click Create and update the fields for the virtual machine
storage or accept the default settings. Then click OK.
For the example scenario, all of the default settings are accepted for the new virtual disk
that is being created, except the Size (GiB) field, which is set to 4. The following
screenshot shows the New Virtual Disk dialog box for the Oracle Linux virtual machine
being created in this example scenario.
4-11
Chapter 4
Creating a New Virtual Machine
4-12
Chapter 4
Creating a New Virtual Machine
4-13
Chapter 4
Creating a New Virtual Machine
3. Start the guest agent service for the Oracle Linux guest.
(Example scenario) For Oracle Linux 8 and Oracle Linux 7 guests:
# systemctl start qemu-guest-agent.service
4. (Optional) Enable an automatic restart of the guest agent service when the virtual
machine is rebooted.
(Example scenario) For Oracle Linux 8 and Oracle Linux 7 guests:
# systemctl enable qemu-guest-agent.service
4-14
Chapter 4
Creating a New Virtual Machine
4-15
Chapter 4
Creating a New Virtual Machine
7. Connect the virtual machine to a network by selecting the vNIC profile created in
Creating a Logical Network from the nic1 drop-down list.
For information about customizing vNICs, refer to Customizing vNIC Profiles for
Virtual Machines in the Oracle Linux Virtualization Manager: Administration Guide.
The following screenshot shows the General tab on New Virtual Machine dialog
box for the new Microsoft Windows virtual machine that is being created in this
example scenario. In the dialog box, the following key fields are completed:
• From the Cluster drop-down list, the Default option is selected.
• For the Operating System drop-down list, Windows 10 x64 is selected.
• For the Name field, windows-10-vm is entered.
• Under Instance Images, a virtual disk named windows-10-vm_Disk1 is being
created, which has been set to a size of 12GB.
• From the nic1 drop-down list, the logical network named vm_pub is selected.
4-16
Chapter 4
Creating a New Virtual Machine
8. Click the System tab on the sidebar to adjust the memory size for the virtual machine
from the defaults.
In this example, change the Memory Size field to 4096 MB and the Total Virtual CPUs
field to 4.
The following screenshot shows the System tab on New Virtual Machine dialog box for
the new Microsoft Windows virtual machine that is being created in this example
scenario. In the dialog box, the following key fields are completed:
4-17
Chapter 4
Creating a New Virtual Machine
4-18
Chapter 4
Creating a New Virtual Machine
The Virtual Machines pane opens with the list of virtual machines that have been
created.
12. Select the Microsoft Windows virtual machine created in Creating a New Microsoft
Windows Virtual Machine and click Edit.
13. Edit the virtual disk. From the Interface drop-down list, change SATA to VirtIO-SCSI .
4-19
Chapter 4
Creating a New Virtual Machine
a. Do not make any changes to the First Device drop-down list. The Hard Disk
option is selected from a previous step.
b. From the Second Device drop-down list, select None.
c. Deselect the Attach CD checkbox.
15. Click OK to save the changes to the virtual machine configuration.
# ls -alt /usr/i686-w64-dir/sys-root/username/bin
total 9280
drwxr-xr-x. 2 root root 30 Nov 3 13:56 .
-rw-r--r--. 1 root root 9499648 Nov 2 09:45 qemu-ga-i386.msi
drwxr-xr-x. 3 root root 17 Sep 23 19:02 ..
# ls -alt /usr/x86_64-w64-dir/sys-root/username/bin/
total 9472
drwxr-xr-x. 2 root root 32 Nov 3 13:56 .
-rw-r--r--. 1 root root 9697280 Nov 2 09:45 qemu-ga-x86_64.msi
Important:
• If you have access to the virtual machine, you can copy the appropriate
MSI (32-bit or 64-bit) to the virtual machine and then run the installer to
install the QEMU guest agent.
• If you do not have access to the virtual machine, use the following steps
to build and upload an ISO and then install the QEMU guest agent.
Build the ISO and install the QEMU guest agent on the virtual machine.
1. Build the QEMU guest agent ISO.
4-20
Chapter 4
Creating a New Virtual Machine
build-iso/
# cp /usr/i686-w64-dir/sys-root/username/bin/qemu-ga-i386.msi build-iso/
# mkisofs -R -J -o qemu-ga-windows.iso build-iso/*
I: -input-charset not specified, using utf-8 (detected in locale settings)
Using QEMU_000.MSI;1 for /qemu-ga-x86_64.msi (qemu-ga-i386.msi)
52.36% done, estimate finish Thu Nov 3 14:20:49 2022
Total translation table size: 0
Total rockridge attributes bytes: 347
Total directory bytes: 0
Path table size(bytes): 10
Max brk space used 0
9549 extents written (18 MB)
# ll qemu-ga-windows.iso
-rw-r--r--. 1 root root 19556352 Nov 3 14:20 qemu-ga-windows.iso
2. Upload the QEMU guest agent ISO image to an Oracle Linux Virtualization Manager
storage domain. Refer to Uploading an ISO Image to the Data Domain for more
information.
3. From the Virtual Machines pane, select the virtual machine created in Creating a New
Microsoft Windows Virtual Machine.
4. Highlight the row for this virtual machine, and click Edit.
The Edit Virtual Machines dialog box opens.
5. Click the Boot Options tab on the sidebar of the dialog box to specify the boot sequence
for the virtual device.
a. From the First Device drop-down list, change CD-ROM to Hard Disk.
b. From the Second Device drop-down list, select CD-ROM.
c. Select the Attach CD checkbox and choose the qemu executable from the drop-
down list.
6. Click OK to save the changes to the virtual machine configuration.
7. Click OK when the Pending Virtual Machine changes dialog box appears.
8. From the Virtual Machines pane, reboot the virtual machine.
9. Click Console to open a console to the virtual machine and navigate to the CDROM.
10. Double-click the the qemu executable to launch the installation program.
11. When installation completes, click Yes, I want to restart my computer now and click
Finish.
The virtual machine is restarted.
12. Stop the virtual machine.
The Virtual Machines pane opens with the list of virtual machines that have been
created.
14. Select the Microsoft Windows virtual machine created in Creating a New Microsoft
Windows Virtual Machine and click Edit.
15. Click the Boot Options tab on the sidebar.
4-21
Chapter 4
Creating a Template
a. Do not make any changes to the First Device drop-down list. The Hard Disk
option is selected from a previous step.
b. From the Second Device drop-down list, select None.
c. Deselect the Attach CD checkbox.
16. Click OK to save the changes to the virtual machine configuration.
17. From the Virtual Machines pane, reboot the virtual machine.
For more information, see the Oracle® Linux: KVM User's Guide
Creating a Template
For this example scenario, you seal the Oracle Linux virtual machine created in
Creating a New Virtual Machine and then you create an Oracle Linux template based
on that virtual machine. You then use that template as the basis for a Cloud-Init
enabled template to automate the initial setup of a virtual machine.
A template is a copy of a virtual machine that you can use to simplify the subsequent,
repeated creation of similar virtual machines. Templates capture the configuration of
software, the configuration of hardware, and the software installed on the virtual
machine on which the template is based, which is known as the source virtual
machine.
Virtual machines that are created based on a template use the same NIC type and
driver as the original virtual machine but are assigned separate, unique MAC
addresses.
Important:
Oracle provides pre-installed and pre-configured templates that allow you to
deploy a fully configured software stack. Use of Oracle Linux templates
eliminates the installation and configuration costs and reduces the ongoing
maintenance costs. For more information, see Importing an Oracle Linux
Template in the Oracle Linux Virtualization Manager: Administration Guide.
4-22
Chapter 4
Creating a Template
# rm -rf /etc/ssh/ssh_host_*
The Oracle Linux virtual machine is now sealed and ready to be made into a template.
4-23
Chapter 4
Creating a Template
3. For the Name field, enter a name for the new virtual machine template.
4. In the Disc Allocation: section under the Alias column, rename the disk alias to
be the same as the template name entered for the Name field.
5. Click the Seal Template (Linux only) checkbox.
The following screenshot shows the New Template dialog box completed for the
new template named ol7-vm-template, which is being created in this example
scenario. In the dialog box, the disk alias has been renamed to ol7-vm-template
and the Seal Template (Linux only) checkbox is selected.
4-24
Chapter 4
Creating a Template
4-25
Chapter 4
Creating a Template
• To use Cloud-Init, the cloud-init package must first be installed on the virtual
machine. Once installed, the Cloud-Init service starts during the boot process and
searches for instructions on what to configure. Use the Run Once window to
provide these instructions on a one-time only basis.
• You must have sealed an Oracle Linux for use as a template. For more
information, refer to Sealing an Oracle Linux Virtual Machine for Use as a
Template.
• You must create a template. For more information, refer to Creating an Oracle
Linux Template.
1. Log in to a Oracle Linux virtual machine.
2. List the cloud-init package.
# yum list cloud-init
4-26
Chapter 4
Creating a Virtual Machine from a Template
• Select the In-guest Network Interface check box and use the + Add new and -
Remove selected buttons to add or remove network interfaces to or from the virtual
machine.
Important:
You must specify the correct network interface name and number (for
example, eth0, eno3, enp0s); otherwise, the virtual machine’s interface
connection will be up but will not have the Cloud-Init network configuration.
9. Expand the Custom Script section and enter any custom scripts in the Custom Script
text area.
4-27
Chapter 4
Backing Up and Restoring the Manager
Figure 4-12 New Virtual Machine Dialog Box for a Template - General Tab
4-28
Chapter 4
Backing Up and Restoring the Manager
Note:
When running the Manager within a virtual machine (standalone or self-hosted
engine) log into the virtual machine that is running the engine.
2. Create a full backup of the Manager. You do not need to stop the ovirt-engine service
before creating your backup.
# engine-backup --mode=backup --scope=all --file=path --log=path
The following example shows how to use the engine-backup command to create a full
backup of the Manager. A backup file and log file for the Manager backup is created in
the path specified.
# engine-backup --mode=backup --scope=all --file=backup/file/ovirt-engine-backup --
log=backup/log/ovirt-engine-backup.log
Backing up:
Notifying engine
- Files
- Engine database 'engine'
- DWH database 'ovirt_engine_history'
Packing into file 'backup/file/ovirt-engine-backup'
Notifying engine
Done.
Note:
When running the Manager within a virtual machine (standalone or self-hosted
engine) log into the virtual machine that is running the engine.
4-29
Chapter 4
Backing Up and Restoring the Manager
This engine-cleanup command removes the configuration files and cleans the
database associated with the Manager.
The following example shows output from the engine-cleanup command.
# engine-cleanup
[ INFO ] Stage: Initializing
[ INFO ] Stage: Environment setup
Configuration files: ...
Log file: ...
Version: otopi-1.7.8 (otopi-1.7.8-1.el7)
[ INFO ] Stage: Environment packages setup
[ INFO ] Stage: Programs detection
[ INFO ] Stage: Environment customization
Do you want to remove all components? (Yes, No) [Yes]: Yes
The following files were changed since setup:
/etc/ovirt-engine/engine.conf.d/11-setup-sso.conf
Remove them anyway? (Yes, No) [Yes]: Yes
4-30
Chapter 4
Backing Up and Restoring the Manager
The following example shows how to use the engine-backup command to restore a full
backup of the Manager.
# engine-backup --mode=restore --scope=all --file=backup/file/ovirt-engine-backup \
--log=backup/log/ovirt-engine-backup.log --restore-permissions
Preparing to restore:
- Unpacking file 'backup/file/ovirt-engine-backup'
Restoring:
- Files
- Engine database 'engine'
- Cleaning up temporary tables in engine database 'engine'
- Updating DbJustRestored VdcOption in engine database
- Resetting DwhCurrentlyRunning in dwh_history_timekeeping in engine database
- Resetting HA VM status
------------------------------------------------------------------------------
Please note:
Objects that were added, removed or changed after this date, such as virtual
machines, disks, etc., are missing in the engine, and will probably require
recovery or recreation.
------------------------------------------------------------------------------
- DWH database 'ovirt_engine_history'
You should now run engine-setup.
Done.
4. Run the engine-setup command to complete the setup of the restored Manager.
# engine-setup
This command reconfigures the firewall and ensures that the Manager service is correctly
configured.
5. Log in to the Manager and verify that the Manager has been restored to the backup.
4-31
5
Self-Hosted Engine Deployment
In Oracle Linux Virtualization Manager, a self-hosted engine is a virtualized environment
where the engine runs inside a virtual machine on the hosts in the environment. The virtual
machine for the engine is created as part of the host configuration process. And, the engine
is installed and configured in parallel to the host configuration.
Since the engine runs as a virtual machine and not on physical hardware, a self-hosted
engine requires less physical resources. Additionally, since the engine is configured to be
highly available, if the host running the Engine virtual machine goes into maintenance mode
or fails unexpectedly the virtual machine is migrated automatically to another host in the
environment. A minimum of two KVM hosts are required.
To review conceptual information, troubleshooting, and administration tasks, see the oVirt
Self-Hosted Engine Guide in oVirt Documentation.
To deploy a self-hosted engine, you perform a fresh installation of Oracle Linux 8.5 (or later)
on the host, install the Oracle Linux Virtualization Manager Release 4.4 package, and then
run the hosted engine deployment tool to complete configuration.
Note:
If you are deploying a self-hosted engine as a hyperconverged infrastructure with
GlusterFS storage, you must deploy GlusterFS BEFORE you deploy the self-hosted
engine. See Deploying GlusterFS Storage.
Note:
The VDSM user and KVM group must have read, write, and execute
permissions on the directory.
5-1
Chapter 5
Deploying the Self-Hosted Engine
NOT_SUPPORTED:
When you have a data center with only one active data storage domain
and that domain gets corrupted, you are unable to add new data storage
domains or remove the corrupted data storage domain. If you have
deployed your self-hosted engine in such a data center and its data
storage domain gets corrupted, you must redeploy your self-hosted
engine.
• The host you are using to deploy a self-hosted engine, must be able to access
yum.oracle.com.
Caution:
Do NOT select any other base environment than Minimal Install for the
installation or your hosts will have incorrect qemu and libvirt versions,
incorrect repositories configured, and no access to virtual machine
consoles.
Do not install any additional packages until after you have installed the
Manager packages, because they may cause dependency issues.
5-2
Chapter 5
Deploying the Self-Hosted Engine
a. For ULN registered hosts, log in to https://linux.oracle.com with your ULN user
name and password. For Oracle Linux Manager registered hosts, access your
internal server URL.
b. On the Systems tab, click the link named for the host in the list of registered
machines.
c. On the System Details page, click Manage Subscriptions.
d. On the System Summary page, select each required channel from the list of
available channels and click the right arrow to move the channel to the list of
subscribed channels. Subscribe the system to the following channels:
– ol8_x86_64_baseos_latest
– ol8_x86_64_appstream
– ol8_x86_64_kvm_appstream
– ol8_x86_64_ovirt44
– ol8_x86_64_ovirt44_extras
– ol8_x86_64_gluster_appstream
– (For VDSM) ol8_x86_64_UEKR7
e. Click Save Subscriptions.
f. Disable the virt:ol module and enable the virt:kvm_utils2 module.
# dnf -y module disable virt:ol
Important:
Before you execute config-manager ensure the dnf-utils package is
installed on your system. For more information, see Yum DNF in
Oracle® Linux: Managing Software on Oracle Linux.
d. Use the dnf command to verify that the required repositories are enabled.
i. Clear the yum cache.
# dnf clean all
5-3
Chapter 5
Deploying the Self-Hosted Engine
ii. List the configured repositories and verify that the required
repositories are enabled.
# dnf repolist
You can deploy a self-hosted engine using the command line or Cockpit portal. If you
want to use the command line, proceed to Using the Command Line to Deploy. If you
want to use the Cockpit portal, proceed to Using the Cockpit Portal to Deploy.
Note:
If you are behind a proxy, you must use the command line option to deploy.
Note:
You can deploy the hosted engine using all the default settings. Make
sure the auto-detected fully qualified DNS name of the host is correct.
The fully qualified DNS name should resolve to the IP address that is
accessible through the host's main interface. For more information on the
default settings, see Engine Configuration Options.
5-4
Chapter 5
Deploying the Self-Hosted Engine
Optionally, use the --ansible-extra-vars option to define variables for the deployment.
For example:
# hosted-engine --deploy --ansible-extra-vars="@/root/extra-vars.yml"
cat /root/extra-vars.yml
---
he_pause_host: true
he_proxy: "http://<host>:<port>"
See the oVirt documentation for more information, Deploying the self-hosted engine
using the command line.
2. Enter Yes to begin deployment.
Continuing will configure this host for serving as hypervisor and will create a
local VM
with a running engine. The locally running engine will be used to configure a new
storage
domain and create a VM there. At the end the disk of the local VM will be moved to
the
shared storage.
Are you sure you want to continue? (Yes, No)[Yes]:
Note:
The hosted-engine script creates a virtual machine and uses cloud-init to
configure it. The script also runs engine-setup and reboots the system so that
the virtual machine can be managed by the high availability agent.
c. The script detects possible NICs to use as a management bridge for the
environment. Select the default.
Please indicate a nic to set ovirtmgmt bridge on: (eth1, eth0) [eth1]:
4. Enter the path to an OVA archive if you want to use a custom appliance for the virtual
machine installation. Otherwise, leave this field empty to use the oVirt Engine Appliance.
If you want to deploy with a custom engine appliance image,
please specify the path to the OVA archive you would like to use
(leave it empty to skip, the setup will use ovirt-engine-appliance rpm
installing it if missing):
5. Specify the fully-qualified domain name for the engine virtual machine.
Please provide the FQDN you would like to use for the engine appliance.
Note: This will be the FQDN of the engine VM you are now going to launch,
it should not point to the base host or to any other existing machine.
Engine VM FQDN: manager.example.com
Please provide the domain name you would like to use for the engine appliance.
Engine VM domain: [example.com]
5-5
Chapter 5
Deploying the Self-Hosted Engine
Enter root password that will be used for the engine appliance:
Confirm appliance root password:
7. Optionally, enter an SSH public key to enable you to log in to the engine as the
root user and specify whether to enable SSH access for the root user.
Enter ssh public key for the root user that will be used for the engine
appliance (leave it empty to skip):
Do you want to enable ssh access for the root user (yes, no, without-
password)
[yes]:
9. Enter a MAC address for the engine virtual machine or accept a randomly
generated MAC address.
You may specify a unicast MAC address for the VM or accept a randomly
generated default [00:16:3e:3d:34:47]:
Note:
If you want to provide the engine virtual machine with an IP address
using DHCP, ensure that you have a valid DHCP reservation for this
MAC address. The deployment script does not configure the DHCP
server for you.
Note:
If you specified Static, enter the IP address of the Engine. The static IP
address must belong to the same subnet as the host. For example, if the
host is in 10.1.1.0/24, the Engine virtual machine’s IP must be in the
same subnet range (10.1.1.1-254/24).
Please enter the IP address to be used for the engine VM [x.x.x.x]:
Please provide a comma-separated list (max 3) of IP addresses of
domain
name servers for the engine VM
Engine VM DNS (leave it empty to skip):
11. Specify whether to add entries in the virtual machine’s /etc/hosts file for the
engine virtual machine and the base host. Ensure that the host names are
resolvable.
Add lines for the appliance itself and for this host to /etc/hosts on the
engine VM?
Note: ensuring that this host could resolve the engine VM hostname is still
5-6
Chapter 5
Deploying the Self-Hosted Engine
up
to you (Yes, No)[No]
12. Provide the name and TCP port number of the SMTP server, the email address used to
send email notifications, and a comma-separated list of email addresses to receive these
notifications. Or, press Enter to accept the defaults.
Please provide the name of the SMTP server through which we will send
notifications [localhost]:
Please provide the TCP port number of the SMTP server [25]:
Please provide the email address from which notifications will be sent
[root@localhost]:
Please provide a comma-separated list of email addresses which will get
notifications [root@localhost]:
13. Enter and confirm a password for the admin@internal user to access the Administration
Portal.
Enter engine admin password:
Confirm engine admin password:
The script creates the virtual machine which can take time if it needs to install the oVirt
Engine Appliance. After creating the virtual machine, the script continues gathering
information.
14. Select the type of storage to use.
Please specify the storage you would like to use (glusterfs, iscsi, fc,
nfs)[nfs]:
• If you selected NFS, enter the version, full address and path to the storage, and any
mount options.
Please specify the nfs version you would like to use (auto, v3, v4,
v4_1)[auto]:
Please specify the full shared storage connection path to use (example:
host:/path):
storage.example.com:/hosted_engine/nfs
If needed, specify additional mount options for the connection to the
hosted-engine storage domain []:
• If you selected iSCSI, enter the portal details and select a target and LUN from the
auto-detected lists. You can only select one iSCSI target during the deployment, but
multipathing is supported to connect all portals of the same portal group.
Note:
To specify more than one iSCSI target, you must enable multipathing before
deploying the self-hosted engine. There is also a Multipath Helper tool that
generates a script to install and configure multipath with different options.
5-7
Chapter 5
Deploying the Self-Hosted Engine
[1] iqn.2017-10.com.redhat.example:he
TPGT: 1, portals:
192.168.1.xxx:3260
192.168.2.xxx:3260
192.168.3.xxx:3260
• If you selected GlusterFS, enter the full address and path to the storage, and
any mount options. Only replica 3 Gluster storage is supported.
* Configure the volume as follows as per [Gluster Volume Options for
Virtual
Machine Image Store]
(documentation/admin-guide/chap-Working_with_Gluster_Storage#Options
set on Gluster Storage Volumes to Store Virtual Machine Images)
• If you selected Fibre Channel, select a LUN from the auto-detected list. The
host bus adapters must be configured and connected. The deployment script
auto-detects the available LUNs, and the LUN must not contain any existing
data.
The following luns have been found on the requested target:
[1] 3514f0c5447600351 30GiB XtremIO XtremApp
status: used, paths: 2 active
If successful, one data center, cluster, host, storage domain, and the engine virtual
machine are already running.
16. Optionally, log into the Oracle Linux Virtualization Manager Administration Portal to
add any other resources.
In the Administration Portal, the engine virtual machine, the host running it, and
the self-hosted engine storage domain are flagged with a gold crown.
17. Enable the required repositories on the Engine virtual machine.
5-8
Chapter 5
Deploying the Self-Hosted Engine
Note:
If you are behind a proxy, you must use the command line option to deploy your
self-hosted engine.
To deploy the self-hosted engine using the Cockpit portal, complete the following steps.
1. Install the Cockpit dashboard.
# dnf install cockpit-ovirt-dashboard -y
5-9
Chapter 5
Deploying the Self-Hosted Engine
• Enter a Root SSH Public Key to use for root access to the Engine virtual
machine.
• Select the Edit Hosts File check box if you want to add entries for the Engine
virtual machine and the base host to the virtual machine’s /etc/hosts file. You
must ensure that the host names are resolvable.
• Change the management Bridge Name, or accept the default of ovirtmgmt.
• Enter the Gateway Address for the management bridge.
• Enter the Host FQDN of the first host to add to the Engine. This is the FQDN
of the host you are using for the deployment.
9. Click Next.
10. Enter and confirm the Admin Portal Password for the admin@internal user.
• Enter the Server Name and Server Port Number of the SMTP server.
• Enter a Sender E-Mail Address.
• Enter Recipient E-Mail Addresses.
12. Click Next.
13. Review the configuration of the Engine and its virtual machine. If the details are
correct, click Prepare VM.
14. When the virtual machine installation is complete, click Next.
15. Select the Storage Type from the drop-down list and enter the details for the self-
hosted engine storage domain.
• For NFS:
a. In the Storage Connection field, enter the full address and path to the
storage.
b. If required, enter any Mount Options.
c. Enter the Disk Size (GiB).
d. Select the NFS Version from the drop-down list.
e. Enter the Storage Domain Name.
• For iSCSI:
a. Enter the Portal IP Address, Portal Port, Portal Username, and Portal
Password.
b. Click Retrieve Target List and select a target. You can only select one
iSCSI target during the deployment, but multipathing is supported to
connect all portals of the same portal group.
Note:
To specify more than one iSCSI target, you must enable
multipathing before deploying the self-hosted engine. There is
also a Multipath Helper tool that generates a script to install and
configure multipath with different options.
5-10
Chapter 5
Enabling High-Availability
If successful, one data center, cluster, host, storage domain, and the engine virtual
machine are already running.
19. Optionally, log into the Oracle Linux Virtualization Manager Administration Portal to add
any other resources.
In the Administration Portal, the engine virtual machine, the host running it, and the self-
hosted engine storage domain are flagged with a gold crown.
20. Enable the required repositories on the Engine virtual machine.
Enabling High-Availability
The host that houses the self-hosted engine is not highly available by default. Since the self-
hosted engine runs inside a virtual machine on a host, if you do not configure high-availability
for the host, then live VM migration is not possible.
5-11
Chapter 5
Enabling High-Availability
The Manager can perform management operations after it reboots, by a proxy host, or
manually in the Administration Portal. All the virtual machines running on the non-
responsive host are stopped, and highly available virtual machines are restarted on a
different host. At least two hosts are required for power management operations.
Important:
If a host runs virtual machines that are highly available, power management
must be enabled and configured.
Important:
If you enable or disable Kdump integration on an existing host, you must
reinstall the host.
5-12
Chapter 5
Enabling High-Availability
11. Enter the Port (SSH) number used by the power management device to communicate
with the host.
12. Enter the Slot number used to identify the blade of the power management device.
13. Enter the Options for the power management device. Use a comma-separated list of
key-value pairs.
• If you leave the Options field blank, you are able to use both IPv4 and IPv6
addresses
• To use only IPv4 addresses, enter inet4_only=1
• To use only IPv6 addresses, enter inet6_only=1
14. Check Secure to enable the power management device to connect securely to the host.
You can use ssh, ssl, or any other authentication protocol your power management
device supports.
15. Click Test to ensure the settings are correct and then click OK.
NOT_SUPPORTED:
Power management parameters (userid, password, options, etc.) are tested by
the Manager only during setup and manually after that. If you choose to ignore
alerts about incorrect parameters, or if the parameters are changed on the
power management hardware without changing in the Manager as well, fencing
is likely to fail when most needed.
16. Fence agents are sequential by default. To change the sequence in which the fence
agents are used:
a. Review your fence agent order in the Agents by Sequential Order field.
b. To make two fence agents concurrent, next to one fence agent click the Concurrent
with drop-down list and select the other fence agent.
You can add additional fence agents to this concurrent fence agent group.
17. Expand the Advanced Parameters and use the up and down buttons to specify the
order in which the Manager searches the host’s cluster and dc (data center) for a power
management proxy.
18. To add an additional power management proxy:
a. Click the plus sign (+) next to Add Power Management Proxy.
The Select fence proxy preference type to add pane opens.
b. Select a power management proxy from the drop-down list and then click OK.
5-13
Chapter 5
Installing Additional Self-Hosted Engine Hosts
Your new proxy displays in the Power Management Proxy Preference list.
Note:
By default, the Manager searches for a fencing proxy within the same
cluster as the host. If The Manager cannot find a fencing proxy within the
cluster, it searches the data center.
From the list of hosts, the exclamation mark next to the host’s name disappeared,
signifying that you have successfully configured power management and fencing.
# engine-config -s PMHealthCheckIntervalInSec=number
When set to true, PMHealthCheckEnabled checks all host agents at the interval
specified by PMHealthCheckIntervalInSec and raises warnings if it detects issues.
Important:
Before you begin, refer to Preparing a KVM Host.
5-14
Chapter 5
Cleaning up the Deployment
3. If the deployment failed after the local, temporary hosted engine virtual machine is
created, you might need to clean up the local virtual machine repository:
# rm -rf /var/tmp/localvm*
5-15
6
Deploying GlusterFS Storage
Oracle Linux Virtualization Manager has been integrated with GlusterFS, an open source
scale-out distributed filesystem, 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. In this
scenario, the Manager is run as a self-hosted engine within a virtual machine on these hosts;
although, you can deploy GlusterFS within a standalone environment.
Note:
If you are deploying a self-hosted engine as hyperconverged infrastructure with
GlusterFS storage, you must deploy GlusterFS BEFORE you deploy the self-hosted
engine. For more information about using GlusterFS, including prerequisites, see
the Oracle Linux GlusterFS documentation.
Note:
Ensure that on all three hosts you have installed the following packages:
• cockpit-ovirt-dashboard to provide a UI for installation
• vdsm-gluster to manage gluster services
• ovirt-host on the KVM host used for cockpit deployment
6-1
Chapter 6
Deploying GlusterFS Storage Using Cockpit
9. On the FQDNs screen, enter the FQDN (or IP address) for the hosts to be
managed by the Hosted Engine and click Next when finished.
Note:
The FQDN of the designated server is input during the Hosted Engine
deployment process and is not asked for here.
11. On the Volumes screen, create the minimum storage domains that are required:
engine, data, export, and iso. Click Next when finished.
For example:
engine
• Name: engine
• Volume Type: Replicate (default)
• Arbiter: Ensure the check box is selected.
• Brick Dirs: /gluster_bricks/engine/engine (default)
data
• Name: data
• Volume Type: Replicate (default)
• Arbiter: Ensure the check box is selected.
• Brick Dirs: /gluster_bricks/data/data (default)
export
• Name: export
• Volume Type: Replicate (default)
• Arbiter: Ensure the check box is selected.
• Brick Dirs: /gluster_bricks/export/export (default)
iso
• Name: iso
• Volume Type: Replicate (default)
• Arbiter: Ensure the check box is selected.
• Brick Dirs: /gluster_bricks/iso/iso (default)
12. On the Brick Locations screen, specify the brick locations for your volumes and
click Next when finished.
For this step, you specify the brick locations for your volumes (engine, data,
export, and iso).
13. Review the screen and click Deploy.
• If you are using an internal disk as the Gluster disk, no edits are required and
you can simply click Deploy to continue with the deployment.
6-2
Chapter 6
Creating a GlusterFS Storage Domain Using the Manager
• If you are using an external iSCSI ZFS external drive as the Gluster disk, click Edit to
edit the gdeployConfig.conf file and specify the block device on each server that
is being used for storage. Click Save and then click Deploy to continue with the
deployment.
This process takes some time to complete, as the gdeploy tool installs required packages
and configures Gluster volumes and their underlying storage.
A message display on the screen when the deployment completes successfully.
You can click Tasks to monitor the various processing steps that are completed to add
the GlusterFS storage domain to the data center.
6-3