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.

Configuring after installation

There are two methods for configuring BMC Cloud Lifecycle Management, depending on the infrastructure platform you require and the complexity of your cloud: 

  • If your cloud environment is a simple one, and you will use only VMware vSphere or Amazon Web Services as your infrastructure platform, then you can configure BMC Cloud Lifecycle Management using the Quick Start wizard.
  • If your cloud environment is more complex, or it requires an infrastructure platform other than VMware vSphere or Amazon Web Services, then you must configure BMC Cloud Lifecycle Management manually by performing tasks in the participating BMC products, as well as in the BMC Cloud Lifecycle Management console.

This topic contains the following sections:

Using the Quick Start wizard

Quick Start is a wizard-based UI that simplifies configuration requirements for BMC Cloud Lifecycle Management. Using Quick Start, you provide a limited number of configuration settings. All other configuration is automated, including configuration of underlying BMC products such as BMC Server Automation and BMC Network Automation.

For detailed information, see Using Quick Start.

Manually configuring BMC Cloud Lifecycle Management

The following table lists all of the tasks required to configure a fully functional BMC Cloud Lifecycle Management environment. The Configuration tasks column contains links to the sub-topics that provide a consolidated list of the procedures required to complete the task. The links in the Details column bring you to the full procedures in the Administering section of this wiki.

Configuration tasks

Details

Post-install configuration for Cloud Platform Manager

Perform these steps to run Sync Index after installing the Cloud Platform Manager:

  1. Log on to the BMC Remedy Mid Tier as an administrator:
    Example URL: http://midTierHost:midTierPort/arsys
  2. Go to Administrator Console > Cloud LifeCycle Management > Configuration workspace and click General.
  3. In the General tab, go to Maintenance Mode On, and add a message and click Save.    
  4. Click Sync Index.
    The status changes to Completed.
  5. Change the Maintenance Mode to Off and save changes.

Perform preliminary tasks

  1. Add the AR User Fixed licenses to the BMC AR System Server – Cloud Portal and Database – Primary host server, as described in Perform preliminary tasks.
  2. On the BMC AR System Server – Cloud Portal and Database – Primary enterprise server, create the following items, as described in To create a new provider company and a new cloud administrator user account:

Set up the initial configuration

(This task is called creating a connector in Quick Start.)

  1. Configure the BMC Cloud Lifecycle Management – Administration Console, as described in Setting Configuration workspace options.
  2. Create a site in the Physical Location form on the BMC AR System Server – Cloud Portal and Database server, as described in Creating a physical location for a pod.
  3. Set up the virtualization connections in BMC Server Automation for VMware, as described in Setting up a VMware vSphere environment.
  4. To set up connections for additional virtual environments, see Adding virtual environments for compute resources.
  5. Create a network pod using a pod blueprint, as described in Creating network pod blueprints and Creating network pods in BMC Network Automation.
  6. Onboard your network pod into BMC Cloud Lifecycle Management, as described in Onboarding and offboarding network pods.
  7. Create network container blueprints, as described in Creating network container blueprints.
  8. Configure email notifications and enable retry provisioning to perform better troubleshooting and maintenance of service offering instances in case of failures.

Configure environments

  1. Create network containers using container blueprints, as described in Creating network containers.
  2. Create resource pools, as described in Creating compute resource pools.
  3. Onboard resources, as described in Onboarding resources.
  4. Map compute pools to network containers, as described in Mapping resource pools to network containers.

Create services

  1. Create the following in BMC Server Automation, as described in Creating objects in BMC Server Automation:
    • Virtual Guest Packages
    • Product Catalog jobs
    • System Packages
    • Virtual machine templates
  2. Create service blueprints, as described in Building service blueprints.
  3. Create service offerings, as described in Creating cloud services.
  4. (Optional) Create and assign entitlement packages, as described in Creating entitlement packages and Managing entitlement packages.

(Optional) Configure optional products

You can integrate other products with BMC Cloud Lifecycle Management in the following ways:

Configure tenants and tenant users

  1. Create and configure tenant companies and users, as described in Tenants.
  2. Map tenants to network containers, as described in Mapping tenants to network containers.

Verify the configuration

Perform specific tasks to verify that the environment is properly configured.

(Optional) Third-party provider typesOptionally, you can configuring BMC Cloud Lifecycle Management with out-of-the-box third party platforms.

(Optional) Enable SSL

Optionally, you can enable SSL for all the BMC Cloud Lifecycle Management components:

(Optional) Configuring products for HA

Optionally, you can perform steps to configure products in BMC Cloud Lifecycle Management for high availability (HA).

Where to go next

Perform preliminary tasks

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.

Comments

  1. Ganapathy Hariharan
    Team, BMC CLM AR comes with SSI Stack Installer where the installer does not allow to change the port #/password during installation. This is only for AR Component where the port # cannot be changed. it will be good if you can provide a link or documentation on where and all you will have change the port # in CLM Components after the installation.
    May 26, 2017 07:18
  2. Moiz Nalwalla

    Thanks for commenting. I'll work on this.

    May 29, 2017 03:01
    1. Ganapathy Hariharan
      Thanks Moiz. let me know once you incorporate the changes..
      May 29, 2017 08:16
    1. Ganapathy Hariharan

      any updates on this?

      Jun 14, 2017 08:11