Setting up and using physical server provisioning

In this topic, the following sections describe the full process necessary to set up and use physical server provisioning in BMC Cloud Lifecycle Management.

Before you begin

Overview of BMC Server Automation configuration tasks for physical server provisioning

The following sections provide an overview of the required tasks performed in BMC Server Automation to provision servers using BMC Cloud Lifecycle Management.

To create or modify the system package type

In the BMC Server Automation console, the System Package Types tab on the Provisioning Configurations window lists the available system package types. Use the following procedure to modify one of the available system package types to meet your provisioning needs. If necessary, create your own custom system package type. For example, you might create a custom system package type to deploy an operating system based on an earlier Microsoft service pack. To create a custom system package type, see the BMC Server Automation online techincal documentation.

To modify an existing system package type

1. Select the System Package Types tab on the Provisioning Manager Configurations dialog box. A list of available OS packages is displayed. 
   
   
2. Double-click a system package type in the list to display the System Package Type dialog box.
3. For Windows, select the processor architecture under the Windows Architecture option.

4. Specify file paths for the OS and agent installers in the OS Installer Configuration and RSCD Installer Configuration fields. 
   
   This file path is relative to the root path of the file server that you specify when you provision a device. Because the system does not validate the file path string, ensure that it matches the file path defined for the file server. 
   
   No absolute path name is entered for the installers. Remember to use the appropriate path separator in the path name: backslash for Windows and forward slash for UNIX or Linux.

   Tip

   The file paths are usually located under the Datastore folder that you create for the PXE server. For more information, see Creating and stocking the data store in the BMC Server Automation online documentation.

5. For Linux, specify the boot kernel files that correspond to the OS image pxeboot files from the tftproot pxelinux directory in the Boot kernal file name and Boot image file name fields. 
   
   
6. For Windows, indicate the initial partition size (megabytes) or accept the default value in the Initial Partition Size field.
7. Click OK.

_{Back to top}

To create or modify the image files

The boot image (also referred to as preboot image) in BMC Server Automation is an object that contains a small operating system. This operating system, in turn, specifies how to start the bare metal machine or physical server and launch the installation of the actual operating system. WinPE is the boot image for Windows, and the Skip Linux pre-install method is the preferred boot image for Linux.

When executing a provisioning command, indicate which preboot image to use. BMC Cloud Lifecycle Management retrieves the preboot image in two ways:

• By selecting a hard-coded BOOT_IMAGE_ID property definition on the device. This property definition can have a default value if all physical server devices use the same boot image.

• By attempting to match an appropriate boot image ID from the manufacturer attributes in BMC Cloud Lifecycle Management with the device. BMC Cloud Lifecycle Management uses the PRODUCT_MANUFACTURER property on the BMC Server Automation provisioning image to determine the appropriate match.

  Note

  The preboot image is supposed to have the PRODUCT_MANUFACTURER property automatically defined from the image type.

  The procedure for creating a boot image file differs for Windows WinPE and Linux Gentoo.

To create a Windows WinPE boot image

Follow these summary guidelines to create a Windows WinPE boot image.

Make the necessary preparations on a system running the RSCD Agent:

• Install and configure the Windows Automated Installation Kit (WAIK), plus any additional utilities as required, as described in the BMC Server Automation online technical documentation  
• Download the BMC Server Automation provisioning files from BMC Support, as described in the BMC Server Automation online technical documentation
• Carefully read the documentation about configuring WAIK in the BMC Server Automation online technical documentation.

Create the Windows WinPE boot image:

• On the BMC Server Automation Console, open the Configuration > Provisioning Image Creation dialog box, and follow the four-step wizard process. 
  
  
• For the Boot Image Target Directory field, if applicable, specify a file path that resides under the updated /blfs/tftproot/ root directory path: for example, /blfs/tftproot/x64, where x64 indicates the processor architecture.
• Extract the WinPE boot files bootmgr.exe and pxeboot.0 so that the boot image can copy them to every TFTP server (application servers and repeaters).
• Above all, carefully read the documentation about Windows OS provisioning and WinPE boot files in BMC Server Automation online technical documentation.

To modify Windows image files

1. Select the Image Files tab from the Provisioning Manager Configurations dialog box to display a list of the available image types. Double-click the WinPE image type for the boot image you want to modify. The Edit Image File dialog box opens. 
   
   

