Building service blueprints for Azure service

Service blueprints overview

Provides an overview of the service blueprint blueprint workspace.

Creating-copying-or-editing-a-service-blueprint

Describes how to add several of the various types of service blueprint objects, and how to define network connections between those objects.

Service blueprint parameters

In this implementation of the Azure Provider, you cannot add new OS users after the VM has been provisioned. However, you can add users by using BMC Server Automation and you must add the following service blueprint definition parameter to enable addition of local users in a provisioned VM:

• UNIX_USER or WINDOWS_USER parameter
• UNIX_USER_PASSWORD or WINDOWS_USER_PASSWORD parameter

For instructions, see Creating a BLPackage for adding local users in the Azure Provider. 

Note: To enable addition of local users as a post-deployment action, you must define the Add local user option and configure the option choice details.

Application

When you enable software installation as part of an Azure service offering, you must create a BMC Server Automation Deploy Job or an application component template.

 In the Azure service blueprint, click Software Packages, and then select the appropriate software package, from a list of available BLPackages. For instructions, see Installing software as a part of an Azure service offering.

Server

1. Add or select a server in the blueprint and expand the Compute Resources detail panel.
2. Select the Cloud Platform as Azure, and ensure that the auto-onboarded Definitive Media Library (DML) entry is defined as an Installable Resource in the service blueprint, as shown in the figure below:
   
   
   
   Note: In Azure Provider, if you are using a custom image as an Installable Resource, the provisioned VMs are placed in the same storage account in Microsoft Azure that was used for creating the custom image.
3. Add the virtual machines to an availability set to manage the availability of an application that uses multiple virtual machines. See Manage the Availability of Virtual Machines for details.

• 
  
  • To specify availability set, add the AVAILABILITY_SET_NAME#<ServerGroupName for example: Msft2012> parameter to an individual server. If you want to use different availability sets for different servers, specify different values while requesting the service for placement in different Availability Sets on Microsoft Azure.

    • To add the parameter, select a server item and click Parameters in the edit pane:

      1. 
         
         1. In the Parameters table, click .
         2. For Name, add AVAILABILITY_SET_NAME#<ServerGroupName for example: Msft2012>.
            Note: In multi-tier service blueprint, you must specify the correct <ServerGroupName> only as the AVAILABILITY_SET_NAME parameter.
         3. Enter a Label, such as Azure Availability Set.
         4. Optionally, add a short Description.
         5. Ensure that the Data Type is set to String.
         6. Optionally, enter a Default Value for the parameter.
         7. Optionally, select the User Entry Enabled option. Leave the other options blank.
         8. Click OK to add the parameter.
         9. Click OK to save the definition details.

      The figure below provides an example of adding the parameter to a server group.
      
      
      

      Note: You can view the Availability Set details of the provisioned server in the server details in My Cloud Services console.

Networks

When you enable VM placement in single or multiple subnets for a Virtual Network, you must define single or multiple subnets for a Virtual Network in a service blueprint and tag them appropriately (as shown in the figure below).



For more information, see Tagging-recommendations-and-examples. To create or manage tag groups and tags from the Service Designer workspace, see Managing-blueprint-tags.

Load balancer pools

To create a load balancer pool as part of Azure service offering, ensure that you have provided the following values as shown in the figure and specified below:

• For Type, specify Define a new Load Balancer Pool.
• For Load Balancer Pool Name, specify <Name of load balancer pool in range of 3-15 characters>.
• For Load Balancer Pool Tags, specify <Tag name that is mapped to the Internet Network Type of the Logical Data Center>.
• For Client Port, specify <Port number that you want to open for the Azure VM>.
• For Transport Protocol, specify TCP or UDP.

To create a load balancer pool entry as part of Azure service offering, ensure that you have provided the following values as shown in the figure and specified below:

Note: The name of the load balancer pool created in Microsoft Azure is same as the Load Balancer Pool Name specified here (for example: LBP1).

• For NIC, specify 0.
• Click the Enabled check box.
• For Server Port, specify <Port number that you want to open for the server>.

See To add and define load balancer pools in a service blueprint.

IP Endpoints/VLAN

When you enable network path creation as part of an Azure service offering, you must add and define networks and connections in an Azure service blueprint. Follow the instructions for adding service blueprints, except specify the following values under Network Path Details:

• For Transport Protocol, specify TCP or UDP.
• For Destination Port, specify Single Port.
• For Network Traffic, specify Permit.
• For IP Endpoint/VLAN, specify VLAN (Addr/Mask).