Chapter 1. Infrastructure Providers

In Red Hat CloudForms, an infrastructure provider is a virtual infrastructure environment that you can add to a CloudForms appliance to manage and interact with the resources in that environment. This chapter describes the different types of infrastructure providers that you can add to CloudForms, and how to manage them. Infrastructure providers can be either discovered automatically by CloudForms, or added individually.

The web interface uses virtual thumbnails to represent infrastructure providers. Each thumbnail contains four quadrants by default, which display basic information about each provider:

2189

  1. Number of hosts
  2. Management system software
  3. Currently unused
  4. Authentication status

Table 1.1. Provider authentication status

IconDescription

2190

Validated: Valid authentication credentials have been added.

2191

Invalid: Authentication credentials are invalid.

2192

Unknown: Authentication status is unknown or no credentials have been entered.

1.1. Discovering Infrastructure Providers

In addition to individually adding providers, you can also discover all infrastructure providers in a given subnet range.

  1. Navigate to ComputeInfrastructureProviders.
  2. Click Configuration (Configuration), then click Discover Infrastructure Providers (Discover Infrastructure Providers).
  3. Select the types of provider to discover.
  4. Enter a Subnet Range of IP addresses starting with a From Address and ending with a To Address. The cursor automatically advances as you complete each octet.
  5. Click Start.

The appliance searches for all infrastructure providers in the specified subnet range, and adds them to the user interface. However, before you can manage the providers added via discovery, you must edit each provider and specify authentication details.

1.2. Discovering Physical Infrastucture Providers

In addition to discovering virtual infrastructure providers, CloudForms now has the ability to discover physical infrastructure providers in a given subnet range.

  1. Navigate to ComputePhysical InfrastructureProviders.
  2. Click Configuration (Configuration), then click Discover Physical Infrastructure Providers (Discover Physical Infrastructure Providers).
  3. Select the provider in Discovery Type.
  4. Enter a Subnet Range of IP addresses starting with a From Address and ending with a To Address.
  5. Enter a Port.
  6. Click Start.

The appliance searches for all physical infrastructure providers in the specified subnet range, and adds them to the user interface. However, before you can manage providers added via discovery feature, you must edit each provider to enter authentication details.

1.3. Red Hat Virtualization Providers

To use a Red Hat Virtualization provider, add it to the appliance and authenticate its hosts. You can also configure capacity and utilization data collection to help track usage and find common issues.

1.3.1. Enabling Red Hat Virtualization Capacity and Utilization Data Collection

Configure the following to collect capacity and utilization data from a Red Hat Virtualization provider:

  • In CloudForms, enable the capacity and utilization server roles from the settings menu, in ConfigurationServerServer Control. For more information on capacity and utilization collection, see Assigning the Capacity and Utilization Server Roles in the Deployment Planning Guide.
  • For information on selecting clusters and datastores used to collect data, see Capacity and Utilization Collections in the General Configuration Guide.
  • In your Red Hat Virtualization environment, install the Data Warehouse and Reports components, and create a Red Hat CloudForms user in the Data Warehouse database:

1.3.2. Adding a Red Hat Virtualization Provider

After initial installation and creation of a Red Hat CloudForms environment, add a Red Hat Virtualization provider to the appliance.

  1. Navigate to ComputeInfrastructureProviders.
  2. Click Configuration (Configuration), then click Add a New Infrastructure Provider (Add a New Infrastructure Provider).
  3. Enter a Name for the provider.
  4. Select Red Hat Virtualization from the Type list.
  5. Select the appropriate Zone for the provider. If you do not specify a zone, it is set to default.
  6. Under Endpoints in the Default tab, configure the following:

    • Enter the Hostname or IPv4 or IPv6 address of the Red Hat Virtualization Manager.

      Important

      The Hostname must be a unique fully qualified domain name.

    • Enter the API Port if your provider uses a non-standard port for access.
    • Select Yes or No to Verify TLS Certificates to specify whether to authenticate securely to the provider using TLS.

      • If you select Yes for Verify TLS Certificates, you can either paste a custom certificate in the Trusted CA Certificates field in PEM format, or leave the Trusted CA Certificates field empty if your Red Hat Virtualization provider has a trusted Certificate Authority.
    • Provide the login credentials for the Red Hat Virtualization administrative user:

      • Enter the user name (formatted as admin@internal) in the Username field.
      • Enter the password in the Password field.
      • Confirm the password in the Confirm Password field.
      • Click Validate to confirm CloudForms can connect to the Red Hat Virtualization Manager.
  7. Under Endpoints in the C & U Database tab, you can configure capacity and utilization metrics collection by providing login credentials for the CloudForms user of the Red Hat Virtualization Data Warehouse database. You can also configure this later by editing the provider. Configure the following in the C & U Database tab:

    Important

    To collect capacity and utilization data from a Red Hat Virtualization provider, the capacity and utilization server roles must be enabled in CloudForms. The Red Hat Virtualization environment must also contain the Data Warehouse and Reports components and a CloudForms user. Specific clusters, hosts, and datastores can also be configured for collection. See Section 1.3.1, “Enabling Red Hat Virtualization Capacity and Utilization Data Collection” for configuration details.

    • Enter the database hostname or IPv4 or IPv6 address in Hostname.
    • Enter the API Port if your provider uses a non-standard port for access.
    • Enter the Database Name.
    • Enter the database 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 CloudForms can connect to the database.
  8. Click Add to finish adding the Red Hat Virtualization provider.