2. In the Image Path field, specify the relative path to the Windows boot image (the wim file), which is defined under the /blfs/tftproot/ directory. For example, if the boot image resides under /blfs/tftproot/X86PC/pxelinux/winpe2_x64, then enter winpe2_x64.

   The wim file must have been created in the specified relative path: in this example, winpe2_x64.

3. If the system is 64-bit, verify that 64-bit Image is selected.
4. If the boot image is to be the default image based on WinPE version and processor architecture, select Set as default image.

To modify Linux image files

Starting in BMC Cloud Lifecycle Management 2.1 Service Pack 1 and later releases, you are no longer required to use the Gentoo boot image as long as the Skip Linux pre-install method is used.

_{Back to top}

To configure the PXE server

For both physical servers and bare-metal virtual machines, configure the PXE server. Before beginning the configuration steps, ensure that you have followed these guidelines:

• BMC recommends that you install the Preboot Execution Environment (PXE) server on a separate system rather than the same system where the BMC Server Automation Application Server is installed.
• If installing the PXE server on a Microsoft Windows system, configure and enable Internet Information Services (IIS). If installing on a Linux system, configure and enable Samba services.
• On the PXE server, set up a datastore directory to store server files, as in the following Windows example: 
  
  

Configuring the PXE settings

You must configure a number items in the Provisioning Manager Configurations dialog box of the BMC Server Automation Console.

1. From the BMC Server Automation Console, choose Configuration > Provisioning Configuration to display the Provisioning Manager Configurations dialog box.
2. Select the PXE tab, and enter values according to the following guidelines. 
   
   
3. Override the default values only when you have specific reasons to do so. For example, accept the Use Multicast option and any supplied multicast address.
4. In the Interface to bind field, enter the Ethernet card (for example, eth1) that the client uses to access the provisioning network.
5. Enter a network domain in the Domain field.
6. Use multicast as the internet protocol; do not select the Use Broadcast option.

Configuring the TFTP settings

1. Select the TFTP tab from the Provisioning Manager Configurations dialog box. 
2. Override the default values only when you have specific reasons to do so.
3. In the IP Address field, enter the IP address of the network interface card (NIC) that is bound to the provisioning network.

4. In the Base directory field, enter the full path of the tftproot directory, which is the base directory of the file system used to store operating system bootstrap programs to be downloaded.

   Recommendation

   If you are working in an environment with multiple PXE servers, BMC recommends that you create a new tftproot directory under the blfs folder: that is, /blfs/tftproot.

   By default, the tftproot directory resides under the NSH scripts folder: /opt/bmc/bladelogic/pxe/NSH/tftproot. Because the blfs folder acts as the client's storage folder on application servers and repeaters, it can also function as the storage folder for OS boot images.

   After you create the /blfs/tftproot directory, copy the contents of the existing /opt/bmc/bladelogic/pxe/NSH/tftproot directory to the newly created /blfs/tftproot directory.

   Then edit the pxe.conf file, located under /opt/bmc/bladelogic/pxe/NSH/br, to

   • indicate the revised tftproot directory path
   • enable the local configuration file
   • set the correct interface of the provisioning network

Some hardware models such as the Dell PowerEdge T310s/R710s and the HP DL380G6S, have newer firmware versions that increase the MFTFP timeout from a few seconds to up to ten minutes. Consequently, the provisioning process takes longer.

Guidelines for setting network shares in the PXE server environment

Follow these guidelines to establish network share drives in Linux and Windows environments.

Configuring PXE server options

1. Select BMC Software > BladeLogic Server Automation Suite > PXE-TFTP Server Configuration and Diagnostics Tool to display the PXE/TFTP Server Configuration dialog box. 
   
   
   
   
2. Select the Database tab of the PXE/TFTP Server Configuration dialog box, and enter the connection parameters of the database server.
3. Select the PXE Options tab of the PXE/TFTP Server Configuration dialog box, and specify details about the network interface card (NIC) to which the virtual machine will be communicating with the PXE server. These details include the name of the interface, the multicast address, and the listening port.

4. Select the TFTP Options tab of the PXE/TFTP Server Configuration dialog box, and enter the details, including the TFTP root directory where the root image files and the IP address of the TFTP server are stored. 

   The PXE MAS Options and the PXE MAS Data Source tabs are optional.

5. After completing the PXE and TFTP options, select the Diagnostics tab of the PXE/TFTP Server Configuration dialog box, and click Run Diagnostics to check the status of your PXE and TFTP server processes.

   Note

   The diagnostic log will display an error message beginning with Unable to open Datagram Socket on port ... if the PXE service is running on the specified port number. You can safely ignore the error message.

