Unsupported content This version of the documentation is no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments.

Populating the Service Catalog for the Azure provider


BMC Cloud Lifecycle Management administrators must create options and option choices for the Azure Provider service offerings as per the cloud service provided by Microsoft Azure, so that end users can provision a virtual machine (VM) and modify the configurations after a VM is provisioned. You then add the options and option choices to the Service Catalog so that they can be used with the Azure service offerings you create.

Note

You cannot specify your own CPU or memory sizes for the virtual machines (VMs) provisioned using Azure Provider. You must create the Azure Instance option choices only as per the cloud service sizes available in Microsoft Azure; for example, ExtraSmall with a Shared CPU core and 768 MB memory.

This topic contains the following sections:

About the options for the Azure Provider

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

Option Name

Option Type

Azure Instance (4.6.02 and earlier)

Request Definition

Azure Instance Family (4.6.03 and later)

Request Definition

Postdeploy Action

Postdeploy Action

Postdeploy Action

Postdeploy Action

Postdeploy Action 

For more information, see the "Option types" section in Configuring-end-user-Option-Choices-in-service-blueprints.

Back to top

To create options and option choices for the Azure Provider

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

UpdCPUMem-Opt.png

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

Azure Instance option 

Note

 BMC Cloud Lifecycle Management 4.6.03 added the more flexible means of automatically choosing the instance type based on the CPU and memory values (and the instance family), as described below in Azure Instance Family option.

The Azure Instance option allows you to specify the cloud service sizes that the end user can specify or change while provisioning the offering. The cloud administrator uses the Azure Instance option to configure the service offering with all of the available sizes and options for virtual machines on Microsoft Azure. 

In an Azure Provider, you can create VMs with a minimum memory size of 768 MB (ExtraSmall size), and a maximum memory size of 56 GB (A7 size). For detailed information about the available sizes and options for virtual machines on Microsoft Azure, see Virtual Machine and Cloud Service Sizes for Azure in the Microsoft online technical documentation.

For the Azure Instance option, you must create option choices for blueprint configuration as a Functional Model parameter. You must create the choices of cloud service size based on the sizes allowed by Microsoft Azure. The available sizes of Microsoft Azure are: 

  • ExtraSmall (shared CPU core, 768 MB memory)
  • Small (1 CPU core, 1.75 GB memory)
  • Medium (2 CPU core, 3.5 GB memory)
  • Large (4 CPU core, 7 GB memory)
  • ExtraLarge (8 CPU core, 14 GB memory)
  • A5 (2 CPU core, 14 GB memory)
  • A6 (4 CPU core, 28 GB memory)
  • A7 (8 CPU core, 56 GB memory)

To create the option choice for the Azure Instance option

  1. Define the the Azure Instance option choice at Blueprint Configuration > Service Definition > Parameters, as shown in the following figure:
    image2014-1-29 13:51:19.png
    Note: For more information, see Option-Choices-available-when-extending-service-blueprints.
  2. Specify the details for configuring an option choice of ExtraSmall size, as shown in the following figure:
    AddDsk-optchoice.png

Back to top

Azure Instance Family option 

The Azure Instance Family option introduced in 4.6.03 and later versions allows you to specify the instance family or instance type series details that the end user can specify or change while provisioning the offering. The cloud administrator uses the Azure Instance Family option to configure the service offering with the correct instance type that belongs to the corresponding instance family for virtual machines on Microsoft Azure.

Instance_Family_option.jpg 

In the Azure Provider, you can create VMs using the Standard tier: A-series with a minimum memory size of 768 MB (Standard_AO size), and a maximum memory size of 56 GB (Standard_A7 size). 

Note

For detailed information about the available sizes and options for virtual machines on Microsoft Azure, see Sizes for Cloud Services and Sizes for virtual machines in Azure.

For the Azure Instance Family option, you must create option choices for blueprint configuration as a Functional Model parameter. You must create the choices based on the allowed instance family series in Microsoft Azure. The available series for Microsoft Azure are:

  • A-series
  • A-series - compute-intensive instances
  • D-series
  • Dv2-series
  • DS-series
  • DSv2-series
  • G-series
  • GS-series

To create the option choice for the Azure Instance Family option

  1. Define the the Azure Instance Family option choice at Blueprint Configuration > Service Definition > Parameters. For more information, see Option-Choices-available-when-extending-service-blueprints.
  2. Specify the details for configuring an option choice of DS-Series, as shown in the following figure:

    Azure_series_config_param.jpg