1.3.3. Authenticating Red Hat Virtualization Hosts

After adding a Red Hat Virtualization infrastructure provider, you must authenticate its hosts to enable full functionality.

  1. Navigate to ComputeInfrastructureProviders.
  2. Click on a provider to display its summary screen.
  3. On the summary screen, click Hosts in the Relationships information box to display the hosts on that provider.
  4. Select the hosts to authenticate. You can select all hosts using the Check All option.
  5. Click Configuration (Configuration).
  6. Click Edit this item (Edit this item).
  7. In the Credentials area, enter credentials for the following, as required:

    1. Default: This field is mandatory. Users should have privileged access such as, root or administrator.
    2. Remote Login: Credentials for this field are required if SSH login is disabled for the Default account.
    3. Web Services: This tab is used for access to Web Services in Red Hat Virtualization.
    4. IPMI: This tab is used for access to IPMI.
  8. Click Validate.
  9. If editing multiple hosts:

    1. Select a host from the Select Host to validate against list.
    2. If required, enter credentials for Remote Login, Web Services, and IPMI in their respective tabs; click Validate.
    3. Select another host to validate each of these credentials against.
  10. Click Add.

1.4. OpenStack Infrastructure Providers

Enable an OpenStack Infrastructure provider by adding it to the appliance.

1.4.1. Adding an OpenStack Infrastructure Provider

After initial installation and creation of a Red Hat CloudForms environment, add an OpenStack infrastructure provider to the appliance. Red Hat CloudForms supports operating with the OpenStack admin tenant. When creating an OpenStack infrastructure provider in Red Hat CloudForms, select the OpenStack infrastructure provider’s admin user because it is the default administrator of the OpenStack admin tenant. When using the admin credentials, a user in Red Hat CloudForms provisions into the admin tenant, and sees images, networks, and instances that are associated with the admin tenant.