_{Back to top}

To configure the PXE datastore

Complete the steps in the following sections to configure the PXE datastore instance.

To create a PXE datastore instance

The Preboot Execution Environment (PXE) datastore is where boot image files, OS installers, and RSCD agent installers are stored. It is a subclass of the Property Dictionary. You must

• Create an instance of the PXE datastore
• Assign it a name in a required format that uses a pod name in the suffix
• Specify the full path to the datastore in the Full Path property

When a service offering request is made to provision a server, BMC Cloud Lifecycle Management searches the list of available datastores until it finds a match with the specified pod name.

1. In the BMC Server Automation Console, select Configuration > Property Dictionary View to display the Property Dictionary. 
   
   
   
   
2. Expand Built-in Property Classes and locate the Datastore class.
3. Expand the Datastore class and select PXE Datastore.
4. Select the Instances tab in the adjoining pane.

5. Click Add New Property Set Instance to define the datastore instance and its properties.

   Important

   The name of the PXE datastore instance should follow this formatting convention:
   CSM Datastore - name of pod (remember to add spaces on both sides of the hyphen). The pod you designate should be the pod you intend to onboard and provision with the physical server, bare metal virtual machine, or virtual guest server.

6. When defining properties for the datastore instance, ensure that the FULL_PATH property points to the full path of the datastore directory you defined earlier on the PXE server, as shown in this Microsoft Windows example.
   
   
   
   
7. Follow these guidelines:
   • For the LOCATION property, enter the IP address or a DNS-resolvable host name of the PXE server where the datastore resides.
   • For the VIRTUAL_DIR property, enter the name of the network share established for HTTP access to the OS images.
   • If the datastore network share is password protected, enter a user name and a password for the USERNAME and PASSWORD properties.
8. Click OK to save the data.

You can repeat these steps to create multiple PXE datastore instances.

Deploying a new VM to a local datastore

When provisioning a new VM to a local datastore (in contrast to a shared datastore), edit the providers.json file on the Platform Manager (OSGi) server.

1. Log in to the computer where the Platform Manager product is installed.
2. Open the providers.json file in a text editor.
   By default, you can find the providers.json file in the BMCInstallSoftware\BMCCloudLifeCycleManagement\Platform_Manager\configuration folder.

3. Change the USE_LOCAL_DATASTOREattribute value from false (the default) to true.

   },
       "attributeValue" : "true",
       "cloudClass" : "com.bmc.cloud.model.beans.AccessAttributeValue",
       "guid" : "7ef9f6e1-86ab-4f6b-8dc1-fceed3010c98",
       "name" : "USE_LOCAL_DATASTORE"
       } ],
   

4. Save the file.

Configuring the DHCP server

The BMC Server Automation provisioning process requires a DHCP server, which gives the computer being provisioned an IP address and (in a single-database environment) the location of the Application Server. The following topics describe the unique configuration needed so that a DHCP server can support BMC Server Automation's provisioning process:

BMC Server Automation requires you to:

• Have the TFTP server and the PXE Server reside on the same host computer
• Provide the IP address of the BMC Server Automation provisioning server
• Define a DHCP option field, which lets the computer being provisioned differentiate between a DHCP server and proxy DHCP servers

The following table describes how to define the DHCP option fields.

_{Back to top}

To create a system package

In order to perform an unattended installation of an operating system, create a system package (or modify an existing package) in BMC Server Automation for each server configuration you want to install.

To enable successful publishing of system packages for BMC Cloud Lifecycle Management, store the packages in the CSM_OS_Packages subfolder of the Depot folder in the navigation tree of the BMC Server Automation Console (Depot > CSM_OS_Packages): 

To create and define a system package

1. Using BMC Server Automation, perform these initial steps necessary to create a system package.
   The system package is created and opens in the content editor.
2. Define the system package by specifying all of its settings.
   1. See System package panels (OS specific) for detailed instructions about supported operating systems.

   2. Review special considerations when defining system packages to determine if these instructions apply to your system package.

      Note

      When defining a system package, note the presence of the Select Property icon next to various input fields. Whenever you see this icon next to an input field, it indicates that you can insert a parameter that refers to a local property that supplies the value for the field.

