12.2. Adding External Providers

12.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.1 is supported with Red Hat Satellite 6.1.

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.
    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.
You have added the Satellite instance to the Red Hat Virtualization Manager, and can work with the hosts it provides.

12.2.2. Adding an OpenStack Image (Glance) Instance for Image Management

Add an OpenStack Image (Glance) instance for image management to the Red Hat Virtualization Manager.

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.
    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.
You have added the OpenStack Image instance to the Red Hat Virtualization Manager, and can work with the images it provides.

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

Add an OpenStack Networking (neutron) instance for network provisioning to the Red Hat Virtualization Manager. To add other third-party network providers that implement the OpenStack Neutron REST API, see Section 12.2.8, “Adding an External Network Provider”.
To use neutron networks, hosts must have the neutron agents configured. You can configure the agents manually, or use the Red Hat OpenStack Platform director to deploy the Networker role, before adding the network node to the Manager as a host. Using the director is recommended; see Section 7.5.4, “Adding a Red Hat OpenStack Platform Network Node as a Host”. Automatic deployment of the neutron agents through the Network Provider tab in the New Host window is not supported.

Important

Red Hat Virtualization supports Red Hat OpenStack Platform 8, 9, and 10 as external network providers.

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.
    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.
    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.
You have added the OpenStack Networking instance to the Red Hat Virtualization Manager. Before you can use the networks it provides, import the networks into the Manager. See Section 6.3.1, “Importing Networks From External Providers”.

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

Important

Using an OpenStack Volume (Cinder) instance for storage management is a Technology Preview feature only. 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 to use 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 https://access.redhat.com/support/offerings/techpreview/.
Add an OpenStack Volume (Cinder) instance for storage management to the Red Hat Virtualization Manager. The OpenStack Cinder volumes are provisioned by Ceph Storage.

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.
    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
You have added the OpenStack Volume instance to the Red Hat Virtualization Manager, and can work with the storage volumes it provides. See Section 11.6.1, “Creating a Virtual Disk” for more information about creating a OpenStack Volume (Cinder) disk.

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

Note

The virt-v2v package is not available on the ppc64le architecture and these hosts cannot be used as proxy hosts.

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.
    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.
You have added the VMware vCenter instance to the Red Hat Virtualization Manager, and can import the virtual machines it provides. See Importing a Virtual Machine from a VMware Provider in the Virtual Machine Management Guide for more information.

12.2.6. Adding a Xen Host as a Virtual Machine Provider

Add a Xen host to import virtual machines from Xen to Red Hat Virtualization Manager.
Red Hat Virtualization uses V2V to convert 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.

Note

The virt-v2v package is not available on the ppc64le architecture and these hosts cannot be used as proxy hosts.

Procedure 12.6. Adding a Xen Instance as a Virtual Machine Provider

  1. Enable public key authentication between the proxy host and the 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 Xen host. The proxy host's known_hosts file will also be updated to include the host key of the Xen host.
      # sudo -u vdsm ssh-copy-id root@xenhost.example.com
    3. Log in to the Xen host to verify that the login works correctly.
      # sudo -u vdsm ssh root@xenhost.example.com
  2. Select the External Providers entry in the tree pane.
  3. Click Add to open the Add Provider window.
    The Add Provider Window

    Figure 12.7. The Add Provider Window

  4. Enter a Name and Description.
  5. From the Type list, select XEN.
  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 (using the Import function in the Virtual Machines tab).
  7. Enter the URI 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 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 (using the Import function in the Virtual Machines tab).
  9. Click Test to test whether you can authenticate successfully with the Xen host.
  10. Click OK.
You have added the Xen host to Red Hat Virtualization Manager, and can import the virtual machines it provides. See Importing a Virtual Machine from a Xen Host in the Virtual Machine Management Guide for more information.

12.2.7. 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 12.7. Adding a KVM Host as a Virtual Machine Provider

  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. Select the External Providers entry in the tree pane.
  3. Click Add to open the Add Provider window.
    The Add Provider Window

    Figure 12.8. The Add Provider Window

  4. Enter a Name and Description.
  5. From the Type list, select KVM.
  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 (using the Import function in the Virtual Machines tab).
  7. Enter the URI in the URI field.
  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 (using the Import function in the Virtual Machines tab).
  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.
You have added the KVM host to Red Hat Virtualization Manager, and can import the virtual machines it provides. See Importing a Virtual Machine from a KVM Host in the Virtual Machine Management Guide for more information.