Note
  1. Navigate to ComputeInfrastructureProviders.
  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. Select the API Version of your OpenStack provider’s Keystone service from the list. The default is Keystone v2.

    Note
    • With Keystone API v3, domains are used to determine administrative boundaries of service entities in OpenStack. Domains allow you to group users together for various purposes, such as setting domain-specific configuration or security options. For more information, see OpenStack Identity (keystone) in the Red Hat OpenStack Platform Architecture Guide.
    • The provider you are creating will be able to see projects for the given domain only. To see projects for other domains, add it as another cloud provider. For more information on domain management in OpenStack, see Domain Management in the Red Hat OpenStack Platform Users and Identity Management Guide.
  6. Select the appropriate Zone for the provider. By default, the zone is set to default.

    Note

    For more information, see the definition of host aggregates and availability zones in OpenStack Compute (nova) in the Red Hat OpenStack Platform Architecture Guide.

  7. In the Default tab, under Endpoints, configure the host and authentication details of your OpenStack provider:

    1. Select a Security Protocol method to specify how to authenticate the provider:

      • SSL without validation: Authenticate the provider insecurely using SSL.
      • SSL: Authenticate the provider securely using a trusted Certificate Authority. Select this option if the provider has a valid SSL certificate and it is signed by a trusted Certificate Authority. No further configuration is required for this option. This is the recommended authentication method.
      • Non-SSL: Connect to the provider insecurely using only HTTP protocol, without SSL.
    2. Enter the Host Name or IP address(IPv4 or IPv6) of the provider. If your provider is an undercloud, use its hostname (see Setting the Hostname for the System in Red Hat OpenStack Platform Director Installation and Usage for more details)
    3. In API Port, set the public port used by the OpenStack Keystone service. By default, OpenStack uses port 5000 for non-SSL security protocol. For SSL, API port is 13000 by default.
    4. Select the appropriate Security Protocol used for authenticating with your OpenStack provider.
    5. In the Username field, enter the name of an OpenStack user with privileged access (for example, admin). Then, provide its corresponding password in the Password and Confirm Password fields.
    6. Click Validate to confirm Red Hat CloudForms can connect to the OpenStack provider.
  8. Next, configure how Red Hat CloudForms should receive events from the OpenStack provider. Click the Events tab in the Endpoints section to start.

    • To use the Telemetry service of the OpenStack provider, select Ceilometer. Before you do so, the provider must first be configured accordingly. See Section 1.4.1.1, “Configuring the Undercloud to Store Events” for details.
    • If you prefer to use the AMQP Messaging bus instead, select AMQP. When you do: In Hostname (or IPv4 or IPv6 address) (of the Events tab, under Endpoints), enter the public IP or fully qualified domain name of the AMQP host.

      • In the API Port, set the public port used by AMQP. By default, OpenStack uses port 5672 for this.
      • In the Username field, enter the name of an OpenStack user with privileged access (for example, admin). Then, provide its corresponding password in the Password and Confirm Password fields.
      • Click Validate to confirm the credentials.
  9. You can also configure SSH access to all hosts managed by the OpenStack infrastructure provider. To do so, click on the RSA key pair tab in the Endpoints section.

    1. From there, enter the Username of an account with privileged access.
    2. If you selected SSL in Endpoints > Default > Security Protocol earlier, use the Browse button to find and set a private key.
  10. Click Add after configuring the infrastructure provider.
Note

Red Hat CloudForms requires that the adminURL endpoint for all OpenStack services be on a non-private network. Accordingly, assign the adminURL endpoint an IP address of something other than 192.168.x.x. The adminURL endpoint must be accessible to the Red Hat CloudForms appliance that is responsible for collecting inventory and gathering metrics from the OpenStack environment. Additionally, all the Keystone endpoints must be accessible, otherwise refresh will fail.

1.4.1.1. Configuring the Undercloud to Store 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. See Installing the Undercloud and Configuring the Director in Red Hat OpenStack Platform Director Installation and Usage for related details.

1.5. VMware vCenter Providers

To use a VMware vCenter provider, add it to the appliance and authenticate its hosts.

1.5.1. Adding a VMware vCenter Provider

After initial installation and creation of a Red Hat CloudForms environment, add a VMware vCenter provider to the appliance.

  1. Navigate to ComputeInfrastructureProviders.
  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 VMware vCenter 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.

  6. Select the appropriate Zone for the provider. By default, the zone is set to default.
  7. In the Credentials area, under Default, provide the login credentials required for the VMware vCenter administrative user:

    • Enter the user name in the Username field.
    • Enter the password in the Password field.
    • Confirm the password in the Confirm Password field.
    • Click Validate to confirm Red Hat CloudForms can connect to the VMware vCenter.
  8. Click Add.

1.5.1.1. Using a Non-Administrator Account for vCenter Hosts

After adding a VMware vCenter infrastructure provider, you must authenticate its hosts to enable full functionality. You can use administrator credentials, or create another user assigned to a role created for Red Hat CloudForms. See the VMware documentation for instructions on how to create a role.

The following privileges should be enabled for the non-administrator user:

From the Global group, check:

  • Cancel task
  • Diagnostics
  • Log Event
  • Set custom attribute
  • Settings

Check the entire set of privileges for the following groups:

  • Alarms
  • Datastores
  • dvPort Group
  • Host
  • Network
  • Resource
  • Scheduled Task
  • Tasks
  • Virtual Machine
  • vSphere Distributed Switch

