Preparing the provisioning service in BMC Cloud Lifecycle Management - a walkthrough
Overview
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 BladeLogic Server Automation, you launch the BMC Cloud Lifecycle Management portal. In the portal, you establish the foundation for the provisioning service by onboarding and creating the related BMC Cloud Lifecycle Management resources.
This section provides a walkthrough of the setup process. For more details of each procedure, refer to the topics under the Additional Information heading.
Before you begin
Ensure that the cache between BMC Cloud Lifecycle Management and BMC BladeLogic 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 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 bmccsmIf 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 BladeLogic Network Automation.
Onboard the pod containing the PXE datastore instance
You must onboard the pod containing the PXE datastore instance you created in BMC BladeLogic Server Automation. The format of the datastore instance name must be CSM Datastore - name of pod.
Additional information
For a more detailed procedure, see Onboarding-network-pods.
Import the container blueprint
Your next step is to import the container blueprint that the Publish Product Catalog job has made available.
Additional information
For a more detailed procedure, see Importing-network-container-blueprints.
Create the network container
Additional information
For a more detailed procedure, see Creating-network-containers.
Onboarding virtual clusters or physical servers
Before onboarding 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 BladeLogic Server Automation Console.
Add properties to the Device class in the Property Dictionary
- Open the Property Dictionary for the selected device in the BMC BladeLogic Server Automation Console.
- Expand the Built-in Property Classes folder, and select the Device class.
- 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. |
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: |
To onboard virtual clusters or physical servers
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.
Additional information
For a more detailed procedure, see Onboarding-compute-resources.
Create compute resource pools
Additional information
For a more detailed procedure, see Creating-compute-resource-pools.
Onboard tenants
Additional information
For a more detailed procedure, see Onboarding-tenants.
Create entitlement packages
Additional information
For a more detailed procedure, see Creating-entitlement-packages.
Map compute resource pools to network containers
Additional information
For a more detailed procedure, see Mapping-compute-pools-to-network-containers.
Map tenants to network containers
Additional information
For a more detailed procedure, see Mapping-tenants-to-network-containers.
Next steps
You are ready to initiate the server provisioning request by defining the service blueprint parameters and submitting the service offering.