3. When entering or modifying parameters for the system packages, keep in mind these guidelines for BMC Cloud Lifecycle Management (Windows or Linux operating system):
   • Under the Basic Config tab, enter ??NAME?? in the Computer name field. When the system package is selected at provisioning time, BMC Cloud Lifecycle Management supplies the hostname of the server to be provisioned or the IP address (if configured to do so).
   • In the Local Properties tab, specify the name of the PXE datastore instance for the DATASTORE variable. Use the same format convention: CSM Datastore - <name of pod>.
4. When you finish defining the system package, select File > Save.

Special considerations when defining system packages

Click any of the following tabs to review OS-specific considerations when defining system packages.

echo "DEVICE=eth1" > /etc/sysconfig/network-scripts/ifcfg-eth1
echo "HWADDR=??ETH1_MAC_ADDRESS_CD??" >> /etc/sysconfig/network-scripts/ifcfg-eth1
echo "BOOTPROTO=??ETH1_BOOTPROTO??" >> /etc/sysconfig/network-scripts/ifcfg-eth1
echo "ONBOOT=yes" >> /etc/sysconfig/network-scripts/ifcfg-eth1
echo "IPADDR=??ETH1_IPADDR??" >> /etc/sysconfig/network-scripts/ifcfg-eth1
echo "NETMASK=??ETH1_NETMASK??" >> /etc/sysconfig/network-scripts/ifcfg-eth1
echo "GATEWAY=??ETH1_GATEWAY??" >> /etc/sysconfig/network-scripts/ifcfg-eth1

echo "DEVICE=eth1:0" > /etc/sysconfig/network-scripts/ifcfg-eth1:0
echo "HWADDR=??ETH1_1_MAC_ADDRESS??" >> /etc/sysconfig/network-scripts/ifcfg-eth1:0
echo "BOOTPROTO=??ETH1_BOOTPROTO??" >> /etc/sysconfig/network-scripts/ifcfg-eth1:0
echo "ONBOOT=yes" >> /etc/sysconfig/network-scripts/ifcfg-eth1:0
echo "IPADDR=??ETH1_1_IPADDR??" >> /etc/sysconfig/network-scripts/ifcfg-eth1:0
echo "NETMASK=??ETH1_1_NETMASK??" >> /etc/sysconfig/network-scripts/ifcfg-eth1:0
echo "GATEWAY=??ETH1_1_GATEWAY??" >> /etc/sysconfig/network-scripts/ifcfg-eth1:0

After you create the system package

After creating a system package, add a Network Shell (NSH) script called CSM_Delayed_Reboot to the Depot subfolder CSM_Scripts.

The script should look similar to the following example:

_{Back to top}

To create the Deploy Job

This section provides high-level guidelines for creating a BLPackage Deploy Job. When you perform this procedure, you are creating software packages that you can use when defining an application in a service blueprint in BMC Cloud Lifecycle Management. Applications let you deploy software on VMs that you provision using the cloud.

Because the BLPackage Deploy Job supports blueprint parameterization, BMC recommends that you create a BLPackage Deploy Job instead of using an application component template.

For detailed information, see the following topics in the BMC Server Automation online technical documentation:

• Working with properties
• Working with components and component templates
• Deploying files and applications using packages and depot objects
• Creating and modifying Software and BLPackage Deploy Jobs
• If you plan to create an application component template, use BMC Server Automation to create Software Deploy Jobs to install applications on target virtual machines.

To create a BLPackage Deploy Job

BMC Server Automation BLPackages can be used to install applications on target virtual machines. A BLPackage is a collection of server assets, software packages, and an XML instruction set. A BLPackage can include installers, files, configuration objects, and so on. The BLPackage can also include parameterized property values among its server assets. The parameterized property values must match exactly the blueprint parameter values used by the service blueprint.

_{Back to top}

To execute the Publish Product Catalog Job

The Publish Product Catalog Job in BMC Server Automation retrieves a list of virtual guest packages and system packages from specially named BMC Server Automation folders, and publishes those to the Product Catalog. The Product Catalog is an application that is installed on the BMC Atrium CMDB and stores your hardware and software metadata. It is also known as the DML (Formerly DSL).

In BMC Server Automation, ensure that you have created the object to be published and stored the object in its appropriate folder, as described above.

To publish the product catalog

1. If you have already configured the CMDB in your BMC Server Automation Console, proceed to Step 4.

