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.

Building service blueprints for Azure service

This topic provides the caveats and considerations you need to review when creating a service blueprint for Azure services. It also provides links to the applicable service blueprint documentation. This topic contains the following sections:


Roadmap for service blueprint documentation

The following table provides links to the applicable service blueprint documentation.

Topic

Description

Provides an overview of the service blueprint blueprint workspace.

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

Considerations for creating a service blueprint for Azure Provider

Create service blueprints as described in Building service blueprints. The following table identifies the items to consider when creating a service blueprint for the Azure Provider.

Note

The following constructs do not apply to Azure:

  • PaaS Resource
  • Load balancer pools

Service blueprint construct

Notes specific to Azure

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:

    CompRes.png

    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.

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

SbntBP.png

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.

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

Where to go from here

Proceed to Managing-the-Azure-service-offerings.

 

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