Creating options and option choices in the OpenStack Provider

BMC Cloud Lifecycle Management administrators must create options and option choices for the OpenStack Provider service offerings as per the cloud service provided by OpenStack, so that end users can provision a virtual machine (VM) and modify configurations after a VM is provisioned.

This topic contains the following sections:

• • Creating options and option choices for the OpenStack Provider
  • About the options for the OpenStack Provider

Creating options and option choices for the OpenStack Provider

To create an OpenStack Provider option, open the Options Editor and define the OpenStack Provider option, as shown in the following figure:

You must configure an option choice for the option created for the OpenStack Provider. For detailed steps, see to add options and option choices to service blueprints.

About the options for the OpenStack Provider

You must create the following options for an OpenStack Provider of the corresponding option types:

The following sections describes the options for the OpenStack Provider and the steps to be followed for creating the option choices:

Flavor option

Flavors define how many virtual CPUs an instance has, the amount of RAM, and the size of its ephemeral disks. OpenStack provides a number of predefined flavors that you can edit or add to. Users must select from the set of available flavors defined on their cloud.

Defining the Flavor option of request definition option type allows you to specify the cloud service sizes that the end user can specify or change during the provisioning of the offering. The cloud administrator uses the Flavor option to configure the service offering with all of the available sizes and options for VMs on OpenStack.

You can create VMs in an OpenStack Provider with a minimum memory size of 512 MB (m1.tiny size), and a maximum memory size of 16,384 MB (m1.xlarge size).

When you launch an instance, you must choose a flavor, which represents a set of virtual resources. For the Flavor option, you must create the option choices for blueprint configuration as a FunctionalModel parameter. You must create the choices of cloud service size based on the allowed sizes in OpenStack. Following is a list of sample sizes of OpenStack:

1. m1.tiny (1 VCPU, 1 disks, 512 MB memory)
2. m1.small (1 VCPU, 20 disks, 2048 MB memory)
3. m1.medium (2 VCPUs, 40 disks, 4096 MB memory)
4. m1.large (4 VCPUs, 80 disks, 8192 MB memory)
5. m1.xlarge (8 VCPUs, 160 disks, 16384 MB memory)

Steps to create the option choice for the Flavor option

1. Define the option choice for the m1.tiny flavor option choice at Blueprint Configuration > Service Definition > Parameters, as shown in the following figure:
   

    

   Note

   For more information, see Option Choices available when extending service blueprints.

2. Specify the following details for configuring an option choice of m1.tiny size, as shown in the following figure:
   

Update CPU and Memory option

The Update CPU and Memory option of Postdeploy Action type allows you to increase the CPU core and memory size of a provisioned VM.

Following are the option choices for Update CPU and Memory option in OpenStack:

• For the memory option, you can create choices of memory size based on allowed memory sizes in the OpenStack Provider. For example, you can create Microsoft Windows VMs in the OpenStack Provider with a minimum memory size of 256 MB and a maximum memory size of 16,384 MB. Each choice must be a multiple of 4, so you can have 256 MB, 1,024 MB, 2,048 MB, or 3,072 MB.
• For the CPU option, you can create option choices for 1, 2, 4, and 8 VCPUs.

Steps to create the option choice for the Update CPU and Memory option

1. Define the option choice for the Update CPU and Memory option at Blueprint Configuration > CPU Count or Memory Size, as shown in the following figure:
   
   
   

   Note

   For more information, see Option Choices available when extending service blueprints.

2. Specify the following details for configuring an option choice of m1.tiny size:

• 
  
  • CPU count, as shown in the following figure:
    
  • Memory Size, as shown in the following figure:
    

Add Disk option

The Add Disk option of Postdeploy Action  type allows you to increase the disk volume of a provisioned VM.

For the Add Disk option, you must create the option choices for blueprint configuration as Additional System Disk.

Steps to create the option choice for the Add Disk option

1. Define the option choice for the Add Disk option at Blueprint Configuration > Additional System Disk, as shown in the following figure:
   
   
   

   Note

   For more information, see Option Choices available when extending service blueprints.

2. Specify details for configuring an option choice for the Add Disk option, as shown in the following figure:
   

Install Software option

The Install Software option allows you to install software on a provisioned server. You can specify the software details to be installed on a provisioned server.

For the Install Software option, you must create the option choices for blueprint configuration as Software Packages.

Steps to create the option choice for the Install Software option

1. Define the option choice for the Install Software option at Blueprint Configuration > Software Packages, as shown in the following figure:
   
   
   

   Note

   For more information, see Option Choices available when extending service blueprints.

2. Specify the following details for configuring an option choice for the Install Software option, as shown in the following figure: