1. Navigate to Compute → Infrastructure → Providers.
2. Click (Configuration), then click (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 Red Hat Enterprise Virtualization Manager 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. Enter the API Port if your provider uses a non-standard port for access.
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 Red Hat Enterprise Virtualization administrative user:

   • Enter the user name, 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 Red Hat CloudForms can connect to the Red Hat Enterprise Virtualization Manager.

9. Under C & U Database tab, provide the login credentials for the Red Hat CloudForms user of the Red Hat Enterprise Virtualization Data Warehouse database:

   Important

   To collect capacity and utilization data, you must enable the capacity and utilization server roles available from the settings menu, Configuration → Server → Server Control. For more information on capacity and utilization collection, see "Assigning the Capacity and Utilization Server Roles" in the Deployment Planning Guide.

   Important

   To collect capacity and utilization data for a Red Hat Enterprise Virtualization environment, the Data Warehouse and Reports components must be installed in that environment, and you must create a Red Hat CloudForms user in the Data Warehouse database.

   To install the Data Warehouse and Reports components in a Red Hat Enterprise Virtualization environment, see the Red Hat Virtualization Installation Guide.

   To create a Red Hat CloudForms user in the Data Warehouse database, see Data Collection for Red Hat Enterprise Virtualization 3.3 and 3.4 in the Deployment Planning Guide. `

   • 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 Red Hat CloudForms can connect to the database.
10. Click Save.

1. Navigate to Compute → Infrastructure → Providers.
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).
6. Click (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 Enterprise 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. Navigate to Compute → Infrastructure → Providers.
2. Click (Configuration), then click (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. 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)
   2. In API Port, set the public port used by the OpenStack Keystone service. By default, OpenStack uses port 5000 for this.
   3. Select the appropriate Security Protocol used for authenticating with your OpenStack provider.
   4. 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.
   5. 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.3.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.

1. Navigate to Compute → Infrastructure → Providers.
2. Click (Configuration), then click (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. Navigate to Compute → Infrastructure → Providers.
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)
6. Click (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. 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.

1. Navigate to Compute → Infrastructure → Providers.
2. Click (Configuration), then click (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. Add Red Hat Satellite 6 server details to Red Hat CloudForms.
2. Refresh the state of your Red Hat Satellite 6 provider in Red Hat CloudForms.
3. Select an existing bare metal host from Red Hat Satellite 6 for reprovisioning.
4. Apply policy tags to Red Hat Satellite 6 hosts.

1. Navigate to Configuration → Management.
2. Select Configuration → Add a new Provider.
3. Enter a Name for the provider.
4. Enter a URL for the provider. This is the root URL for the Satellite 6 server and can be either an IP address or a hostname. For example, http://satellite6.example.com.
5. Select Verify Peer Certificate to use encrypted communication with the provider. This requires the SSL certificates from your Red Hat Satellite 6 provider.
6. Enter a Username for a user on the provider. Ideally, this would be a user in Satellite 6 with administrative access.
7. Enter a Password, and then enter it again in Confirm Password.
8. Click Validate to test your connection with the Red Hat Satellite 6 server.
9. Click Add to confirm your settings and save the provider.

1. Navigate to Configuration → Management.
2. Select your Red Hat Satellite 6 provider using the checkbox, and click Configuration → Refresh Relationships and Power States. This triggers the refresh.
3. When the refresh is complete, select the Red Hat Satellite 6 provider to check the updated list of hosts groups in the provider.

1. Navigate to Configuration → Management.
2. Select Configured Systems from the accordion menu on the left. This displays the system list.
3. Select one or more hosts to reprovision.
4. Select Lifecycle → Provision Configured Systems.

5. Under the Request tab, enter the following details:

   1. E-Mail address
   2. First Name
   3. Last Name
   4. This form also contains optional fields for users to enter a plain text Note to inform Red Hat CloudForms administrators of any special details, and a field to provide a manager’s name in case administrators require approval from a user’s manager.
6. Select the Purpose tab and select any Red Hat CloudForms policy tags that apply to the system.
7. Select the Catalog tab. This screen displays the list of chosen machines to reprovision and their current details. Select a target host group from the Configuration Profile list. Red Hat CloudForms communicates with Red Hat Satellite to apply the configuration from this host group to the selected host and reprovision the system.

8. Select the Customize tab. This screen displays some customizable fields for the selected system. You can change the Root Password or change the Hostname and IP Address. Note that these fields are optional, because the host group in Red Hat Satellite 6 contains this information. The fields here will override the settings from the host group.

   Important

   Provisioning bare metal systems still requires access to the network that Red Hat Satellite 6 manages. This is because Red Hat Satellite controls PXE booting, kickstarts, and Puppet configuration for bare metal systems. Ensure the IP address you enter in Red Hat CloudForms can access a DHCP service that Red Hat Satellite 6 provides either through the main server or through a Red Hat Satellite 6 Capsule server.

9. Select the Customize tab. This screen allows you to either launch the provisioning process immediately on approval or using a schedule. Click Schedule to show the date and time fields used to schedule the provisioning.
10. Click Submit.

1. Navigate to Configuration → Management.
2. Select Configured Systems from the accordion menu on the left. This displays the system list.
3. Select one or more hosts to tag.
4. Select Policy → Edit Tags.
5. Under Tag Assignment, select a tag from Select a customer tag to assign and then choose a value from Select a value to assign. For example, you can tag this system as located in Chicago by selecting Location as the tag and Chicago as the value. Once selected, the user interface automatically adds this tag and value to the table below.
6. Click Save.

1. Navigate to Configuration → Management → Providers.
2. Under Configuration, click Add a new Provider.

3. In the Add a new Configuration Management Provider area:

   

   1. Enter a Name for the new provider.
   2. In the Type field, select Ansible Tower from the list.
   3. Enter the URL location or IP address to the Ansible Tower server.
4. Select the Verify Peer Certificate checkbox if desired.
5. In the Credentials area, provide the Username and Password, and Confirm Password.
6. Click Add.

1. Navigate to Configuration → Management → Providers.
2. Select the checkboxes for the Ansible Tower providers to refresh under All Ansible Tower Providers.
3. Click (Configuration), and then (Refresh Relationships and Power States).
4. Click OK.

1. Navigate to Configuration → Management → Providers.
2. Under All Configuration Manager Providers, select the Ansible Tower Providers accordion menu to display a list of providers.
3. Select your Ansible Tower provider to expand and list the inventory groups on that Ansible Tower system. The inventory groups can be expanded to view the systems contained within each group, as well as configuration details for these systems.

1. Navigate to Configuration → Management → Configured Systems.
2. Under All Configured Systems, select Ansible Tower Configured Systems to display a list.

1. Navigate to Services → Catalogs.
2. Click (Configuration), then (Add a New Catalog)
3. Enter a Name and Description for the catalog.
4. Click Add.

1. Navigate to Configuration → Management.
2. Click Ansible Tower Job Templates and select an Ansible Tower job template.
3. Click (Configuration), then (Create Service Dialog from this Job Template).
4. Enter a Service Dialog Name (for example, ansible_tower_job)and click Save.
5. Navigate to Services → Catalogs. Click Catalog Items.

6. Click (Configuration), then (Add a New Catalog Item) to create a new catalog item with the following details, at minimum:

   • For Catalog Item type, select Ansible Tower.
   • Enter a Name for the service catalog item.
   • Select Display in Catalog.
   • In Catalog, select the catalog you created previously.
   • In Dialog, select the service dialog you created previously (in this example, ansible_tower_job). No Dialog can be selected if the playbook does not require extra variables from the user. To ask the user to enter extra information when running the task, Service Dialog must be selected.
   • In Provider, select your Ansible Tower provider. This brings up the Ansible Tower Job Template option and configures the Provisioning Entry Point State Machine automatically.

   • Select your desired Ansible Tower Job Template from the list. Generally, this is the Ansible Tower job template previously used to create the service dialog.

     

7. Click Add. The catalog item you created will appear in the All Service Catalog Items list.

1. Navigate to Service Catalogs → Ansible Tower catalog.

   

2. Click Order for the catalog item.
3. Enter any variables requested and click Submit.

1. Navigate to Automate → Customization.
2. Click the Buttons accordion menu.
3. Click VM and Instance → Unassigned Buttons. This configures the button to run on virtual machines or instances.

4. Click (Configuration), then click (Add a new Button).

   • In the Adding a new Button screen, configure the Action parameters as desired. Dialog can be left blank if the playbook does not require extra variables. To ask the user to enter extra information when running the task, Service Dialog must be selected.

   • Configure Object Details fields with the following request details:

     • For System/Process, select Request.
     • For Message, enter create.
     • For Request, enter Ansible_Tower_Job.

   • Configure Attribute/Value Pairs with the following parameters:

     • job_template_name is the Ansible Tower job template name to associate with the button. The job_template_name field is mandatory; other parameters are provided by the Tower job dialog.

   • Configure Visibility to all users, or limit visibility by role as desired.

     

   • Click Add.

1. From Automate → Customization, navigate to Buttons → VM and Instance → Add a new Button Group, and configure the following:

   • Configure Basic Info as desired. For example, name the button group VM Actions.

   • In Assign Buttons, select the button you just created from the Unassigned list and click to assign it to Selected.

     

   • Click Add.

1. Navigate to Buttons → VM and Instance → VM Actions → Edit this Button Group.
2. In Assign Buttons, select the button you just created from the Unassigned list and click to assign it to Selected.
3. Click Add.

1. Navigate to Compute → Infrastructure → Virtual Machines.
2. Select the virtual machine to run the Ansible Tower job template on.

3. Click the VM Actions button to show the button you created, and click the button from the list to run the Ansible Tower job template.

   

4. Click Submit to execute the job.

1. Navigate to Compute → Clouds → Providers.
2. Click (Configuration), then click (Add a New Cloud Provider).
3. Enter a Name for the provider.
4. From the Type drop down menu select OpenStack.

5. Select the appropriate API Version from the list. The default is Keystone v2.

   If you select Keystone v3, enter the Keystone V3 Domain ID that Red Hat CloudForms should use. This is the domain of the user account you will be specifying later in the Default tab. If domains are not configured in the provider, enter default.

   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. By default, tenant mapping is disabled. To enable it, set Tenant Mapping Enabled to Yes.

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

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

   1. In Hostname (or IPv4 or IPv6 address), enter the public IP or fully qualified domain name of the OpenStack Keystone service.

      Note

      The hostname required here is also the OS_AUTH_URL value in the ~/overcloudrc file generated by the director (see Accessing the Overcloud in Red Hat OpenStack Platform Director Installation and Usage), or the ~/keystonerc_admin file generated by Packstack (see Evaluating OpenStack: Single-Node Deployment).

   2. In API Port, set the public port used by the OpenStack Keystone service. By default, OpenStack uses port 5000 for this.
   3. Select the appropriate Security Protocol used for authenticating with your OpenStack provider.

   4. In the Username field, enter the name of a user in the OpenStack environment.

      Important

      In environments that use Keystone v3 authentication, the user must have the admin role for the relevant domain.

   5. In the Password and Confirm Password fields, enter the password for the user.
   6. Click Validate to confirm Red Hat CloudForms can connect to the OpenStack provider.

9. 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 3.1.1.1, “Configuring the Overcloud 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.
10. Click Add after configuring the cloud provider.

1. Navigate to Compute → Clouds → Providers.
2. Click (Configuration), then click (Add a New Cloud Provider).
3. Enter a Name for the provider.
4. From the Type list, select Azure.
5. Select a region from the Region list. One provider will be created for the selected region.
6. Enter Tenant ID.
7. Enter Subscription ID.
8. Enter Zone.
9. In the Credentials section, enter the Client ID and Client Key; click Validate.
10. Click Add.

1. Navigate to Compute → Clouds → Providers.
2. Click (Configuration), then click (Discover Cloud Providers).
3. Select Azure from the Discover Type list.
4. In the Credentials section, enter your Azure Client ID, Client Key, Azure Tenant ID, and the Subscription ID for that tenant.
5. Click Start.

1. Navigate to Compute → Clouds → Providers.
2. Click (Configuration), then click (Add a New Cloud Provider).
3. Enter a Name for the provider.
4. From the Type list, select Amazon EC2.
5. Select an Amazon Region.
6. Select the appropriate Zone if you have more than one available.
7. Generate an Access Key in the Security Credentials of your Amazon AWS account. The Access Key ID acts as your User ID, and your Secret Access Key acts as your Password.
8. Click Validate to validate the credentials.
9. Click Add.

1. Navigate to Compute → Clouds → Providers.
2. Click (Configuration), then click (Discover Cloud Providers).
3. Select Amazon EC2 from the Discover Type list.
4. Enter your Amazon EC2 User ID and Password. Reenter your password in the Verify Password field.
5. Click Start.

1. Navigate to the settings menu, then Configuration → Zone → Advanced.
2. Select the configuration file to edit from the File list. If not already automatically selected, select EVM Server Main Configuration.

3. Set the get_public_images parameter:

   1. Set the parameter to get_public_images: true to make public images viewable.
   2. Set the parameter to get_public_images: false to make public images not viewable.

1. Enable the AWS Config service in the AWS Management Console. See the AWS Config Developer Guide for more information.
2. Create a new Amazon SNS topic named AWSConfig_topic. Red Hat CloudForms automatically connects to this topic.
3. (Optional) Configure the frequency of delta creation in the AWS Management Console.

To add a Google Compute Engine provider:

1. Navigate to Compute → Clouds → Providers.
2. Click (Configuration), then click (Add a New Cloud Provider).
3. Enter a Name for the provider.
4. From the Type list, select Google Compute Engine.
5. Select your Preferred Region from the list.
6. Enter your Google Compute Engine Project ID for Project.
7. Select the appropriate Zone if you have more than one available. Red Hat recommends creating a new zone for your Google Compute Engine provider.
8. Copy your project’s Service Account JSON key contents to the Service Account JSON field.
9. Click Validate to validate the credentials.
10. Click Add.

1. In Google Cloud Platform, select your project from the top menu bar.
2. Click to show the Products and Services menu. Click API Manager to go to https://console.cloud.google.com/apis/library/.
3. In the API Manager Overview tab, search for Pub/Sub in the Google APIs search bar and select Google Cloud Pub/Sub API from the results. Click the Enable button.
4. If Google Cloud Pub/Sub API is already enabled, the Enable button will not show, and instead Google Cloud Pub/Sub API will be listed under Enabled APIs.

1. In Google Cloud Platform, select your project and navigate to Products and Services → IAM & Admin → IAM to go to https://console.cloud.google.com/iam-admin/iam/.

2. Assign Logs Configuration Writer permissions to your project:

   1. If the cloud-logs@system.gserviceaccount.com account is already listed under Members, ensure Logs Configuration Writer is selected under Role(s).

   2. If the cloud-logs@system.gserviceaccount.com account is not listed under Members:

      1. Click Add to add the permissions.
      2. In the dialog box, enter cloud-logs@system.gserviceaccount.com in Members to add the Google APIs service account to the permissions list.
      3. In the Select a Role dropdown, select Logging → Logs Configuration Writer and click Add.

To add a middleware management provider:

1. Navigate to Middleware → Providers.
2. Click (Configuration), then click (Add a New Middleware Provider).

3. In the Add a New Middleware Provider screen, enter the following:

   • Name - Enter a name for the provider, for example, Middleware Manager.
   • Type - Select Hawkular.

   • Zone - Accept the default.

     Endpoints

   • Hostname (or IPv4 or IPv6 address) Host name of the machine where you installed the middleware manager.
   • API Port - Port of the middleware manager. The default is 8080.
   • User Name - The user name used to start the middleware manager. This should match the HAWKULAR_USERNAME.
   • Password - This should match the HAWKULAR_PASSWORD.
   • Confirm Password - Reenter the password.
4. Before you add the provider, click the Validate button to confirm that the user has the proper credentials.
5. Click Add.
6. Click (Configuration), then click (Refresh Items and Relationships).

1. To obtain the management service account token name, run the following command::

   # oc describe sa -n management-infra management-admin
   ...
   Tokens:  management-admin-token-0f3fh
            management-admin-token-q7a87

2. Select one of the tokens and run the following command to retrieve the full token output:

   # oc describe secret -n management-infra management-admin-token-0f3fh
   ...
   Data
   ====
   token:  eyJhbGciOiJSUzI1NiI...

   Replace management-admin-token-0f3fh with the name of your token.

Working with the Containers Overview Page

1. Navigate to Compute → Containers → Overview.
2. Click the desired containers entity, or provider, if applicable, for viewing the summary with further information.

Using the Topology Widget

1. Navigate to Compute → Containers → Providers.
2. Click the desired containers provider for viewing the provider summary.
3. On the provider summary page, click Topology in the Overview box on the right-hand side of the page.

Running a SmartState Analysis

1. Navigate to Compute → Containers → Container Images.
2. Check the container image to analyze. You can check multiple images.
3. Click (Configuration), and then (Perform SmartState Analysis).

1. Navigate to Storage → Volumes.
2. Click (Configuration), then click (Add a new Cloud Volume).
3. Enter a Volume Name.
4. Enter the volume size in gigabytes (GB).
5. Under Placement, select the cloud tenant to attach it to.
6. Click Add.

1. Navigate to Storage → Volumes.
2. Click the volume you want to back up to open the volume’s summary page.
3. Click (Configuration), then click (Create a Backup of this Cloud Volume).
4. Enter a name for the backup in Backup Name.

5. (Optional) Select Incremental? to take an incremental backup of the volume instead of a full backup.

   Note

   You can take an incremental backup of a volume if you have at least one existing full backup of the volume. An incremental volume saves resources by capturing only changes made to the volume since its last backup. See Create an Incremental Volume Backup in the Red Hat OpenStack Platform Storage Guide for more information.

6. Click Save.

1. Navigate to Storage → Volumes.
2. Click the volume whose backup you want to restore. This will open the volume’s summary page.
3. Click (Configuration), then click (Restore from a Backup of this Cloud Volume).
4. Select the volume to restore from in the Cloud Volume Backup list.
5. Click Save.

1. Navigate to Storage → Volumes.
2. Click the volume to snapshot to open the volume’s summary page.
3. Click (Configuration), then click (Create a Snapshot of this Cloud Volume).
4. Enter a name for the snapshot in Snapshot Name.
5. Click Save.

1. Navigate to Storage → Volumes.
2. Select the volume to attach.
3. Click (Configuration), then click (Attach selected Cloud Volume to an Instance) to open the Attach Cloud Volume screen.
4. Select an instance from the list.
5. (Optional) Enter the Device Mountpoint.
6. Click Attach.

1. Navigate to Storage → Volumes.
2. Select the volume to detach.
3. Click (Configuration), then click (Detach selected Cloud Volume from an Instance) to open the Detach Cloud Volume screen.
4. Select an instance from the list.
5. Click Detach.

1. Navigate to Storage → Volumes.
2. Select the volume to edit to open its summary page.
3. Click (Configuration), then click (Edit this Cloud Volume).
4. Enter the new Volume Name.
5. Click Save.

1. Navigate to Storage → Volumes.
2. Select the volume to delete.
3. Click (Configuration), then click (Delete selected Cloud Volumes).

1. Navigate to Storage → Object Stores to display a list of object store containers.
2. Click a container to open a summary page for that object store container.
3. Click Cloud Objects to view a list of object stores in the object store container.
4. Click an object store from the list to view the object store’s summary page.