12.2.8. Adding an External Network Provider

Any network provider that implements the OpenStack Neutron REST API can be added to Red Hat Virtualization. The virtual interface driver needs to be provided by the implementer of the external network provider. A reference implementation of a network provider and a virtual interface driver are available at https://github.com/mmirecki/ovirt-provider-mock and https://github.com/mmirecki/ovirt-provider-mock/blob/master/docs/driver_instalation.

Procedure 12.8. Adding an External Network Provider for Network Provisioning

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

    Figure 12.9. 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.
  8. Click OK.
You have added an external networking provider to the Red Hat Virtualization Manager. Before you can use the networks it provides, you need to install the virtual interface driver on the hosts and import the networks. To import networks, see Section 6.3.1, “Importing Networks From External Providers”.

12.2.9. Adding Open Virtual Network (OVN) as an External Network Provider

Important

Using Open Virtual Network (OVN) as an external network provider is a Technology Preview feature only. 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 to use 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 https://access.redhat.com/support/offerings/techpreview/.
Open Virtual Network (OVN) is an Open vSwitch (OVS) extension that enables support for virtual networks abstraction by adding native OVS support for virtual L2 and L3 overlays. By adding an OVN external network provider, you can import existing OVN networks to Red Hat Virtualization, and add new OVN networks from the Manager without needing to make VLAN requests or infrastructure changes to the network provider (the OVN central server).
For more information on OVS and OVN, see the OVS documentation at http://docs.openvswitch.org/en/latest/ and http://openvswitch.org/support/dist-docs/.
Adding OVN as an external network provider in Red Hat Virtualization involves the following key steps:
  • Install the OVN virtual interface driver on any hosts to which you want to add OVN networks. The virtual interface driver connects vNICs to the appropriate OVS bridge and OVN logical network.
  • Install the OVN provider, a proxy used by the Manager to interact with OVN. The OVN provider can be installed on any machine, but must be able to communicate with the OVN central server and the Manager.
  • Add the OVN provider to Red Hat Virtualization as an external network provider.
This procedure assumes you have an existing OVN central server. The OVN central server can be on the same machine as the Red Hat Virtualization Manager, or on a separate machine.

Prerequisites

  • The following packages are required by the OVN virtual interface driver and must be available on the hosts:
    • openvswitch-ovn-host
    • openvswitch
    • openvswitch-ovn-common
    • python-openvswitch
  • The following packages are required by the OVN provider and must be available on the provider machine:
    • openvswitch-ovn-central
    • openvswitch
    • openvswitch-ovn-common
    • python-openvswitch
If these packages are not available from the repositories already enabled on each machine, they can be downloaded from the OVS website: http://openvswitch.org/download/.

Procedure 12.9. Adding Open Virtual Network (OVN) as an External Network Provider

  1. Install and configure the OVN virtual interface driver on any hosts to which you want to add OVN networks.
    1. Install the driver:
      • On a RHEL host:
        # yum install ovirt-provider-ovn-driver
      • On Red Hat Virtualization Host (RHVH), the RPM must be manually built and installed:
        # git clone https://gerrit.ovirt.org/ovirt-provider-ovn
        # cd ovirt-provider-ovn
        # make rpm
        # cd
        # yum install rpmbuild/RPMS/noarch/ovirt-provider-ovn-driver-version.noarch.rpm
    2. Start and enable the service:
      # systemctl start ovn-controller
      # systemctl enable ovn-controller
    3. Configure the service:
      # vdsm-tool ovn-config OVN_central_server_IP local_OVN_tunneling_IP
      The local IP address used for OVN tunneling must be reachable by the OVN central server and by other hosts using OVN. It can be the ovirtmgmt interface on the host.
    4. Open port 6081 in the firewall. This can be done either manually or by adding ovn-host-firewall-service to the appropriate zone:
      # firewall-cmd --zone=ZoneName --add-service=ovn-host-firewall-service --permanent
      # firewall-cmd --reload
  2. Install and configure the OVN provider.
    1. Install the provider:
      • If you are installing the provider on the same machine as the Manager:
        # yum install ovirt-provider-ovn
      • If you are not installing the provider on the same machine as the Manager, the RPM must be manually built and installed:
        # git clone https://gerrit.ovirt.org/ovirt-provider-ovn
        # cd ovirt-provider-ovn
        # make rpm
        # cd
        # yum install rpmbuild/RPMS/noarch/ovirt-provider-ovn-version.noarch.rpm
    2. If you are not installing the provider on the same machine as the OVN central server, add the following entry to the /etc/ovirt-provider-ovn/ovirt-provider-ovn.conf file:
      ovn-remote=tcp:OVN_central_server_IP:6641
    3. Open ports 9696, 6641, and 6642 in the firewall to allow communication between the OVN provider, the OVN central server, and the Manager. This can be done either manually or by adding the ovirt-provider-ovn and ovirt-provider-ovn-central services to the appropriate zone:
      # firewall-cmd --zone=ZoneName --add-service=ovirt-provider-ovn --permanent
      # firewall-cmd --zone=ZoneName --add-service=ovirt-provider-ovn-central --permanent
      # firewall-cmd --reload
    4. Start and enable the service:
      # systemctl start ovirt-provider-ovn
      # systemctl enable ovirt-provider-ovn
    5. Configure the OVN central server to listen to requests from ports 6642 and 6641:
      # ovn-sbctl set-connection ptcp:6642
      # ovn-nbctl set-connection ptcp:6641
  3. In the Administration Portal, select the External Providers entry in the tree pane.
  4. Click Add.
    The Add Provider Window

    Figure 12.10. The Add Provider Window

  5. Enter a Name and Description.
  6. From the Type list, select External Network Provider.
  7. Enter the URL or fully qualified domain name of the OVN provider in the Provider URL text field, followed by the port number. If the OVN provider and the OVN central server are on separate machines, this is the URL of the provider machine, not the central server. If the OVN provider is on the same machine as the Manager, the URL can remain the default http://localhost:9696.
  8. Clear the Read-Only check box to allow creating new OVN networks from the Red Hat Virtualization Manager.
  9. Clear the Requires Authentication check box. Authentication and SSL are currently not supported for OVN external network providers.
  10. Click OK.