Back to top

Update CPU and Memory option

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

Note

For detailed information about the available sizes and options for virtual machines on Microsoft Azure, see Virtual Machine and Cloud Service Sizes for Azure in the Microsoft online technical documentation.

For the Update CPU and Memory 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 following sizes allowed by Microsoft Azure: 

  • ExtraSmall (shared CPU core, 768 MB memory)
  • Small (1 CPU core, 1.75 GB memory)
  • Medium (2 CPU core, 3.5 GB memory)
  • Large (4 CPU core, 7 GB memory)
  • ExtraLarge (8 CPU core, 14 GB memory)
  • A5 (2 CPU core, 14 GB memory)
  • A6 (4 CPU core, 28 GB memory)
  • A7 (8 CPU core, 56 GB memory) 

To create the option choice for the Update CPU and Memory option

  1. Define the Update CPU and Memory option choice at Blueprint Configuration > CPU Count or Memory Size, as shown in the following figure:
    UpdCPUMem-OptChoice1.png
    Note: For more information, see Option-Choices-available-when-extending-service-blueprints.
  2. Specify the following details for configuring an option choice of ExtraSmall size:

    • CPU count, as shown in the following figure:
      UpdCPU-OptChoice1.png
    • Memory Size, as shown in the following figure:
      UpdMem-OptChoice1.png

Back to top

Add Disk option

The Add Disk option 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.

Note

You can create the option choice for disk size in the 1-1024 GB range only, as shown in the following figure:

AddDsk-optchoice3.png

To create the option choice for the Add Disk option:

  1. Define the Add Disk option choice at Blueprint Configuration > Additional System Disk, as shown in the following figure:
    AddDsk-optchoice1.png
    Note: For more information, see Option-Choices-available-when-extending-service-blueprints.
  2. Specify the following details for configuring an option choice for the Add Disk option, as shown in the following figure:
    AddDsk-optchoice2.png

Back to top

Add Server option 

The Add Server option allows you to add a new VM to an existing service instance. You can specify the number of VMs to be added to an existing service instance.

Note

  1. The VMs of an existing service instance must not have the NAT IP address enabled.
  2. The Add Server post-deploy action is applicable only on single-tier, provisioned VMs and does not apply on multitier, provisioned VMs.

For the Add Server option, you must create the option choices for blueprint configuration as Add Server.

To create the option choice for the Add Server option:

  1. Define the Add Server option choice at Blueprint Configuration > Add Server, as shown in the following figure:
    AddServ-OptChoice1.png
    Note: For more information, see Option-Choices-available-when-extending-service-blueprints.
  2. Specify the following details for configuring an option choice for the Add Server option, as shown in the following figure:
    AddServ-OptChoice.png

    Note

    • Number of Instances specifies the number of VMs to be provisioned by using the Add Server post-deployment action. You must create only one instance.
    • Ensure that User Entry is set to Enabled to allow the user to log on to the newly provisioned VM by using the specified user name and password when adding a new VM.

Back to top

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. 

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:
    SwOpt.png
    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:
    SwOpt1.png

Back to top

Add Local User option

The Add Local User option allows you to add local user on a provisioned server. You must specify the User Name and Password parameters to enable user provisioning on the Azure VM. 

For the Add Local User option, you must create the Create User option choice with the following blueprint configuration details:

  • A  BLPackage having the local properties defined in it for user provisioning (For example: Linux Add User or Windows Add User BLPackage)  as Software Packages.
  • A parameter for user name (UNIX_USER or WINDOWS_USER) as Deployment Model Parameter.
  • A parameter for user password (UNIX_USER_PASSWORD or WINDOWS_USER_PASSWORD) as Deployment Model Parameter.

See Creating-a-BLPackage-for-adding-local-users-in-the-Azure-Provider for details.

The following figure illustrates the blueprint configuration details to be defined for the Create User option choice:

UsrProv-SrvCatOpt.png

To create the option choice for the Add Local User option:

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

    UsrProv-SrvCatOptCnfg.png
    Note: For more information, see Option-Choices-available-when-extending-service-blueprints.
  2. Specify the following details for configuring an option choice for the Add Local User option, as shown in the following figure:

    UsrProv-SrvCatOptChc.png

Back to top

Where to go from here

Creating-service-offerings-for-the-Azure-provider

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*