1. Click Administration → Providers.
2. Click Add.
3. Enter a Name and Description.
4. Select Foreman/Satellite from the Type drop-down list.

5. 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.

   Important

   IP addresses cannot be used to add a Satellite instance.

6. Select the Requires Authentication check box.
7. 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.

8. Test the credentials:

   1. Click Test to test whether you can authenticate successfully with the Satellite instance using the provided credentials.
   2. If the Satellite instance uses SSL, the Import provider certificates window opens; click OK to import the certificate that the Satellite instance provides to ensure the Manager can communicate with the instance.
9. Click OK.

1. Click Administration → Providers.
2. Click Add and enter the details in the General Settings tab. For more information on these fields, see Section 14.2.11, “Add Provider General Settings Explained”.
3. Enter a Name and Description.
4. Select OpenStack Image from the Type drop-down list.
5. 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.

6. 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.

7. Test the credentials:

   1. Click Test to test whether you can authenticate successfully with the OpenStack Image instance using the provided credentials.
   2. If the OpenStack Image instance uses SSL, the Import provider certificates window opens. Click OK to import the certificate that the OpenStack Image instance provides to ensure the Manager can communicate with the instance.
8. Click OK.

Adding a Network Node as a Host

1. Use the Red Hat OpenStack Platform director to deploy the Networker role on the network node. See Creating a New Role and Networker in the Red Hat OpenStack Platform Advanced Overcloud Customization Guide.

2. Enable the required repositories:

   1. Register your system with the Content Delivery Network, entering your Customer Portal user name and password when prompted:

      # subscription-manager register

   2. Find the Red Hat Enterprise Linux Server and Red Hat Virtualization subscription pools and record the pool IDs:

      # subscription-manager list --available

   3. Use the pool IDs to attach the subscriptions to the system:

      # subscription-manager attach --pool=poolid

   4. Configure the repositories:

      # subscription-manager repos \
          --disable='*' \
          --enable=rhel-7-server-rpms \
          --enable=rhel-7-server-rhv-4-mgmt-agent-rpms \
          --enable=rhel-7-server-ansible-2.9-rpms

   5. Ensure that all packages currently installed are up to date:

      # yum update

   6. Reboot the machine if any kernel packages were updated.

3. Install the Openstack Networking hook:

   # yum install vdsm-hook-openstacknet

4. Add the network node to the Manager as a host. See Section 10.5.1, “Adding Standard Hosts to the Red Hat Virtualization Manager”.

   Important

   Do not select the OpenStack Networking provider from the Network Provider tab. This is currently not supported.

5. Remove the firewall rule that rejects ICMP traffic:

   # iptables -D INPUT -j REJECT --reject-with icmp-host-prohibited

1. Click Administration → Providers.
2. Click Add and enter the details in the General Settings tab. For more information on these fields, see Section 14.2.11, “Add Provider General Settings Explained”.
3. Enter a Name and Description.
4. Select OpenStack Networking from the Type drop-down list.
5. Ensure that Open vSwitch is selected in the Networking Plugin field.
6. Optionally, select the Automatic Synchronization check box. This enables automatic synchronization of the external network provider with existing networks.

7. Enter the URL or fully qualified domain name of the machine on which the OpenStack Networking instance is installed in the Provider URL text field, followed by the port number. The Read-Only check box is selected by default. This prevents users from modifying the OpenStack Networking instance.

   Important

   You must leave the Read-Only check box selected for your setup to be supported by Red Hat.

8. Optionally, select the Requires Authentication check box and enter the Username and Password for the OpenStack Networking user registered in Keystone. You must also define the authentication URL of the Keystone server by defining the Protocol, Hostname, API Port, and API Version.

   For API version 2.0, enter the Tenant for the OpenStack Networking instance. For API version 3, enter the User Domain Name, Project Name, and Project Domain Name.

9. Test the credentials:

   1. Click Test to test whether you can authenticate successfully with the OpenStack Networking instance using the provided credentials.
   2. If the OpenStack Networking instance uses SSL, the Import provider certificates window opens; click OK to import the certificate that the OpenStack Networking instance provides to ensure the Manager can communicate with the instance.

10. Click the Agent Configuration tab.

    Warning

    The following steps are provided only as a Technology Preview. Red Hat Virtualization only supports preconfigured neutron hosts.

11. Enter a comma-separated list of interface mappings for the Open vSwitch agent in the Interface Mappings field.
12. Select the message broker type that the OpenStack Networking instance uses from the Broker Type list.
13. Enter the URL or fully qualified domain name of the host on which the message broker is hosted in the Host field.
14. Enter the Port by which to connect to the message broker. This port number will be 5762 by default if the message broker is not configured to use SSL, and 5761 if it is configured to use SSL.
15. Enter the Username and Password of the OpenStack Networking user registered in the message broker instance.
16. Click OK.

1. Click Administration → Providers.
2. Click Add and enter the details in the General Settings tab. For more information on these fields, see Section 14.2.11, “Add Provider General Settings Explained”.
3. Enter a Name and Description.
4. Select OpenStack Block Storage from the Type drop-down list.
5. Select the Data Center to which OpenStack Block Storage volumes will be attached.
6. Enter the URL or fully qualified domain name of the machine on which the OpenStack Block Storage instance is installed, followed by the port number, in the Provider URL text field.

7. Optionally, select the Requires Authentication check box and enter the Username and Password for the OpenStack Block Storage instance user registered in Keystone. 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 Block Storage instance.