You have added an OVN network provider to the Red Hat Virtualization Manager. To import networks, see Section 6.3.1, “Importing Networks From External Providers”. To create new networks using OVN, see Section 6.1.2, “Creating a New Logical Network in a Data Center or Cluster” and use the Create on external provider option.

12.2.10. Add Provider General Settings Explained

The General tab in the Add Provider window allows you to register the core details of the external provider.

Table 12.1. Add Provider: General Settings

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.
Foreman/Satellite
  • Provider URL: The URL or fully qualified domain name of the machine that hosts the Satellite instance. You do not need to add the port number to the end of the URL or fully qualified domain name.
  • Requires Authentication: Allows you to specify whether authentication is required for the provider. Authentication is mandatory when Foreman/Satellite is selected.
  • Username: A user name for connecting to the Satellite instance. This user name must be the user name used to log in to the provisioning portal on the Satellite instance. By default, this user name is admin.
  • Password: The password against which the above user name is to be authenticated. This password must be the password used to log in to the provisioning portal on the Satellite instance.
OpenStack Image
  • Provider URL: The URL or fully qualified domain name of the machine on which the OpenStack Image service is hosted. You must add the port number for the OpenStack Image service to the end of the URL or fully qualified domain name. By default, this port number is 9292.
  • Requires Authentication: Allows you to specify whether authentication is required to access the OpenStack Image service.
  • Username: A user name for connecting to the OpenStack Image service. This user name must be the user name for the OpenStack Image service registered in the Keystone instance of which the OpenStack Image service is a member. By default, this user name is glance.
  • Password: The password against which the above user name is to be authenticated. This password must be the password for the OpenStack Image service registered in the Keystone instance of which the OpenStack Image service is a member.
  • Tenant Name: The name of the OpenStack tenant of which the OpenStack Image service is a member. By default, this is services.
  • Authentication URL: The URL and port of the Keystone server with which the OpenStack Image service authenticates.
OpenStack Networking
  • Networking Plugin: The networking plugin with which to connect to the OpenStack Networking server. Open vSwitch is the only option, and is selected by default.
  • Provider URL: The URL or fully qualified domain name of the machine on which the OpenStack Networking instance is hosted. You must add the port number for the OpenStack Networking instance to the end of the URL or fully qualified domain name. By default, this port number is 9696.
  • Read Only: Allows you to specify whether the OpenStack Networking instance can be modified from the Administration Portal.
  • Requires Authentication: Allows you to specify whether authentication is required to access the OpenStack Networking service.
  • Username: A user name for connecting to the OpenStack Networking instance. This user name must be the user name for OpenStack Networking registered in the Keystone instance of which the OpenStack Networking instance is a member. By default, this user name is neutron.
  • Password: The password against which the above user name is to be authenticated. This password must be the password for OpenStack Networking registered in the Keystone instance of which the OpenStack Networking instance is a member.
  • Tenant Name: The name of the OpenStack tenant of which the OpenStack Networking instance is a member. By default, this is services.
  • Authentication URL: The URL and port of the Keystone server with which the OpenStack Networking instance authenticates.
