Red Hat Training

A Red Hat training course is available for Red Hat OpenStack Platform

Chapter 4. Adding an OpenStack Infrastructure Provider

After you have deployed your CloudForms Management Engine appliance, you can begin managing your OpenStack environment by adding it as an OpenStack Infrastructure provider. Supply the details of the admin account to get access to the resources in the admin tenant:

  1. Navigate to Infrastructure > Providers.
  2. Click Configuration (Configuration), then click Add a New Infrastructure Provider (Add a New Infrastructure Provider).
  3. Enter the Name of the provider to add. The Name is how the device is labeled in the console.
  4. Select OpenStack Platform Director from the Type list.

  5. Enter the Host Name or IP address(IPv4 or IPv6) of the provider.

    Important

    The Host Name must use a unique fully-qualified domain name (FQDN).

  6. Select the API Version of the keystone service from the list. The default is Keystone v2.

    Important

    If the keystone service is configured to use SSL, you must enter the keystone SSL port.

  7. Select the appropriate Zone for the provider. By default, the zone is set to default.

  8. In the Credentials area, under Default, provide the login credentials required for the OpenStack Infrastructure administrative user:

    • Enter the user name in the Username field.
    • Enter the password in the Password field.
    • Confirm the user password in the Confirm Password field.
    • Click Validate to confirm that the CloudForms Management Engine can connect to the OpenStack Infrastructure instance using the user name and password.

  9. Under AMQP, provide the login credentials required for the Advanced Message Queuing Protocol messaging service:

    • Enter the administrative user name in the Username field.
    • Enter the user password in the Password field.
    • Confirm the user password in the Confirm Password field.
    • Click Validate to confirm CFME can connect to the messaging service.

  10. Under RSA key pair, provide the user name and private key required to connect via SSH to all hosts in the provider:

    • Enter the administrative user name in the Username field.
    • Enter the private key from the machine on which OpenStack was deployed in the Private Key field.
  11. Click Add.
Note

CloudForms Management Engine requires that the adminURL endpoint for all OpenStack services be on a non-private network. As a result, you should assign the adminURL endpoint an IP address of something other than 192.168.x.x. The adminURL endpoint must be accessible to the CFME Appliance that is responsible for collecting inventory and gathering metrics from the OpenStack environment. In addition, make sure that all the keystone endpoints are accessible, otherwise the refresh process will fail.

4.1. Configuring Red Hat CloudForms to Receive Events

To allow Red Hat CloudForms to receive events from a Red Hat OpenStack Platform environment, you must configure the notification_driver option for the Compute service and Orchestration service in that environment.

  1. Edit /etc/heat/heat.conf, and specify the following options: 

    notification_driver=glance.openstack.common.notifier.rpc_notifier
notification_topics=notifications

  2. Edit /etc/nova/nova.conf, and specify the following options: 

    notification_driver=messaging
notification_topics=notifications

  3. Restart the Compute service and Orchestration services: 

    # systemctl restart openstack-heat-api.service \
  openstack-heat-api-cfn.service \
  openstack-heat-engine.service \
  openstack-heat-api-cloudwatch.service
# systemctl restart openstack-nova-compute.service

4.2. Configuring the Telemetry Service to Store Events

By default, the Telemetry service does not store events emitted by other services in a Red Hat OpenStack Platform environment. The following procedure outlines how to enable the Telemetry service to store such events so that they are exposed to Red Hat CloudForms when a Red Hat OpenStack Platform environment is added as an infrastructure provider.

  1. On the director node, edit undercloud.conf, and set store_events to true.

  2. Create an environment file called ceilometer.yaml, and add the following contents: 

    parameter_defaults:
  CeilometerStoreEvents: true

  3. Add the environment file to the overcloud deploy command: 

    # openstack overcloud deploy --templates -e ~/ceilometer.yaml