Configuring version 2.1 SP1

After installing or upgrading to BMC Cloud Lifecycle Management version 2.1 SP1, you must perform the following configuration steps before you use the product:

Enable compute placement customization

Enabling compute placement customization requires you perform these procedures:

• Making Platform Manager changes for compute placement customization
• Configuring BMC Atrium Orchestrator adapters and workflows for compute placement customization

Enable host name customization

Perform the following steps:

1. Stop the OSGI container by opening Services on the computer where Platform Manager is installed and stopping the BMC CSM service.
2. In the providers.json file, located in the Home\BMCCloudLifeCycleManagement\Platform_Manager\Configuration directory, change the following attribute default values to customize your organization's host names in BMC Cloud Lifecycle Management:

   Attribute	Default value
   MAX_HOST_NAME_LENGTH	14
   MAX_HOST_NAME_PREFIX_LENGTH	8
   HOST_NAME_PATTERN	{0}-{1,number,#} {0} is the host name prefix, - is the separator, and {1,number,#} is the counter; see the following table for examples Note Use only dashes "-", underscores "_", or periods "." as separators in HOST_NAME_PATTERN.

3. Save the modified providers.json file.
4. Restart the service BMC CSM to restart the OSGI container.
   

The following table shows several examples of host name patterns that you can customize:

Customizing host name prefix length 

Perform the following steps if you require the ability to use host name prefixes with lengths in excess of eight characters:

1. Log on to BMC Remedy Developer Studio using your administrator credentials.
2. Select Base Development mode.
3. Open the form CMU:CloudAdvancedInterface and click the Page 2 tab.
4. Double-click the field HostnamePrefix_SRT11 to edit its properties.
5. Change the value in the Input Length field from 8 to the number of characters you require for host name prefixes.
6. Save the form.
7. Open the form CMF:CloudServicesFulfillment.
8. Double-click the field Instance Name Prefix to edit its properties.
9. Change the value in the Input Length field from 8 to the number of characters you require for host name prefixes.
10. Save the form.
11. Log on to the BMC Remedy Mid Tier configuration server and flush the cache.
12. Verify your changes by logging on to My Cloud Services Console with end user credentials. 

Verify vCenter synchronization operation

Perform the following steps:

1. Make a required change in vCenter. For example, add a new VRP or data store or ESX to a cluster.
2. On the computer where the platform manager, OSGI, is installed, open the csm.log file.
3. In the csm.log file, search for the most recent occurrence of the string BBSA Cache Loading completed, which should appear in an API call.
4. Note the timestamp for the BBSA Cache Loading completed operation.
5. Add 30 minutes to this timestamp to get the next BMC BladeLogic Server Automation cache loading time.
6. Perform a vCenter synchronization after the next BMC BladeLogic Server Automation cache loading time.
   If you perform the synchronization before the next cache loading time, the changes made in vCenter are not reflected in BMC Cloud Lifecycle Management.
7. Check the vCenter changes that you made.
   For example, if you added a new VRP, ensure that the data store or ESX is onboarded into BMC Cloud Lifecycle Management.

If verification is unsuccessful, contact BMC Software Customer Support.