OpenStack Volume
  • Data Center: The data center to which OpenStack Volume storage volumes will be attached.
  • Provider URL: The URL or fully qualified domain name of the machine on which the OpenStack Volume instance is hosted. You must add the port number for the OpenStack Volume instance to the end of the URL or fully qualified domain name. By default, this port number is 8776.
  • Requires Authentication: Allows you to specify whether authentication is required to access the OpenStack Volume service.
  • Username: A user name for connecting to the OpenStack Volume instance. This user name must be the user name for OpenStack Volume registered in the Keystone instance of which the OpenStack Volume instance is a member. By default, this user name is cinder.
  • Password: The password against which the above user name is to be authenticated. This password must be the password for OpenStack Volume registered in the Keystone instance of which the OpenStack Volume instance is a member.
  • Tenant Name: The name of the OpenStack tenant of which the OpenStack Volume instance is a member. By default, this is services.
  • Authentication URL: The URL and port of the Keystone server with which the OpenStack Volume instance authenticates.
VMware
  • Data Center: Specify the data center into which VMware virtual machines will be imported, or select Any Data Center to specify the destination data center during individual import operations (using the Import function in the Virtual Machines tab).
  • vCenter: The IP address or fully qualified domain name of the VMware vCenter instance.
  • ESXi: The IP address or fully qualified domain name of the host from which the virtual machines will be imported.
  • Data Center: The name of the data center in which the specified ESXi host resides.
  • Cluster: The name of the cluster in which the specified ESXi host resides.
  • Verify server's SSL certificate: Specify whether the ESXi host's certificate will be verified on connection.
  • Proxy Host: Select a host in the chosen data center with virt-v2v installed to serve as the 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, you cannot choose the host here, but can specify a host during individual import operations (using the Import function in the Virtual Machines tab).
  • Username: A user name for connecting to the VMware vCenter instance. The user must have access to the VMware data center and ESXi host on which the virtual machines reside.
  • Password: The password against which the above user name is to be authenticated.
Xen
  • Data Center: Specify the data center into which Xen 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).
  • URI: The URI of the Xen host.
  • Proxy Host: Select a host in the chosen data center with virt-v2v installed to serve as the host during virtual machine import operations. This host must also be able to connect to the network of the Xen external provider. If you selected Any Data Center, 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).
KVM
  • Data Center: Specify the data center into which KVM 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).
  • URI: The URI of the KVM host.
  • Proxy Host: Select a host in the chosen data center to serve as the 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, 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).
  • Requires Authentication: Allows you to specify whether authentication is required to access the KVM host.
  • Username: A user name for connecting to the KVM host.
  • Password: The password against which the above user name is to be authenticated.
External Network Provider
  • Provider URL: The URL or fully qualified domain name of the machine on which the external network provider is hosted. You must add the port number for the external network provider to the end of the URL or fully qualified domain name. By default, this port number is 9696.
  • Read Only: Allows you to specify whether the external network provider can be modified from the Administration Portal.
  • Requires Authentication: Allows you to specify whether authentication is required to access the external network provider.
  • Username: A user name for connecting to the external network provider.
  • Password: The password against which the above user name is to be authenticated.
  • Authentication URL: The URL and port of the authentication server with which the external network provider authenticates.
Test
Allows users to test the specified credentials. This button is available to all provider types.

12.2.11. Add Provider Agent Configuration Settings Explained

The Agent Configuration tab in the Add Provider window allows users to register details for networking plugins. This tab is only available for the OpenStack Networking provider type.

Table 12.2. Add Provider: General Settings

Setting
Explanation
Interface Mappings
A comma-separated list of mappings in the format of label:interface.
Broker Type
The message broker type that the OpenStack Networking instance uses. Select RabbitMQ or Qpid.
Host
The URL or fully qualified domain name of the machine on which the message broker is installed.
Port
The remote port by which a connection with the above host is to be made. By default, this port is 5762 if SSL is not enabled on the host, and 5761 if SSL is enabled.
Username
A user name for authenticating the OpenStack Networking instance with the above message broker. By default, this user name is neutron.
Password
The password against which the above user name is to be authenticated.