Additionally, you must assign the new role to the following objects:

  • Datacenter: At the Datacenter the Red Hat CloudForms user/group must have at least the read-only role at the Datacenter level (Not Propagated) to be able to see the datacenter. Without this access, relationships cannot be made. Specifically, the datastores will not show up.
  • Cluster: Each Cluster that the Red Hat CloudForms needs access to must have the new role assigned and propagated.
  • Folders: Each Folder that Red Hat CloudForms needs access to must have the new role assigned and propagated.
  • Datastores: Each Datastore that Red Hat CloudForms needs access to must have the new role assigned and propagated.
  • Networking: Each vLAN or Port Group that Red Hat CloudForms needs access to must have the new role assigned and propagated.

1.5.2. Authenticating VMware vCenter Hosts

The procedure below describes how to authenticate the VMware vCenter hosts.

  1. Navigate to ComputeInfrastructureProviders.
  2. Click on a provider to display its summary screen.
  3. On the summary screen, click Hosts in the Relationships information box to display the hosts on that provider.
  4. Select the hosts to authenticate. You can select all hosts using the Check All option.
  5. Click Configuration (Configuration)
  6. Click Edit Selected items (Edit Selected items).
  7. In the Credentials area, under Default, provide the VMware ESXi login credentials:

    • Enter the user name in the Username field.
    • Enter the password in the Password field.
    • Confirm the password in the Confirm Password field.
    • Click Validate to confirm Red Hat CloudForms can connect to the VMware vCenter host.
  8. If editing multiple hosts, select a host from the Select Host to validate against list; provide the VMware ESXi login credentials and click Validate.
  9. Click Save.

1.6. Microsoft SCVMM Providers

To use a Microsoft System Center Virtual Machine Manager (SCVMM) provider, add it to the appliance and set up the SCVMM server for authentication.

Note

To use a SCVMM provider, you must have at least one network adapter available for communication between the host and the SCVMM management server. Make sure that Used by Management is checked for this network adapter in the SCVMM host properties.

1.6.1. Authenticating to Microsoft SCVMM

Before you can add a Microsoft SCVMM provider to your Red Hat CloudForms environment, you must enable WinRM to listen for HTTP traffic on Microsoft SCVMM servers. You must also set the appropriate execution policy on the Microsoft SCVMM server to allow PowerShell scripts from the appliance to run remotely.

  1. Log in to the Microsoft SCVMM server.
  2. Enable WinRM for configuration.

    winrm quickconfig
  3. Set the following options:

    winrm set winrm/config/client/auth @{Basic="true"}
    winrm set winrm/config/service/auth @{Basic="true"}
    winrm set winrm/config/service @{AllowUnencrypted="true"}
  4. For Windows 2012 R2 with PowerShell 4.0, use the following syntax to set these options:

    winrm set winrm/config/client/auth '@{Basic="true"}'
    winrm set winrm/config/service/auth '@{Basic="true"}'
    winrm set winrm/config/service '@{AllowUnencrypted="true"}'
  5. Enable remote script execution on the SCVMM server using the Set-ExecutionPolicy cmdlet.

    Set-ExecutionPolicy RemoteSigned

    For more information on SCVMM remote script execution policies, see Using the Set-ExecutionPolicy Cmdlet.

If PowerShell returns an error, search for log_dos_error_results in the evm.log and scvmm.log files for information.

1.6.2. Adding a Microsoft SCVMM Provider

After initial installation and creation of a Red Hat CloudForms environment, add a Microsoft System Center Virtual Machine Manager (SCVMM) provider to the appliance.

Note

