2.9. External Providers
2.9.1. Introduction to External Providers in Red Hat Virtualization
In addition to resources managed by the Red Hat Virtualization Manager itself, Red Hat Virtualization can also take advantage of resources managed by external sources. The providers of these resources, known as external providers, can provide resources such as virtualization hosts, virtual machine images, and networks.
Red Hat Virtualization currently supports the following external providers:
- Red Hat Satellite for Host Provisioning
- Satellite is a tool for managing all aspects of the life cycle of both physical and virtual hosts. In Red Hat Virtualization, hosts managed by Satellite can be added to and used by the Red Hat Virtualization Manager as virtualization hosts. After you add a Satellite instance to the Manager, the hosts managed by the Satellite instance can be added by searching for available hosts on that Satellite instance when adding a new host. For more information on installing Red Hat Satellite and managing hosts using Red Hat Satellite, see the Red Hat Satellite Quick Start Guide and Red Hat Satellite Managing Hosts.
- KubeVirt/Openshift Virtualization
- Openshift Virtualization (formerly container-native virtualization or "CNV") enables you to bring virtual machines (VMs) into containerized workflows so you can develop, manage, and deploy virtual machines side-by-side with containers and serverless. In RHV Manager, adding this provider is one of the requirements for using Openshift Virtualization. For details, see Adding KubeVirt/Openshift Virtualization as an external provider.
- OpenStack Image Service (Glance) for Image Management
- OpenStack Image Service provides a catalog of virtual machine images. In Red Hat Virtualization, these images can be imported into the Red Hat Virtualization Manager and used as floating disks or attached to virtual machines and converted into templates. After you add an OpenStack Image Service to the Manager, it appears as a storage domain that is not attached to any data center. Virtual disks in a Red Hat Virtualization environment can also be exported to an OpenStack Image Service as virtual disks.
Support for OpenStack Glance is now deprecated. This functionality will be removed in a later release.
- VMware for Virtual Machine Provisioning
-
Virtual machines created in VMware can be converted using V2V (
virt-v2v
) and imported into a Red Hat Virtualization environment. After you add a VMware provider to the Manager, you can import the virtual machines it provides. V2V conversion is performed on a designated proxy host as part of the import operation. - RHEL 5 Xen for Virtual Machine Provisioning
-
Virtual machines created in RHEL 5 Xen can be converted using V2V (
virt-v2v
) and imported into a Red Hat Virtualization environment. After you add a RHEL 5 Xen host to the Manager, you can import the virtual machines it provides. V2V conversion is performed on a designated proxy host as part of the import operation. - KVM for Virtual Machine Provisioning
- Virtual machines created in KVM can be imported into a Red Hat Virtualization environment. After you add a KVM host to the Manager, you can import the virtual machines it provides.
- Open Virtual Network (OVN) for Network Provisioning
-
Open Virtual Network (OVN) is an Open vSwitch (OVS) extension that provides software-defined networks. After you add OVN to the Manager, you can import existing OVN networks, and create new OVN networks from the Manager. You can also automatically install OVN on the Manager using
engine-setup
.
2.9.2. Adding External Providers
2.9.2.1. Adding a Red Hat Satellite Instance for Host Provisioning
Add a Satellite instance for host provisioning to the Red Hat Virtualization Manager. Red Hat Virtualization 4.2 is supported with Red Hat Satellite 6.1.
Procedure
-
Click
. - Click Add.
- Enter a Name and Description.
- Select Foreman/Satellite from the Type drop-down list.
Enter the URL or fully qualified domain name of the machine on which the Satellite instance is installed in the Provider URL text field. You do not need to specify a port number.
ImportantIP addresses cannot be used to add a Satellite instance.
- Select the Requires Authentication check box.
- Enter the Username and Password for the Satellite instance. You must use the same user name and password as you would use to log in to the Satellite provisioning portal.
Test the credentials:
- Click Test to test whether you can authenticate successfully with the Satellite instance using the provided credentials.
- If the Satellite instance uses SSL, the Import provider certificates window opens; click to import the certificate that the Satellite instance provides to ensure the Manager can communicate with the instance.
- Click .
2.9.2.2. Adding an OpenStack Image (Glance) Instance for Image Management
Support for OpenStack Glance is now deprecated. This functionality will be removed in a later release.
Add an OpenStack Image (Glance) instance for image management to the Red Hat Virtualization Manager.
Procedure
-
Click
. - Click Add and enter the details in the General Settings tab. For more information on these fields, see Add Provider General Settings Explained.
- Enter a Name and Description.
- Select OpenStack Image from the Type drop-down list.
- Enter the URL or fully qualified domain name of the machine on which the OpenStack Image instance is installed in the Provider URL text field.
Optionally, select the Requires Authentication check box and enter the Username and Password for the OpenStack Image instance user registered in Keystone. You must also define the authentication URL of the Keystone server by defining the Protocol (must be
HTTP
), Hostname, and API Port.Enter the Tenant for the OpenStack Image instance.
Test the credentials:
- Click Test to test whether you can authenticate successfully with the OpenStack Image instance using the provided credentials.
- If the OpenStack Image instance uses SSL, the Import provider certificates window opens. Click to import the certificate that the OpenStack Image instance provides to ensure the Manager can communicate with the instance.
- Click .
2.9.2.3. Adding KubeVirt/Openshift Virtualization as an external provider
To run virtual machines in a container on the OpenShift Container Platform, you add OpenShift as an external provider in Red Hat Virtualization.
This capability is known as OpenShift Virtualization.
Prerequisites
Procedure
-
In the RHV Administration Portal, go to
and click . - In Add Provider, set Type to KubeVirt/Openshift Virtualization.
- Enter the Provider URL and Token, which are required.
- Optional: Enter values for Advanced parameters such as Certificate Authority, Prometheus URL, and Prometheus Certificate Authority.
- Click to verify the connection to the new provider.
- Click to finish adding this new provider.
Verification steps
-
In the RHV Administration Portal, click
. - Click the name of new cluster you just created. This cluster name, kubevirt for example, is based on the name of the provider. This action opens the cluster details view.
Click the Hosts tab to verify that the status of the OpenShift Container Platform worker nodes is
up
.NoteThe status of the control plane nodes is
down
, even if they are running, because they cannot host virtual machines.-
Use
to deploy a virtual machine to the new cluster. -
In the OpenShift Container Platform web console, in the Administrator perspective, use
to view the virtual machine you deployed.
Additional resources
2.9.2.4. Adding a VMware Instance as a Virtual Machine Provider
Add a VMware vCenter instance to import virtual machines from VMware to the Red Hat Virtualization Manager.
Red Hat Virtualization uses V2V to convert VMware virtual machines to the correct format before they are imported. The virt-v2v
package must be installed on at least one host. The virt-v2v
package is available by default on Red Hat Virtualization Hosts (RHVH) and is installed on Red Hat Enterprise Linux hosts as a dependency of VDSM when added to the Red Hat Virtualization environment. Red Hat Enterprise Linux hosts must be Red Hat Enterprise Linux 7.2 or later.
The virt-v2v
package is not available on ppc64le architecture; these hosts cannot be used as proxy hosts.
Procedure
-
Click
. - Click Add.
- Enter a Name and Description.
- Select VMware from the Type drop-down list.
- Select the Data Center into which VMware virtual machines will be imported, or select Any Data Center to instead specify the destination data center during individual import operations.
- Enter the IP address or fully qualified domain name of the VMware vCenter instance in the vCenter field.
- Enter the IP address or fully qualified domain name of the host from which the virtual machines will be imported in the ESXi field.
- Enter the name of the data center in which the specified ESXi host resides in the Data Center field.
- If you have exchanged the SSL certificate between the ESXi host and the Manager, leave the Verify server’s SSL certificate check box selected to verify the ESXi host’s certificate. If not, clear the check box.
-
Select a host in the chosen data center with
virt-v2v
installed to serve as the Proxy Host during virtual machine import operations. This host must also be able to connect to the network of the VMware vCenter external provider. If you selected Any Data Center above, you cannot choose the host here, but instead can specify a host during individual import operations. - Enter the Username and Password for the VMware vCenter instance. The user must have access to the VMware data center and ESXi host on which the virtual machines reside.
Test the credentials:
- Click Test to test whether you can authenticate successfully with the VMware vCenter instance using the provided credentials.
- If the VMware vCenter instance uses SSL, the Import provider certificates window opens; click to import the certificate that the VMware vCenter instance provides to ensure the Manager can communicate with the instance.
- Click .
To import virtual machines from the VMware external provider, see Importing a Virtual Machine from a VMware Provider in the Virtual Machine Management Guide.
2.9.2.5. Adding a RHEL 5 Xen Host as a Virtual Machine Provider
Add a RHEL 5 Xen host to import virtual machines from Xen to Red Hat Virtualization.
Red Hat Virtualization uses V2V to convert RHEL 5 Xen virtual machines to the correct format before they are imported. The virt-v2v
package must be installed on at least one host. The virt-v2v
package is available by default on Red Hat Virtualization Hosts (RHVH) and is installed on Red Hat Enterprise Linux hosts as a dependency of VDSM when added to the Red Hat Virtualization environment. Red Hat Enterprise Linux hosts must be Red Hat Enterprise Linux 7.2 or later.
The virt-v2v
package is not available on ppc64le architecture; these hosts cannot be used as proxy hosts.
Procedure
Enable public key authentication between the proxy host and the RHEL 5 Xen host:
Log in to the proxy host and generate SSH keys for the vdsm user.
# sudo -u vdsm ssh-keygen
Copy the vdsm user’s public key to the RHEL 5 Xen host. The proxy host’s known_hosts file will also be updated to include the host key of the RHEL 5 Xen host.
# sudo -u vdsm ssh-copy-id root@xenhost.example.com
Log in to the RHEL 5 Xen host to verify that the login works correctly.
# sudo -u vdsm ssh root@xenhost.example.com
-
Click
. - Click Add.
- Enter a Name and Description.
- Select XEN from the Type drop-down list.
- Select the Data Center into which Xen virtual machines will be imported, or select Any Data Center to specify the destination data center during individual import operations.
- Enter the URI of the RHEL 5 Xen host in the URI field.
-
Select a host in the chosen data center with
virt-v2v
installed to serve as the Proxy Host during virtual machine import operations. This host must also be able to connect to the network of the RHEL 5 Xen external provider. If you selected Any Data Center above, you cannot choose the host here, but instead can specify a host during individual import operations. - Click Test to test whether you can authenticate successfully with the RHEL 5 Xen host.
- Click .
To import virtual machines from a RHEL 5 Xen external provider, see Importing a Virtual Machine from a RHEL 5 Xen Host in the Virtual Machine Management Guide.
2.9.2.6. Adding a KVM Host as a Virtual Machine Provider
Add a KVM host to import virtual machines from KVM to Red Hat Virtualization Manager.
Procedure
Enable public key authentication between the proxy host and the KVM host:
Log in to the proxy host and generate SSH keys for the vdsm user.
# sudo -u vdsm ssh-keygen
Copy the vdsm user’s public key to the KVM host. The proxy host’s known_hosts file will also be updated to include the host key of the KVM host.
# sudo -u vdsm ssh-copy-id root@kvmhost.example.com
Log in to the KVM host to verify that the login works correctly.
# sudo -u vdsm ssh root@kvmhost.example.com
-
Click
. - Click Add.
- Enter a Name and Description.
- Select KVM from the Type drop-down list.
- Select the Data Center into which KVM virtual machines will be imported, or select Any Data Center to specify the destination data center during individual import operations.
Enter the URI of the KVM host in the URI field.
qemu+ssh://root@host.example.com/system
- Select a host in the chosen data center to serve as the Proxy Host during virtual machine import operations. This host must also be able to connect to the network of the KVM external provider. If you selected Any Data Center in the Data Center field above, you cannot choose the host here. The field is greyed out and shows Any Host in Data Center. Instead you can specify a host during individual import operations.
- Optionally, select the Requires Authentication check box and enter the Username and Password for the KVM host. The user must have access to the KVM host on which the virtual machines reside.
- Click Test to test whether you can authenticate successfully with the KVM host using the provided credentials.
- Click .
To import virtual machines from a KVM external provider, see Importing a Virtual Machine from a KVM Host in the Virtual Machine Management Guide.
2.9.2.7. Adding Open Virtual Network (OVN) as an External Network Provider
You can use Open Virtual Network (OVN) to create overlay virtual networks that enable communication among the virtual machines without adding VLANs or changing the infrastructure. OVN is an extension of Open vSwitch (OVS) that provides native support for virtual L2 and L3 overlays.
You can also connect an OVN network to a native Red Hat Virtualization network. See Connecting an OVN Network to a Physical Network for more information. This feature is available as a Technology Preview only.
The ovirt-provider-ovn
exposes an OpenStack Networking REST API. You can use this API to create networks, subnets, ports, and routers. For details, see OpenStack Networking API v2.0.
For more details, see the Open vSwitch Documentation and Open vSwitch Manpages.
2.9.2.7.1. Installing a New OVN Network Provider
Installing OVN using engine-setup
performs the following steps:
- Sets up an OVN central server on the Manager machine.
- Adds OVN to Red Hat Virtualization as an external network provider.
-
On the Default cluster only, sets the Default Network Provider to
ovirt-provider-ovn
.
- Installing OVN changes the Default Network Provider setting on the Default cluster only, not on other clusters.
- Changing the Default Network Provider setting does not update hosts in that cluster to use the Default Network Provider.
- For hosts and virtual machines to use OVN, perform the addition tasks described in the "Next steps" at the end of this topic.
Procedure
Optional: If you use a preconfigured answer file with
engine-setup
, add the following entry to install OVN:OVESETUP_OVN/ovirtProviderOvn=bool:True
-
Run
engine-setup
on the Manager machine. If you do not use a preconfigured answer file, answer
Yes
when theengine-setup
asks: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]:
Answer the following question:
Use default credentials (admin@internal) for ovirt-provider-ovn (Yes, No) [Yes]?:
If
Yes
,engine-setup
uses the default engine user and password specified earlier in the setup process. This option is only available during new installations.oVirt OVN provider user[admin]: oVirt OVN provider password[empty]:
You can use the default values or specify the oVirt OVN provider user and password.
To change the authentication method later, you can edit the /etc/ovirt-provider-ovn/conf.d/10_engine_setup.conf
file, or create a new /etc/ovirt-provider-ovn/conf.d/20_engine_setup.conf
file. Restart the ovirt-provider-ovn
service for the change to take effect. See oVirt external network provider for OVN for more information about OVN authentication.
Next steps
Before you can create virtual machines that use a newly-installed OVN network, complete these additional steps:
Add a network to the Default cluster.
-
While doing so, select the Create on external provider check box. This creates a network based on
ovirt-provider-ovn
. - Optional: To connect the OVN network to a physical network, select the Connect to physical network check box and specify the Red Hat Virtualization network to use.
- Optional: Determine whether the network should use a security group and select one from the Security Groups drop-down. For more information on the available options see Logical Network General Settings Explained.
-
While doing so, select the Create on external provider check box. This creates a network based on
-
Add hosts to or reinstall the hosts on the Default cluster so they use the cluster’s new Default Network Provider,
ovirt-provider-ovn
. Optional: Edit non-Default clusters and set Default Network Provider to
ovirt-provider-ovn
.-
Optional: Reinstall the hosts on each non-Default cluster so they use the cluster’s new Default Network Provider,
ovirt-provider-ovn
.
-
Optional: Reinstall the hosts on each non-Default cluster so they use the cluster’s new Default Network Provider,
Additional resources
- To configure your hosts to use an existing, non-default network, see Configuring Hosts for an OVN tunnel network.
2.9.2.7.2. Updating the OVN Tunnel Network on a Single Host
You can update the OVN tunnel network on a single host with vdsm-tool
:
# vdsm-tool ovn-config OVN_Central_IP Tunneling_IP_or_Network_Name Host_FQDN
The Host_FQDN must match the FQDN that is specified in the engine for this host.
Example 2.4. Updating a Host with vdsm-tool
# vdsm-tool ovn-config 192.168.0.1 MyNetwork MyFQDN
2.9.2.7.3. Connecting an OVN Network to a Physical Network
This feature relies on Open vSwitch support, which is available only as a Technology Preview in Red Hat Virtualization. Technology Preview features are not supported with Red Hat production service level agreements (SLAs), might not be functionally complete, and Red Hat does not recommend using them for production. These features provide early access to upcoming product features, enabling customers to test functionality and provide feedback during the development process.
For more information on Red Hat Technology Preview features support scope, see Technology Preview Features Support Scope.
You can create an external provider network that overlays a native Red Hat Virtualization network so that the virtual machines on each appear to be sharing the same subnet.
If you created a subnet for the OVN network, a virtual machine using that network will receive an IP address from there. If you want the physical network to allocate the IP address, do not create a subnet for the OVN network.
Prerequisites
- The cluster must have OVS selected as the Switch Type. Hosts added to this cluster must not have any pre-existing Red Hat Virtualization networks configured, such as the ovirtmgmt bridge.
- The physical network must be available on the hosts. You can enforce this by setting the physical network as required for the cluster (in the Manage Networks window, or the Cluster tab of the New Logical Network window).
Procedure
-
Click
. - Click the cluster’s name. This opens the details view.
- Click the Logical Networks tab and click Add Network.
- Enter a Name for the network.
-
Select the Create on external provider check box.
ovirt-provider-ovn
is selected by default. - Select the Connect to physical network check box if it is not already selected by default.
Choose the physical network to connect the new network to:
- Click the Data Center Network radio button and select the physical network from the drop-down list. This is the recommended option.
Click the Custom radio button and enter the name of the physical network. If the physical network has VLAN tagging enabled, you must also select the Enable VLAN tagging check box and enter the physical network’s VLAN tag.
ImportantThe physical network’s name must not be longer than 15 characters, or contain special characters.
- Click .
////Removing for BZ2006228 include::topics/Adding_an_External_Network_Provider.adoc[leveloffset=+2]
2.9.2.8. Add Provider General Settings Explained
The General tab in the Add Provider window allows you to register the core details of the external provider.
Setting | Explanation |
---|---|
Name | A name to represent the provider in the Manager. |
Description | A plain text, human-readable description of the provider. |
Type | The type of external provider. Changing this setting alters the available fields for configuring the provider. External Network Provider
Foreman/Satellite
KubeVirt/OpenShift Virtualization
OpenStack Image
OpenStack Volume
VMware
RHEL 5 Xen
KVM
|
Test | Allows users to test the specified credentials. This button is available to all provider types. |
2.9.3. Editing an External Provider
Procedure
-
Click
and select the external provider to edit. - Click Edit.
- Change the current values for the provider to the preferred values.
- Click .
2.9.4. Removing an External Provider
Procedure
-
Click
and select the external provider to remove. - Click Remove.
- Click .