8. Click Test to test whether you can authenticate successfully with the OpenStack Block Storage instance using the provided credentials.
9. Click OK.

10. If client Ceph authentication (cephx) is enabled, you must also complete the following steps. The cephx protocol is enabled by default.

    1. On your Ceph server, create a new secret key for the client.cinder user using the ceph auth get-or-create command. See Cephx Configuration Reference for more information on cephx, and Managing Users for more information on creating keys for new users. If a key already exists for the client.cinder user, retrieve it using the same command.
    2. In the Administration Portal, select the newly created Cinder external provider from the Providers list.
    3. Click the Authentication Keys tab.
    4. Click New.
    5. Enter the secret key in the Value field.
    6. Copy the automatically generated UUID, or enter an existing UUID in the text field.

    7. On your Cinder server, add the UUID from the previous step and the cinder user to /etc/cinder/cinder.conf:

       rbd_secret_uuid = UUID
       rbd_user = cinder

Procedure

1. In the RHV Administration Portal, go to Administration → Providers and click New.
2. In Add Provider, set Type to KubeVirt/Openshift Virtualization.
3. Enter the Provider URL and Token, which are required.
4. Optional: Enter values for Advanced parameters such as Certificate Authority, Prometheus URL, and Prometheus Certificate Authority.
5. Click Test to verify the connection to the new provider.
6. Click OK to finish adding this new provider.

Verification steps

1. In the RHV Administration Portal, click Compute → Clusters.
2. 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.

3. Click the Hosts tab to verify that the OpenShift Container Platform status of the worker nodes is up.

   Note

   Even if they are running, the status of the master nodes is down because they cannot host virtual machines.

4. Use Compute → Virtual Machines to deploy a virtual machine to the new cluster.
5. In the OpenShift Container Platform web console, in the Administrator perspective, use Workloads → Virtual Machines to view the virtual machine you deployed.

1. Click Administration → Providers.
2. Click Add.
3. Enter a Name and Description.
4. Select VMware from the Type drop-down list.
5. 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.
6. Enter the IP address or fully qualified domain name of the VMware vCenter instance in the vCenter field.
7. Enter the IP address or fully qualified domain name of the host from which the virtual machines will be imported in the ESXi field.
8. Enter the name of the data center in which the specified ESXi host resides in the Data Center field.
9. 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.
10. 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.
11. 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.

12. Test the credentials:

    1. Click Test to test whether you can authenticate successfully with the VMware vCenter instance using the provided credentials.
    2. If the VMware vCenter instance uses SSL, the Import provider certificates window opens; click OK to import the certificate that the VMware vCenter instance provides to ensure the Manager can communicate with the instance.
13. Click OK.

1. Enable public key authentication between the proxy host and the RHEL 5 Xen host:

   1. Log in to the proxy host and generate SSH keys for the vdsm user.

      # sudo -u vdsm ssh-keygen

   2. 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

   3. Log in to the RHEL 5 Xen host to verify that the login works correctly.

      # sudo -u vdsm ssh root@xenhost.example.com

2. Click Administration → Providers.
3. Click Add.
4. Enter a Name and Description.
5. Select XEN from the Type drop-down list.
6. 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.
7. Enter the URI of the RHEL 5 Xen host in the URI field.
8. 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.
9. Click Test to test whether you can authenticate successfully with the RHEL 5 Xen host.
10. Click OK.

1. Enable public key authentication between the proxy host and the KVM host:

   1. Log in to the proxy host and generate SSH keys for the vdsm user.

      # sudo -u vdsm ssh-keygen

   2. 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

   3. Log in to the KVM host to verify that the login works correctly.

      # sudo -u vdsm ssh root@kvmhost.example.com

2. Click Administration → Providers.
3. Click Add.
4. Enter a Name and Description.
5. Select KVM from the Type drop-down list.
6. 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.

7. Enter the URI of the KVM host in the URI field.

   qemu+ssh://root@host.example.com/system

8. 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.
9. 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.
10. Click Test to test whether you can authenticate successfully with the KVM host using the provided credentials.
11. Click OK.

1. Click Administration → Providers.
2. Click Add and enter the details in the General Settings tab. For more information on these fields, see Section 14.2.11, “Add Provider General Settings Explained”.
3. Enter a Name and Description.
4. Select External Network Provider from the Type drop-down list.
5. Optionally, click the Networking Plugin text box and select the appropriate driver from the drop-down menu.

6. Optionally, select the Automatic Synchronization check box. This enables automatic synchronization of the external network provider with existing networks. This feature is disabled by default when adding external network providers.

   Note

   Automatic synchronization is enabled by default on the ovirt-provider-ovn network provider created by the engine-setup tool.

7. Enter the URL or fully qualified domain name of the machine on which the external network provider is installed in the Provider URL text field, followed by the port number. The Read-Only check box is selected by default. This prevents users from modifying the external network provider.

   Important

   You must leave the Read-Only check box selected for your setup to be supported by Red Hat.

8. Optionally, select the Requires Authentication check box and enter the Username and Password for the external network provider user registered in Keystone. You must also define the authentication URL of the Keystone server by defining the Protocol, Hostname, and API Port.

   Optionally, enter the Tenant for the external network provider.

9. Test the credentials:

   1. Click Test to test whether you can authenticate successfully with the external network provider using the provided credentials.
   2. If the external network provider uses SSL, the Import provider certificates window opens; click OK to import the certificate that the external network provider provides to ensure the Manager can communicate with the instance.
10. Click OK.