12.2. Adding External Providers

Procedure 12.1. Adding a Satellite Instance for Host Provisioning

1. Select the External Providers entry in the tree pane.
2. Click Add to open the Add Provider window.
   

   Figure 12.1. The Add Provider Window

3. Enter a Name and Description.
4. From the Type list, ensure that Foreman/Satellite is selected.
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. 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.
7. 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.

      Important

      You must import the certificate that the Satellite instance provides to ensure the Manager can communicate with the instance.
8. Click OK.

Procedure 12.2. Adding an OpenStack Image (Glance) Instance for Image Management

1. Select the External Providers entry in the tree pane.
2. Click Add to open the Add Provider window.
   

   Figure 12.2. The Add Provider Window

3. Enter a Name and Description.
4. From the Type list, select OpenStack Image.
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, Password, Tenant Name, and Authentication URL for the OpenStack Image instance. You must use the user name and password for the OpenStack Image user registered in Keystone, the tenant of which the OpenStack Image instance is a member, and the URL and port of the Keystone server.
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.

      Important

      You must import the certificate that the OpenStack Image instance provides to ensure the Manager can communicate with the instance.
8. Click OK.

Procedure 12.3. Adding an OpenStack Networking (Neutron) Instance for Network Provisioning

1. Select the External Providers entry in the tree pane.
2. Click Add to open the Add Provider window.
   

   Figure 12.3. The Add Provider Window

3. Enter a Name and Description.
4. From the Type list, select OpenStack Networking.
5. Ensure that Open vSwitch is selected in the Networking Plugin field.
6. 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.
7. Optionally, select the Requires Authentication check box and enter the Username, Password, Tenant Name, and Authentication URL for the OpenStack Networking instance. You must use the user name and password for the OpenStack Networking user registered in Keystone, the tenant of which the OpenStack Networking instance is a member, and the URL and port of the Keystone server.
8. 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.

   Warning

   The following steps are provided only as a Technology Preview. Red Hat Virtualization only supports preconfigured Neutron hosts.
9. Click the Agent Configuration tab.
   

   Figure 12.4. The Agent Configuration Tab

10. Enter a comma-separated list of interface mappings for the Open vSwitch agent in the Interface Mappings field.
11. Select the message broker type that the OpenStack Networking instance uses from the Broker Type list.
12. Enter the URL or fully qualified domain name of the host on which the message broker is hosted in the Host field.
13. 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.
14. Enter the Username and Password of the OpenStack Networking user registered in the message broker instance.
15. Click OK.

Procedure 12.4. Adding an OpenStack Volume (Cinder) Instance for Storage Management

1. Select the External Providers entry in the tree pane.
2. Click Add to open the Add Provider window.
   

   Figure 12.5. The Add Provider Window

3. Enter a Name and Description.
4. From the Type list, select OpenStack Volume.
5. Select the Data Center to which OpenStack Volume storage volumes will be attached.
6. Enter the URL or fully qualified domain name of the machine on which the OpenStack Volume 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, Password, Tenant Name, and Authentication URL for the OpenStack Volume instance. You must use the user name and password for the OpenStack Volume user registered in Keystone, the tenant of which the OpenStack Volume instance is a member, and the URL, port, and API version of the Keystone server.
8. Click Test to test whether you can authenticate successfully with the OpenStack Volume 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 Config 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 sub-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 12.5. Adding a VMware vCenter Instance as a Virtual Machine Provider

1. Select the External Providers entry in the tree pane.
2. Click Add to open the Add Provider window.
   

   Figure 12.6. The Add Provider Window

3. Enter a Name and Description.
4. From the Type list, select VMware.
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 (using the Import function in the Virtual Machines tab).
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 Verify server's SSL certificate checked to verify the ESXi host's certificate. If not, uncheck the option.
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 (using the Import function in the Virtual Machines tab).
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.

       Important

       You must import the certificate that the VMware vCenter instance provides to ensure the Manager can communicate with the instance.
13. Click OK.

Procedure 12.6. Adding an External Network Provider for Network Provisioning

1. Select the External Providers entry in the tree pane.
2. Click Add.
   

   Figure 12.7. The Add Provider Window

3. Enter a Name and Description.
4. From the Type list, select External Network Provider.
5. 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.
6. Optionally, select the Requires Authentication check box and enter the Username, Password, Tenant Name, and Authentication URL for the external network provider.
7. 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.