Unsupported content This version of the documentation is no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments.

Verify the configuration


Optionally, you can perform the following tasks to verify that the environment is properly configured: 

To verify the BMC Cloud Lifecycle Management configuration

After installing BMC Cloud Lifecycle Management, create cloud users (for example, the cloud administrator) and provider companies to verify the installation.

  1. Log in to the BMC Remedy Mid Tier as appadmin or as a user in the AR administrator group.
  2. Create a cloud administrator user in one of the following ways using the Application Administration Console:
  3. Log out and log back in using the new cloud administrator account you just created.
  4. Check the user form for the cloud administrator user that you created in Step 2. 
  5. Access the BMC Cloud Lifecycle Management Administration Console, as described in Accessing-the-console.
     The first time you access the BMC Cloud Lifecycle Management Administration Console, the Configuration workspace is displayed.
  6. Perform the steps listed in Setting-Configuration-workspace-options.
  7. From the BMC Cloud Lifecycle Management Administration Console, click the vertical Workspaces menu on the left side of the window and select Providers.
    The list of registered resource provider instances should be displayed.

    Note

    If you receive the error message, The specified plug-in does not exist. BMC.CLOUD.ARDBCPLUGIN, then the BMC Remedy Action Request Server/mid-tier is not connecting to the BMC Cloud Lifecycle Management plug-in. Review the enterprise server armonitor.cfg and ar.cfg files and the arjavaplugin.log file for a list of default providers. Also, check the API Server csm log to verify that the service has started.

  8. Verify that the default providers for Compute and Network are listed, as described in Listing-resource-providers-and-viewing-provider-details.
  9. Check to see if compute resources are available:
    1. From the BMC Cloud Lifecycle Management Administration console, click the vertical Workspaces menu on the left side of the window and select Resources
    2. Under Quick Links on the left, click Resources under the Compute section.
    3. Click the Onboard Resource icon plus_button.gif.
      The Onboard Resource dialog box is displayed.
      OnboardResource.gif
    4. Select the Pod, Provider Name, and Resource Type for the resource you want to onboard. By selecting a Resource Type, you can onboard resources from a virtual cluster or physical server. When you onboard a virtual cluster, you are also onboarding the virtual hosts, virtual resource pools, and virtual disk repositories (also called datastores) associated with the virtual cluster. An alphabetical list of resources is displayed in the Available Resources table.
    5. Find the resources that you want to add.
      • You can page through a long list by clicking the Page button pagebtn.gif.
      • You can search for resources by entering a search string in the Search box and clicking the search icon search_button.gif.

If resources are displayed in the Available Resources table, then installation and configuration was successful.

Unknown macro: confluence_scroll-html-ignore. Click on this message for details.

To verify TrueSight Server Automation (formerly known as BMC Server Automation) object

After creating the Virtual Guest packages and System Packages in TrueSight Server Automation, you can optionally validate them by creating and running a Virtual Guest Job or Provisioning Job.

Note that creating and running the jobs is for validation purposes only; BMC Cloud Lifecycle Management creates and runs these jobs automatically during the provisioning process.

For more information, see the following topics from the TrueSight Server Automation online technical documentation:

Unknown macro: confluence_scroll-html-ignore. Click on this message for details.

Where to go next

Perform-preliminary-tasks

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*