Skip to Content
Information
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.

Preparing the provisioning service in BMC Cloud Lifecycle Management

After you have completed the configuration steps to prepare the physical server, bare-metal virtual machine, or virtual machine with template for provisioning in BMC Server Automation, you launch the BMC Cloud Lifecycle Management--Administration console. In the console, you establish the foundation for the provisioning service by onboarding and creating the related BMC Cloud Lifecycle Management resources.

This section provides an overview of the setup process. Each section provides a link to more details of each procedure.

Before you begin

  • Ensure that the cache between BMC Cloud Lifecycle Management and BMC Server Automation has been executed. It runs every 30 minutes by default. If necessary, you can force the caching by restarting the BMC_CSM service of the BMC Cloud Platform Manager (OSGi).

    To restart the BMC_CSM service under Microsoft Windows, use the stop\start commands of the Control Panel.
     To restart the BMC_CSM service under Linux, enter the following commands from the specified path on the command line:

    /etc/init.d/stop bmccsm
    /etc/init.d/start bmccsm

  • If you are not running OSGi as a service, then you can execute the following commands from the command line:

    To stop OSGi, enter Shutdown and then Exit.
     To run OSGi, use 

    -Xdebug -Xrunjdwp:transport=dt_socket,address=8654,suspend=n,server=y -jar org.eclipse.osgi_3.5.2.R35x_v20100126.jar -console -Xmx2048m -Xms512m -XX:MaxPermSize=256m
  • The pod to be onboarded must already be configured in BMC Network Automation.

To onboard the pod containing the PXE datastore instance

You must onboard the pod containing the PXE datastore instance you created in BMC Server Automation. The format of the datastore instance name must be CSM Datastore - name of pod.

Warning

The macro unmigrated-inline-wiki-markup from Confluence is no longer available.

For a more detailed procedure, see Onboarding-network-pods.

To import the container blueprint

Your next step is to import the container blueprint that the Publish Product Catalog Job has made available.

Warning

The macro unmigrated-inline-wiki-markup from Confluence is no longer available.

For a more detailed procedure, see Importing-network-container-blueprints.

To create the network container

Warning

The macro unmigrated-inline-wiki-markup from Confluence is no longer available.

For a more detailed procedure, see Creating-network-containers.

To onboard virtual clusters or physical servers

Before you onboard a physical server, ensure that the server is turned on. In addition, you will need to check whether values are assigned to properties in the Device class of the Property Dictionary in the BMC Server Automation Console.

To add properties to the Device class in the Property Dictionary

Warning

Note

If autodiscovery of unprovisioned devices is working correctly, you do not need to populate the CPU_COUNT (Integer), CPU_FAMILY (String), and RAM_MB (Integer) properties when you see devices in the user interface displaying the correct values for the corresponding properties.

  1. Open the Property Dictionary for the selected device in the BMC Server Automation Console.
  2. Expand the Built-in Property Classes folder, and select the Device class.
  3. Verify that values are assigned to the following properties.

Property

Value

CPU_COUNT (Integer)

number of CPUs for the device. If devices display in the interface showing the correct number of CPUs, you do not need to set a value for this property.

CPU_FAMILY (String)

the CPU family for the device. If devices display in the interface showing the correct CPU family, you do not need to set a value for this property.

Set the CPU family value to a valid BMC Atrium CMDB value. Choose among the following:

Alpha
AS400
ESA_390
IA_64
MIPS
MIPS_64
PA_RISC
PowerPC
PowerPC_64
SPARC
SPARC_64
StrongARM
Unknown
X86
X86_64
zArchitecture

(This listing will be updated with regular expression logic to cover likely discovered values.)

RAM_MB (Integer)

the correct amount of memory for the device. If devices display in the interface showing the correct CPU family, you do not need to set a value for this property.

NIC_DETAILS (List of Strings)

You must always enter this value. It is an entry for each network interface card (NIC) in the following format: mac-address, switch name, switch port. For example:

32:9C:53:50:AF:15,fooswitch,10
56:0C:FF:72:CC:46,fooswitch,11


To onboard virtual clusters or physical servers

Warning

Tip

For the Resource Type, select Virtual Cluster for bare-metal virtual machines and for virtual machines with templates. Select Physical Server for physical servers.

Warning

The macro unmigrated-inline-wiki-markup from Confluence is no longer available.

6. Select one or more resources and click the Add button to move them to the Selected Resources table. You can also drag and drop resources from the Available Resources table to the Selected Resources table.
 7. Click Onboard to onboard the selected resources and close the dialog box.

For a more detailed procedure, see Onboarding-compute-resources.

To create compute resource pools

Warning

Tip

For the Resource Type, select Virtual Cluster for bare-metal virtual machines and for virtual machines with templates. Select Physical Server for physical servers.

Warning

The macro unmigrated-inline-wiki-markup from Confluence is no longer available.

For a more detailed procedure, see Creating-compute-resource-pools.

To onboard tenants

Warning

The macro unmigrated-inline-wiki-markup from Confluence is no longer available.

For a more detailed procedure, see Onboarding-tenants.

To create entitlement packages

Entitlement packages are groups of requestable offerings that you want to make available to one or more tenant companies.

Warning

The macro unmigrated-inline-wiki-markup from Confluence is no longer available.

For a more detailed procedure, see Creating-entitlement-packages.

To map compute resource pools to network containers

Warning

The macro unmigrated-inline-wiki-markup from Confluence is no longer available.

For a more detailed procedure, see Mapping-compute-pools-to-network-containers.

To map tenants to network containers

Warning

The macro unmigrated-inline-wiki-markup from Confluence is no longer available.

For a more detailed procedure, see Mapping-tenants-to-network-containers.

Where to go from here

You are ready to initiate the server provisioning request by defining the service blueprint parameters and submitting the service offering.

 

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

BMC Cloud Lifecycle Management 3.0