Building service blueprints for an 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:
Links to service blueprint documentation
The following table provides links to the applicable service blueprint documentation.
Topic | Description |
---|---|
Provides an overview of the service 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.
Service blueprint construct | Notes specific to Azure |
---|---|
Service blueprint parameters | |
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 |
|
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). |
Load balancers | When using Azure Resource Manager without templates and BMC Cloud Lifecycle Management 4.6.05 and later, be aware of the following behavior:
|
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:
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).
See "To add and define load balancer pools in a service blueprint" in Creating-copying-or-editing-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:
|
Network security groups (NSGs) | When using Azure Resource Manager without templates and BMC Cloud Lifecycle Management 4.6.05 and later, be aware that Azure Resource Manager supports TCP, UDP protocols, and all other protocols defined in the network path. These are considered custom protocols. By default, no security rules are applied to a VM's NIC that is provisioned on Azure Resource Manager. After an NSG is associated to the NIC, then a set of default rules is applied. If the VM contains any network path, explicitly define an RSCD port rule and a load balancer port rule. |
Shared NSGs | When using Azure Resource Manager without templates and BMC Cloud Lifecycle Management 4.6.05 and later, be aware that, by default, NSGs for a NIC are shared across service offering instances as long as no NIC-to-NIC network paths are defined. If an NSG for a NIC is shared and a new network path is added to that NIC, the NSG will be unshared by the creation of a new unshared NSG with all of the rules in the resource group where the NIC exists. Then, a new network path will be created in that unshared NSG. |
Where to go from here
Proceed to Populating-the-Service-Catalog-for-the-Azure-provider.