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.

Managing the Azure service offerings

This topic describes how to create and manage Microsoft Azure service offerings that cloud users can request from the BMC Cloud Lifecycle Management – My Cloud Services Console.

A service offering describes a function or capability that a cloud administrator makes available to users in the cloud. Application stacks, single servers, and adding a new account to a Microsoft Exchange server are all examples of services. For more general information about services, see Services overview.

After you have mapped the tenants to the logical data centers or network containers, you then can define your service blueprint for the Azure Provider. Service blueprints define the software, hardware, and deployment options for a service in the Service Catalog. A service blueprint is required before you can create a service. For service blueprint overview information, see Service blueprints overview.

You can group requestable offerings into packages to which different tenants can be entitled. This grouping makes it easier for service providers to partition and manage services created specifically for particular tenants.

The following topics provide information and instructions for creating and managing a Microsoft Azure service offering using BMC Cloud Lifecycle Management:

TaskDescription
Build service blueprints for Azure service

Create service blueprints as per the guidelines that are specific to Azure Provider.

Notes:

Creating the service offering for Azure

Create an Azure service offering instance. For detailed steps, see:

Notes:

Request an Azure cloud service

A cloud administrator or an end user can request Azure cloud service offerings from the BMC Cloud Lifecycle Management – My Cloud Services Console, based on the services available to you in the service catalog.

Note: The storage account name created in Microsoft Azure contains the first five characters of the user account prefix used for provisioning a VM; for example, azure803462722a585f1 as shown in the figure below:

A cloud administrator or a tenant administrator can also request an Azure cloud service on behalf of another user of the same tenant. See Requesting cloud services on behalf of another user for details.

Notes:

  • A cloud administrator or a tenant administrator can request an Azure cloud service on behalf of another user of a different tenant, only if both the source and target user's tenant has applied the same tags on an onboarded Logical Data Center.
  • While requesting a cloud service, in the Quota details area, the available quota for the selected user is displayed (click here to see figure). If the available quota is less than the required quota, the service request fails. The end users are assigned quota by the BMC Cloud Lifecycle Management administrators or tenant administrators based on the tenant quota allocated for the Azure Provider accounts.

Where to go next

Managing Azure services and servers

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.

Comments