2. Choose Atrium Integration > Configuration from the Configuration menu and enter the following BMC Atrium CMDB details on the AR/CMDB Configuration tab:
   AR/CMDB Configuration parameters

   Parameter	Description
   Host Name/IP Address	Host name or IP address of the computer where BMC Atrium CMDB is installed.
   CMDB Port	Port used for communicating with BMC Atrium CMDB. Note If you are using a portmapper service for AR system, enter a value of 0.
   CMDB User	User Name for connecting to BMC Atrium CMDB.
   CMDB Password	Password for connecting to BMC Atrium CMDB.

3. Click Test Connection to verify that the credentials that you entered are correct.
4. Right-click the Jobs > CSM_Jobs folder, and select New > Publish Product Catalog Job.
5. In the General panel, name the job and give it a description.
6. In the Default Notifications panel, define default notifications that are generated when the job completes. Default notifications can take the form of e-mails or SNMP traps. For more information, see the Managing jobs topic in the BMC Server Automation online technical documentation.
7. In the Schedules panel, schedule the job to execute immediately, at a specific time in the future, or on a recurring basis, and define notifications that are issued when the job runs. For more information, see the Managing jobs topic in the BMC Server Automation online technical documentation.
8. In the Properties panel, there is a list of properties automatically assigned to each object. In this list, you can modify the value of any properties that are defined as editable. For more information, see the Setting values for system object properties topic in the BMC Server Automation online technical documentation.
9. In the Permissions panel, grant roles access to any objects created in the system, such as jobs, servers, or depot objects. Using the Permissions panel, you can add individual permissions to an object. You can also set permissions by adding access control list (ACL) templates or ACL policies. For more information, see the Defining permissions for a system object topic in the BMC Server Automation online technical documentation.
10. Click Finish to run the Publish Product Catalog Job.
11. Review the job execution logs to verify that content created within the specially named folders in BMC Server Automation has been published into the BMC Cloud Lifecycle Management product catalog.

Viewing published objects in BMC Cloud Lifecycle Management

Objects published to the Service Catalog are available to the BMC Cloud Lifecycle Management Service Designer workspace, where they can be added to service blueprint components.

For more information about defining service blueprints, see Creating, copying, or editing a service blueprint. For more information about PaaS provisioning, see Setting up and using PaaS provisioning.

_{Back to top}

Overview of BMC Cloud Lifecycle Management configuration tasks for physical server provisioning

After completing the configuration steps to prepare the physical server for provisioning in BMC Server Automation, launch the BMC Cloud Lifecycle Management Administration console. In the console, establish the foundation for the provisioning service by onboarding and creating the related BMC Cloud Lifecycle Management resources.

The following sections provide an overview of this setup process. Each section provides a link to more details of each procedure.

To onboard the pod containing the PXE datastore instance

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>.

1. From the BMC Cloud Lifecycle Management Administration Console, click the vertical Workspaces menu on the left side of the window and select Resources.
2. Under Quick Links at left, click Pods under the General section.
3. Click the Onboard Pod icon . The Onboard Pod dialog box is displayed.
    
4. Click the Provider Name menu button to select the resource provider instance for the pod. The default network resource provider is listed as BBNA for BMC Network Automation.
5. Select the pods that you want to onboard.
6. Click Onboard to onboard the selected pods and close the dialog box.

For a more detailed procedure, see Onboarding and offboarding network pods.

_{Back to top}

To import the container blueprint

The next step is to import the container blueprint that the Publish Product Catalog Job has made available to BMC Cloud Lifecycle Management.

1. From the BMC Cloud Lifecycle Management Administration Console, click the vertical Workspaces menu on the left side of the window and select Resources.
2. Under Quick Links on the left, click Pods under the General section.
3. Click the Import Network Container Blueprints icon .
   The Import Network Container Blueprints dialog box is displayed. The dialog shows the Pod name, the version number (if the pod has been updated), and a description (if available).
    
4. Select the network container blueprints that you want to import.
5. Click Import to onboard the selected blueprints and close the dialog box.

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

_{Back to top}

To create the network container

To create a new network container, you launch a wizard that contains three dialog boxes. In the first dialog box, you specify the unique name of the container, its pod, network container blueprint, NAT range (if applicable), and any tags. In the second dialog, you specify networks, firewalls, and associated load balancers. In the third dialog, you enter any additional parameters.

1. From the BMC Cloud Lifecycle Management Administration Console, click the vertical Workspaces menu on the left side of the window and select Resources.
2. Under Quick Links on the left, click Network Containers under the Network section.
3. Click the Create Network Container icon 
   The Create Network Container wizard is displayed.
   
   

