Creating and onboarding resources and tenants

After you have created your DML entries in the Product Catalog, you are ready to create and onboard the resources and tenants for your Amazon Elastic Compute Cloud (Amazon EC2) provider instance. These procedures follow the typical BMC Cloud Lifecycle Management workflows for creating and onboarding objects. Be aware of the following guidelines that are unique to Amazon EC2 provider instances:

• Amazon EC2 Availability Zones are onboarded as pods.
• The network container blueprints that you import are based on the Amazon Web Services (AWS) constructs Availability Zone and Virtual Private Cloud (VPC).
• You add a virtual disk repository resource type for the Amazon EC2 provider type.

This topic provides the following instructions:

• • Before you begin
  • To onboard a pod for the Amazon EC2 provider type
  • To onboard a virtual cluster
  • To create a compute pool
  • To create a Virtual Disk Repository pool for the onboarded pod
  • To import a network container blueprint to an onboarded pod
  • To create a network container for the onboarded pod and blueprint
  • To map compute pools to the network container
  • To map tenants to the network container
  • Where to go from here

Before you begin

You must first create and onboard the requisite resources and tenants to enable the provisioning of the Amazon EC2 instance.

To onboard a pod for the Amazon EC2 provider type

Amazon Availability Zones are onboarded as pods. These Amazon EC2 pods function independent of any Amazon account.

1. From the BMC Cloud Lifecycle Management Administration Console, choose the Resources workspace.
2. Select Pods under the General section.
3. Click the Onboard Pods icon to display the Onboard Pod dialog box.
4. Select the registered Amazon EC2 provider type from the Provider Name drop-down menu.
   
   
   
5. Select one or more entries from the list of Amazon EC2 Availability Zones. (Availability Zones are designated as geographic areas and onboarded as pods.)
6. Click Onboard.

Refer to Onboarding-and-offboarding-network-pods for detailed procedures.

To onboard a virtual cluster

You onboard one virtual cluster per pod.

1. On the Resource Management > Compute > Resources window, check that the Resource Type Virtual Cluster is specified.
   
   
   
2. Click the Onboard Resource icon to display the Onboard Resource dialog box.
   
   
   

3. Complete the following fields:
   || Field || Description ||

   Pod	Pod to which the virtual cluster is assigned.
   Resource Type	A physical or virtual cluster. Choose virtual cluster.
   Provider Name	Source of the cluster. Select the Amazon EC2 provider type name.
   Available Resources	List of available virtual clusters. Select only those entries that correspond to the selected pod.
   Selected Resources	Virtual cluster(s) to be onboarded.

4. Select the virtual cluster with the same name as the selected pod, and click Add.
   
   All Amazon EC2 virtual clusters are depicted with 0 CPUs and 0 Memory. This is by design and is no reason for concern.
   The only virtual cluster that is compatible with the selected pod is a virtual cluster with a same name. Onboarding a virtual cluster with a different name will fail.
5. Click Onboard.

For detailed procedures, see Onboarding-compute-resources.

To create a compute pool

You create one compute pool per pod.

1. On the Resource Management > Compute > Compute Pools window, click the Create Compute Pools icon to open the Create Compute Pool dialog box.
   
   
   

2. Complete the following fields:
   || Field || Description ||

   Name	Unique name of the compute pool.
   Description	Description that distinguishes the container.
   Tags	Metadata that enhances the compute pool description.
   Pod	Pod (Availability Zone) to which the compute pool is assigned
   Resource Type	A virtual or physical cluster, a virtual resource pool, a virtual host, or a virtual disk repository. Choose virtual cluster.
   Provider Type	source of the resource. Select the Amazon EC2 provider type name.
   Vendor	Owner or seller of the resource type. Select Amazon.
   Architecture	Architecture of the microprocessor. Select x86_64.

3. Click Next to display the available resources.
   
   
   
4. Select the resources to add, and click Add.
5. Click Save.

Refer to Creating-compute-resource-pools for detailed procedures.

To create a Virtual Disk Repository pool for the onboarded pod

You create one Virtual Disk Repository per pod.

1. On the Resource Management > Compute > Compute Pools window, click the Create Compute Pools icon to open the Create Compute Pool dialog box.
   
   
   

