Before resources can be used in the cloud, you must first make BMC Cloud Lifecycle Management aware of those resources. This procedure describes how to set up resource providers and resources within BMC Cloud Lifecycle Management so that they can be used when provisioning services in the cloud. For more overview information about resources, see Resource provider overview and Resource types.
BMC Cloud Lifecycle Management does not limit the number of network resources you can use (for example, how many VLAN IDs in a POD or network container, how many subnets in a network container, or how many IP ranges can you have for a subnet). Restrictions depend on the resources themselves. Limits for each third-party product might be different.
Before you begin
- Ensure that one or more network pods and network container blueprints exist in the registered BMC Network Automation provider instance.
- If you are provisioning VMs, ensure that one or more virtual clusters have been configured through BMC Server Automation and exist in the network.
Setting up providers and resources
The following list outlines the high-level steps to onboard and use resources within the cloud:
- Register a resource provider.
- Onboard a pod into BMC Cloud Lifecycle Management.
- Import network container blueprints.
- Create a network container.
- Onboard compute or platform-as-a-service (Paas) resources.
- Create a compute or PaaS resource pool.
- Map resource pools to network containers.
- Configure storage resources. You do not have to configure storage resources when setting up PaaS resources, such as databases.
For information about modifying resources that have already been added to the cloud, see Editing and removing resources.
See the following BMC Communities video (8:31) to learn how you can use BMC Cloud Lifecycle Management to manage infrastructure changes during the software development cycle.
Log in or register to comment.