4. Complete the following fields:

   Field	Description
   Name	Required. Enter a unique name. The name can include only alphanumeric characters. It cannot include symbols or special characters such as a single quote (') or dollar sign ($).
   Description	Provide a description that helps to distinguish this container.
   Tags	Metadata that helps to define and classify the network container. Click the Add Tag icon to open the Tag Details dialog box from where you select or add a tag. See Creating tag groups and tags.
   Pod	Select an appropriate pod from the list of available ones.
   Container Blueprint	Select a network container blueprint from the list of available ones. The selection of the network container blueprint determines whether the container is dynamic and whether it supports Network Address Translation.
   NAT Address Pools	This table shows the pools of registered IP addresses to which Network Address Translation can map an unregistered IP address. This section is enabled if the selected container blueprint supports Network Address Translation.
   Add NAT Address Pools	Use the following fields to add a new NAT Address Pool: Address - Enter a single IP address to identify the starting point of the address range. Mask - 24\- or 32-bit mask that divides the IP address into subnets and identifies the available hosts in the network. Click Add to add the new NAT Address Pool. The Address in combination with the Mask defines the address range to be allocated for the network container. These fields are enabled if the selected container blueprint supports Network Address Translation.

5. Click Next to open the Dynamic Components dialog box. It displays the available networks and corresponding load balancers. For details, see Managing dynamic components for network containers.

The container will be provisioned on the network by BMC Network Automation using the specified network container blueprint.

For a more detailed procedure, see Creating network containers.

_{Back to top}

To onboard resources for physical servers

Before onboarding a physical server, ensure that the server is powered on. In addition, check whether values are assigned to properties in the Device class of the Property Dictionary in the BMC Server Automation console, as described in the following procedure.

To onboard the servers, complete the following steps:

1. From the BMC Cloud Lifecycle Management Administration console, click the vertical Workspaces menu on the left side of the window and select Resources
2. Under Quick Links on the left, click Resources under the Compute section.
3. Click the Onboard Resource icon .
   The Onboard Resource dialog box is displayed.
   
4. Select the Pod, Provider Name, and Resource Type for the resource you want to onboard. By selecting a Resource Type, you can onboard resources from a virtual cluster or physical server. When you onboard a virtual cluster, you are also onboarding the virtual hosts, virtual resource pools, and virtual disk repositories (also called datastores) associated with the virtual cluster. An alphabetical list of resources is displayed in the Available Resources table.
5. Find the resources that you want to add.
   • You can page through a long list by clicking the Page button .
   • You can search for resources by entering a search string in the Search box and clicking the search icon .

Select one or more resources and click the Add button to move them to the Selected Resources table, or drag and drop resources from the Available Resources table to the Selected Resources table. When finished, click Onboard.

For a more detailed procedure, see Onboarding and offboarding compute resources.

_{Back to top}

To create compute resource pools

1. From the BMC Cloud Lifecycle Management Administration Console, click the vertical Workspaces menu on the left side of the window and select Resources.
2. Under Quick Links on the left, click Compute Pools under the Compute section. The list of current compute resource pools is displayed.
3. Click the Create Compute Pool icon . The Create Compute Pool dialog box is displayed.
   
4. Type a name for this pool.
5. Type a useful description. Descriptions can help you distinguish pools from each other and can help you find a pool by using Search.
6. If needed, create or select tags, as described in Creating tag groups and tags.
7. From the Pod menu, select the network pod to which this pool will belong.

8. From the Resource Type menu, select the type of resources that this pool will contain:

   Note

   If you would like to place VMs on DRS-enabled clusters, make sure to set up Compute Pools of VirtualClusters. If you would like to place VMs on non-DRS clusters, make sure to setup your Compute Pools of VirtualHosts or VirtualResourcePools.

   • Virtual Cluster—You must also pick the Vendor and HW Architecture of the cluster. 

   • Physical Server—You must also pick the HW Architecture of the server. 

   • Virtual Resource Pool—You must also pick the Vendor and HW Architecture of the virtual resource pool. 

   • Virtual Host—You must also pick the Vendor and HW Architecture of the virtual host. 

   • Virtual Disk Repository—You must also pick the Vendor of the virtual disk repository. 

9. From the Provider Type menu, select the provider for this pool. 

10. From the Vendor menu, select the vendor for the compute resources in this pool. 

11. From the Hardware Architecture menu, select the architecture type for the compute resources in this pool. 

12. Click Next.
    The Create Compute Pool Resources dialog box is displayed.
    
    

    • Availability column—This column is displayed for the Virtual Resource, Virtual Host, and Virtual Disk Repository resource types. A value of Available indicates that the virtual resource can be used as an active resource in the compute pool. Items displayed as Unavailable have been marked for deletion and should not be included as a compute resource for the pool. 

    • Type column—This column is displayed for the Virtual Disk Repository resource type. If you are adding a compute pool with a Virtual Disk Repository resource type, you will also see a Type column on this dialog box. If the resource is a VMware datastore cluster, you will see the following format in the Type column: Cluster:<fileType>. For example, a VMware Virtual Machine File System (VMFS) data store cluster would be displayed in the Type column as Cluster: VMFS. 

13. Click Save to create an empty pool or continue with the following steps to add resources to the pool. 

14. Find the resources that you want to add. 

    • You can page through a long list by clicking the Page button . 

    • You can search for resources by entering a search string in the Search box and clicking the search icon . 

15. 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. 

16. Click Save.

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

_{Back to top}

To import tenants

1. From the Administration Console, click the vertical Workspaces menu and select Tenants.
2. In the Tenant Management pane, click Create or import tenant .
3. In the Add Tenant dialog box, enter the required details.
   Fields marked with an asterisk (*) are mandatory. 
   1. Select the Import Existing Tenant button.

   2. From the Company Name list, select the tenant that you want to import.
      The Company Name list comprises the tenants created in BMC Remedy IT Service Management Foundation, which are not yet imported. After you select the tenant, the details are displayed. You cannot edit the tenant details from BMC Cloud Lifecycle Management.

      Note

      You cannot import a tenant if the location for the tenant is not specified in BMC Remedy ITSM Foundation.

   3. Click the Contract End Date calendar icon and select the date when the tenant's users will no longer to be able to request cloud services in the BMC My Cloud Services Console.
      

      Note

      The Contract Start Date is set to the date that you onboard the tenant and you cannot change it. The Contract Start Date defaults to the start of the day, at 12:00 A.M. To increase the the length of the contract to the end of the day, add an additional day. 

       

   4. From the list of Available Entitlement Packages, select the packages you want to apply to this tenant.
   5. Click Add > to move them to the Selected Entitlement Packages area. 
      You can use the search field to search for the preferred entitlement package. For details about the entitlement packages, see Creating entitlement packages.
   6. Click the Quotas tab to define the quota for the tenant. 
      By default, the Unlimited check box is selected for a tenant. For details about quota, see Setting and managing quota. 
   7. If you want to specify a limited quota for the tenant, perform the following steps in the Allocation area:
      1. Clear the Unlimited check box for the Server, CPU Count, Memory (GB), and the Local Storage (GB) fields.
      2. In the Tenant Quota text box for the Server field, enter the number of servers that you want to assign to the tenant. 
      3. In the Tenant Quota text box for the CPU Count field, enter the number of CPUs that you want to assign to the tenant.
      4. In the Tenant Quota text box for the Memory (GB) field, enter the memory in GB that you want to assign to the tenant.
      5. In the Tenant Quota text box for the Local Storage (GB) field, enter the local hard disk in GB that you want to assign to the tenant.  
4. Click Add.
   The tenant is imported successfully.

To verify whether the tenant is onboarded successfully, click the Activities tab. The Update Tenant Quota activity and its status are displayed. 

For a more detailed procedure, see Creating and importing tenants.

_{Back to top}

To create entitlement packages

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

1. From the BMC Cloud Lifecycle Management Administration Console, click the vertical Workspaces menu on the left side of the window and select Service Catalog.
2. Click the Entitlement Packages tab.
   The Packages workarea is displayed.
3. Click the Create Entitlement Package icon .
   The Package Details dialog box is displayed.
   
4. Enter a name for the package.
5. Enter a description.
6. In Company, select the tenant company for the package or select Global to make the package available to all companies.
7. You can enter or select a package group.
   Package Group marks a package as being part of a group. The Package Group value is not used anywhere else.
8. In the Available Requestable Offerings (SRDs) table, select the offerings that you want to make available to the selected company.
9. Click Add to move the offering to the Selected Requestable Offerings (SRDs) table.
   You can also drag and drop entitlement packages from one table to the other.
10. Click Save.
11. Click Close.

You can now associate the new entitlement package with a particular tenant company, as described in Selecting tenant entitlement packages.

For a more detailed procedure, see Creating entitlement packages.

_{Back to top}

To map compute resource pools to network containers

1. From the BMC Cloud Lifecycle Management Administration Console, click the vertical Workspaces menu at left and select Resources.

2. Under Quick Links at left, click Network Containers under the Network section.

3. Select the network container to which you want to map one or more resource pools.
4. Click Manage Pool Mappings .
   The Map Pools dialog box opens.
    
5. Find the resource pools that you want to add to the network container:
   • You can page through the list by clicking the Page button .
   • You can search for resource pools by entering a search string in the Search box and clicking Search .
6. Select one or more resource pools in the Available Pools table and click Add to move them to the Mapped Pools table.
   You can also drag and drop resource pools from the Available Pools table to the Mapped Pools table. 
7. Click Save.
   The selected pools are mapped to the network container. 

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

_{Back to top}

To map tenants to network containers

1. From the the BMC Cloud Lifecycle Management – Administration Console, click the vertical Workspaces menu and select Resources.
2. Under Quick Links > Network section, click Network Containers.
3. Select the network container to which you want to map one or more tenants.
4. Click Manage Tenant Mappings .
   The Map Tenants dialog box is displayed for the selected network container. In the Name field, the name of the tenant is displayed. In the Available Tenants table the list of onboarded tenants is displayed.
   

5. Select one or more tenants from the tenants table and click Add >.
   The selected tenant or tenants are moved to the Mapped Tenants table. You can search for a tenant by using the Search field.

   Note

   The Search field is case-sensitive.

6. Click Save. 
   The selected tenant or tenants are mapped to the network container.  

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

_{Back to top}

To define the service blueprint

Prior to defining the service blueprint, review the prerequisites.

1. Do one of the following:

   If you want to...	Complete these steps
   Create a new blueprint	In the Service Designer workspace, click Create New, and then select the type of blueprint you want to create. A new service blueprint is opened in the Blueprint Editor. By default, you begin working in Definition 1. If you are creating an Application, Server, or PaaS Blueprint, your blueprint will contain only one application, server, or PaaS database object. Click Save. Enter a unique name for your blueprint to describe the application or server type (for example, LAMP Gold or MediaWiki). Provide a Description. Click OK.
   Copy an existing blueprint	In the Service Designer workspace, click a service blueprint in the Blueprint Library. The service blueprint appears in view-only mode. Select Version > Clone. Enter a unique name for your blueprint to describe the application or server type (for example, LAMP Gold or MediaWiki). Click Create Copy. The new service blueprint is opened as a working copy and is available to edit.

2. As needed, add and define the components in your blueprint.

_{Back to top}

To add components and define compute resources

Whether creating, copying, or editing a service blueprint, you can add several different types of objects, and define network connections between those objects in many ways. The procedures referred to in the table below offer a suggested path through the initial creation process, though you can add some or all of these objects in almost any order.

_{Back to top}

To create the service offering

Use the Service Catalog to create services, which are composed of one or more service offerings and requestable offerings. You create services and offerings to provide cloud services that your user can request. For overview information about services, see Services overview.

Except storage services, a service blueprint is required for all services, as described in Building service blueprints. You can start creating the service without a service blueprint, but you must select a service blueprint in order for the service to be functional.

1. Create a new service, as described in Creating new services for the Service Catalog.
2. Create a service offering, as described in Creating a service offering.
3. Create a requestable offering, as described in Creating a requestable offering.
4. Create options for services, as described in Service Catalog options and option choices.

_{Back to top}

To make the provisioning request

1. Access Workspaces > Service Instances to display the Service Instances workspace, and click the New Service Request icon to display the New Service Request dialog box.
2. In the New Service Request dialog box, click the server provisioning service you want to request to display the Submit Request dialog box.
3. Enter the data in the required fields to complete the request for an instance of the service request. You can click Next to review the details.
4. Click Submit. The request is added to the Pending Activity list in the Service Instances window.

The request status is displayed in the Pending Activity list of the Service Instances window. You can double-click on the service request to see its detailed information.

For more detailed procedures, see Requesting cloud services.

Related topics

Setting up and using PaaS provisioning

Setting up and using bare-metal VM provisioning

Setting up and using VM provisioning (from VMware VM template)