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.

Azure provider

Note

From BMC Cloud Lifecycle Management 4.6.07, Azure Classic (commonly known as Azure Service Manager) is no longer supported. BMC recommends you to use Azure Resource Manager (ARM). All the classic resources are available in Azure Resource Manager portal.

BMC Cloud Lifecycle Management 4.6.03 and earlier versions integrate with the Azure Service Management (ASM) Portal, commonly known as the Azure Classic Portal to deploy Azure cloud applications as a service. With Microsoft Azure virtual machines (VMs), enterprise customers can deploy their own customized Microsoft Windows Server or Linux images into a multizone, commercially backed Service Level Agreement (SLA) production environment in minutes or get started with a preconfigured image from the Microsoft image gallery. Finally, with Microsoft Azure and virtual network technology, the cloud is a seamless extension of your data center, taking full advantage of Microsoft System Center, Active Directory, and Visual Studio.

The topics in this section provide information and instructions for installing, setting up, preparing, and initiating an Azure service offering instance:

With an Azure Provider integration with BMC Cloud Lifecycle Management, you can perform the following actions:

  • Provision VMs:Onboard existing Azure VMs using the QuickStart utility or REST API.
    • Provision VMs from a public image gallery of prepopulated templates available from Microsoft Azure.
    • Provision VMs from custom-built virtual hard disk (VHD) images (private image).
    • Attach or detach and use data disks for storage (each disk can be up to 1 TB in size).
  • Perform remote actions:
    • Log in remotely via Remote Desktop Procedure (RDP), PowerShell, Secure Socket Shell (SSH), or terminal server, to customize VMs.
    • Allocate and view tenant and user quota usage.
    • Start, stop, or shutdown VMs.
    • Modify the CPU count or memory size of provisioned VMs.
    • Add a server to an existing service.
    • Request an Azure cloud service on behalf of another user.
    • Share and transfer ownership of an existing Azure cloud service.
    • Install software on provisioned VMs (both pre- and post-provisioning) using BMC Server Automation.
    • Add local OS users to a provisioned VM.
    • Add VM in an existing availability set or create a new one while provisioning.

  • Perform networking actions:
    • Onboard an Azure network with subnets.
    • Place VMs in specific networks or subnets.
    • Open or close VM endpoints by using network paths.
    • Add servers to load balancer pool.
    • Enable or disable external IP Address Management (IPAM) solution. 
  • Monitor server and tenant details of the Azure Provider by using the Value Dashboard. See Monitoring server and tenant usage for details.
  • Request and manage Azure services and servers using both legacy and new My Cloud Services Console.  

High-level tasks for setting up an Azure Provider

The cloud administrator is an IT professional who is responsible for the full life cycle of the cloud environment, including initial planning, deployment and configuration, continued administration, operation, and maintenance. As a cloud administrator, you can leverage Microsoft Azure in the IaaS provider capability for your development and testing teams. As a Microsoft Software Developer Network (MSDN) subscriber and an enterprise customer, you can have access to an image gallery that contains multiple versions of the Windows server operating system and additional server software, such as SQL Server, SharePoint Server, and BizTalk Server, enabling you to quickly develop and test components at discounted rates. You can use your own MSDN server software licenses and bits to create VMs tailored to your specific needs.

The following pages list the tasks of a cloud administrator, associated with the stages at which the tasks are required:

 

Where to go from here

Installing the Azure Classic Provider

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