To authenticate the provider using a self-signed Certificate Authority (CA), configure the CloudForms appliance to trust the certificate using the steps in Section A.1, “Using a Self-Signed CA Certificate” before adding the provider.

  1. Navigate to ComputeInfrastructureProviders.
  2. Click 1847 (Configuration), then click 1862 (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 Microsoft System Center VMM 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.

  6. Select Kerberos or Basic (SSL) from the Security Protocol list.

    1. For Kerberos:

      1. Enter the user name and realm in the Username field.
      2. Enter the password in the Password field.
      3. Enter the password again in the Confirm Password field.
    2. For Basic (SSL):

      1. Enter the user name in the Username field.
      2. Enter the password in the Password field.
      3. Enter the password again in the Confirm Password field.
  7. Click Validate to confirm that Red Hat CloudForms can connect to the Microsoft System Center Virtual Machine Manager.
  8. Click Add.

1.7. Refreshing Providers

Refresh a provider to find other resources related to it. Use Refresh after initial discovery to get the latest data about the provider and the virtual machines it can access. Ensure the provider has credentials to do this. If the providers were added using Discovery, add credentials using Edit Selected Infrastructure Provider (Edit Selected Infrastructure Provider).

  1. Navigate to ComputeInfrastructureProviders.
  2. Select the providers to refresh.
  3. Click Configuration (Configuration), and then Refresh Relationships and Power States (Refresh Relationships and Power States).
  4. Click OK.

1.8. Tagging Multiple Providers

Apply tags to all providers to categorize them together at the same time.

  1. Navigate to InfrastructureProviders.
  2. Check the providers to tag.
  3. Click Policy (Policy), and then Edit Tags (Edit Tags).
  4. In the Tag Assignment area, select a customer tag to assign from the first list, then select a value to assign from the second list.

    2194

  5. Select more tags as required; click (Save).

1.9. Viewing a Provider

From a list of providers, you can review a specific provider by clicking on it. This displays various options to access provider information.

There are two methods of viewing an infrastructure provider’s details: the summary screen (default) and the dashboard screen. Use the summary Summary and dashboard Dashboard buttons to toggle between views.

Both the summary and dashboard screens contain a taskbar with Reload, Configuration, Policy, Monitoring, and Authentication buttons to manage the selected provider.

Provider Summary Screen

providers summary screen

The provider summary screen displays information about the provider in table format.

  • Provider accordion: Displays details about the provider’s Properties and Relationships on the sidebar. Click to expand these lists.
  • Provider summary: Displays a provider’s Properties, Status, Relationships, and Smart Management. Click on an item in the Relationships table to see more information about that entity.

Provider Dashboard Screen

providers summary dashboard

From the dashboard, you can view:

  • Number of clusters, hosts, virtual machines, templates, datastores, resource pools, and other entities on the provider. Click on an entity to see more information about that item.
  • Aggregate utilization for CPU, memory, and storage
  • Network I/O statistics
  • Trends for hosts and virtual machines discovered

To view the dashboard:

  1. Navigate to ComputeInfrastructureProviders.
  2. Click the infrastructure provider to view.
  3. To access the dashboard view, click Dashboard (Dashboard view).

To return to the summary view, click Summary (Summary view).

1.10. Removing a Provider

If a provider has been decommissioned or requires some troubleshooting, it might require deletion from the VMDB.

Deleting a provider removes the account information from Red Hat CloudForms console. You will no longer be able to view any associated history including chargeback reports generated for the deleted provider. Additionally, if Red Hat CloudForms is the database of record, deleting providers would become a major problem for the other systems relying on it for accurate and consistent billing information. Review all the dependencies carefully before deleting a provider.

  1. Navigate to ComputeInfrastructureProviders.
  2. Select the check box for the provider to delete.
  3. Click Configuration (Configuration), then Remove Infrastructure Providers from the VMDB (Remove Infrastructure Providers from the VMDB).
  4. Click (OK).

1.11. Viewing the Provider Timeline

View the timeline of events for the virtual machines registered to a provider.

  1. Navigate to ComputeInfrastructureProviders.
  2. Click a provider.
  3. Click Monitoring (Monitoring), and then Timelines (Timelines)from the taskbar, or from the provider accordion, click PropertiesTimeline.
  4. From Options, customize the period of time to display and the types of events to see.

    provider timeline

    • Use Show to select regular Management Events or Policy Events.
    • Use the Interval dropdown to select hourly or daily data points.
    • Use Date to type the date for the timeline to display.
    • If you select to view a daily timeline, use Show to set how many days back to go. The maximum history is 31 days.
    • The three Event Groups lists allow you to select different groups of events to display. Each has its own color.
    • From the Level list, select a Summary event, or a Detail list of events. For example, the detail level of a Power On event might include the power on request, the starting event, and the actual Power On event. If you select Summary, only the Power On event displays in the timeline.

1.12. Viewing Hosts and Clusters

Access a tree view of the hosts and clusters for a provider from the Provider Summary.

  1. Navigate to ComputeInfrastructureProviders.
  2. Click the provider to view the hosts and clusters.
  3. Click on the Relationships accordion, then click Hosts & Clusters.

hostsandclusters

1.13. Viewing Virtual Machines and Templates

Access a tree view of the virtual machines and templates for a provider from the Provider Summary.

  1. Navigate to ComputeInfrastructureProviders.
  2. Click the provider to view the virtual machines and templates.
  3. From accordion menu, click Relationships, then click VMs & Templates.