2. Complete the following fields:
   || Field || Description ||

   Name	unique name of the virtual disk repository
   Description	Description that distinguishes the virtual disk repository.
   Tags	Metadata that enhances the virtual disk repository description.
   Pod	Pod to which the virtual disk repository is assigned.
   Resource Type	A virtual or physical cluster, a virtual resource pool, a virtual host, or a virtual disk repository. Choose virtual disk repository.
   Provider Type	Source of the resource. Select the Amazon EC2 provider type name.
   Vendor	Owner or seller of the resource type. Select Amazon.

3. Click Next to display the available resources.
   
   
   
4. Select the resources to add, and click Add.
5. Click Save.

For more information, see Creating-compute-resource-pools.

To import a network container blueprint to an onboarded pod

You can import multiple container blueprints.

1. On the Resource Management > Pods windows, select the onboarded pod (Availability Zone) and click the Import Network Container Blueprints icon.
   
   
   
2. In the Import Network Container Blueprints dialog box, from the drop-down list select the pod you want to assign the container blueprint. A list of available container blueprints is displayed. Each container blueprint is based on one of the following Amazon EC2 constructs:
   • Availability Zone — Designated as a geographic area, such as in BMC:us-west-2b, where BMC is the Amazon account alias.
   • Virtual Private Cloud — Designated with VPC in its name, as in BMC:VPC_vpc-6c06d105, where BMC is the Amazon account alias and vpc-6c06d105 is the VPC ID.
     
     Selecting either an Availability Zone or a Virtual Private Cloud blueprint determines where in AWS your EC2 instances will populate.
     
     
3. Select one or more container blueprints, and click Import.

For detailed procedures, see Importing Network Container Blueprints.

To create a network container for the onboarded pod and blueprint

You can create multiple network containers.
 For Amazon EC2 offerings, the network container is based on one of the following:

1. On the Resource Management > Network Containers window, click the Create Network Container icon to open the Create Network Container General Information dialog box.
   
   
   

2. Complete the following fields:
   || Field || Description ||

   Name	Unique name for the container.
   Description	Description that distinguishes the container.
   Pod	Pod (Availability Zone) to which the network container is assigned.
   Container Blueprint	Container blueprint (for an Availability Zone or Virtual Private Cloud) associated with the container and pod.
   Address	Leave blank.
   Mask	Leave blank.
   Tags	If needed, create or select tags, as described in Creating-tag-groups-and-tags.

3. Click Next to display the Additional Parameters dialog box.
   
   Because Amazon EC2 network containers do not accept additional parameters, leave all the parameter fields blank.
4. Click Submit.

For detailed procedures, see Creating Network Containers.

To map compute pools to the network container

1. On the Resource Management > Network > Network Containers window, choose a Network Container, and click the Manage Compute pool mappings icon to open the Network Container - Map Compute Pools dialog box.
   
   
   
2. Choose the Compute Pool type that you have defined from the Available Compute Pools list.
3. After making your Compute Pool type selection, click Add to move the entry to the Mapped Compute Pools list.
4. To remove existing Compute Pools from the current Mapped Compute Pools list, select the Compute Pool, and click Remove to move the entry back to the *Available Compute Pool*s list.
5. Click Save.

For more information, see Mapping-compute-pools-to-network-containers.

To map tenants to the network container

The mapping of Amazon account to BMC Cloud Lifecycle Management tenant is a many-to-many association. To illustrate, you have these possible mappings:

• A single Amazon account that maps to multiple BMC Cloud Lifecycle Management tenants
• A single Amazon account that maps to a single tenant
• Multiple Amazon accounts that map to a single tenant

1. On the Resource Management > Network > Network Containers window, choose a Network Container, and click the Manage Tenant mappings icon to open the Network Container - Map Tenants dialog box.
   
   
   
2. Choose a Tenant from the Available Tenants list. If necessary, enter search criteria in the Search text box and click the Search icon to retrieve matching tenants.
3. After making your Tenant selection, click Add to move the entry to the Mapped Tenants list.
4. To remove existing Tenants from the current Mapped Tenants list, select the Tenant, and click Remove to move the entry back to the Available Tenants list.
5. Click Save.

For more information, see Mapping-tenants-to-network-containers.

Where to go from here

You next define your service blueprint and prepare your service offering instance.