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 Azure VMs

After you have provisioned a virtual machine (VM) by using the BMC Cloud Lifecycle Management, you can start, stop, shut down, add, or remove disks of a provisioned VM. The following topic details the procedures to follow to manage provisioned Azure VMs. You can also install software, add local OS users, and create or delete network paths on a provisioned VM.

For information about starting, stopping, and shutting down an Azure VM:

Note

If you are using the new My Cloud Services console introduced in BMC Cloud Lifecycle Management version 4.5, the following operations are not supported: remove disk, manage network paths or endpoints, and manage load balancers TRO. To perform these operations, use the legacy My Cloud Services Console.

Considerations for an upgraded Azure SOI

After upgrading from Azure Provider 1.0.00 to 4.5.00 and later or 1.1.00 (only the upgraded SOIs from 1.0.00) to 4.5.00 and later, consider the following information while performing the Day 2 operations on an upgraded SOI:

  • An upgraded SOI is not covered under Quota calculations because Quota management is not supported for the servers provisioned by Azure Provider 1.0.00.

    Note

    You might experience incorrect quota calculations for servers provisioned in an upgraded environment. The cloud administrator must ensure that the quota allocation is done properly.

  • If you transfer an upgraded SOI to another user, and the user performs the add or remove disk operation, the operations are performed on the original storage account in Microsoft Azure.
  • If you or any other user perform an Add server operation on an upgraded SOI, the new VM disk is created or placed on a different storage account in Microsoft Azure instead of the storage account used for the original SOI servers.

Back to top

Managing system disks of an Azure VM

You can perform the following tasks to manage the system disks for a server in an Azure service offering:


Adding disks to an Azure VM

Note

  • To enable adding new disks to an Azure VM, BMC Cloud Lifecycle Management, cloud administrators must first create Add disk options and option choices for the Azure Provider. See Populating-the-Service-Catalog-for-the-Azure-provider for details. 
  • Azure provider supports addition of empty data disk only.

You can add a disk to the provisioned VM by using the legacy My Cloud Services Console or the new My Cloud Services Console. After you have added the disk, you must access the VM and add a new disk volume to reflect the additional disk in the VM.

Click here for the new My Cloud Services Console.
  1. Log on to My Cloud Services portal by using your end-user credentials.
  1. On the left side of the window, in RESOURCE TYPE, click Servers.
    A list of available servers is displayed, as shown in the following figure:

    MyRe1.png
  1. Click the server name to view the server's HARDWARE configuration and to add a disk, as shown in the figure below:
    AddDsk01.png
  2. In the HARDWARE pane, click Add Disk.
  3. In the Add Disk dialog box, select an available disk size from Optional Disks, as displayed in the figure below:
    AddDsk02.png
  1. Click OK.
  2. Click Submit Changes.
  3. In the Submit Changes dialog box, as shown in the following figure, click Yes to confirm the addition of a disk of selected size to your server:
    AddDsk04.png

The disk is now added for the server.

Click here for the legacy My Cloud Services Console.
  1. Log on to BMC Remedy Action Request System (AR System) by using your end-user credentials.
  2. On the left side of the window, click the vertical Applications menu, and select Cloud Lifecycle Management > My Cloud Services Console.
  3. On the My Services tab of My Cloud Services workspace, click the Servers link. 
  4. From the list of servers, select the server for which you want to add a new disk. 
    The following figure shows the list of servers.
    AddDskold01.png
  5. Click Modify Actions ModifyCPU.gif and select a postdeployment modify action (for example, Add disk) from the list.
    The options available for adding a new disk for an Azure VM are displayed, as shown in the following figure:
    AddDskold02.png
  6. In the Submit Request dialog box, select your option and click Next. 
  7. Review your request details, as shown in the following figure, and click Submit.
    AddDskold03.png

Back to top

Adding a new disk volume to a provisioned VM using Microsoft Azure

After you have added a disk (Disk1) to the provisioned VM using BMC Cloud Lifecycle Management, the new disk volume (Disk 2) remains unallocated. You must perform the following steps to add a new disk volume (Disk 2) to a provisioned VM.

Note

The steps detailed in the following procedure are specific to the VMs provisioned with Windows Server 2008 R2 Datacenter. For any other OS, steps 3 through 7 might differ. For details, see How to attach a data disk to a virtual machine.

  1. Connect to the provisioned VM by using the Azure Management Portal.
  2. Launch Server Manager.
  1. Click Storage.
    The existing disk details of the VM are displayed along with the new disk (Disk 2 - Unallocated), as shown in the following figure:
    VMAdDsk1.png
  1. Right-click the new disk (Disk 2) and select New Simple Volume.
    VMAdDsk2.png
  1. In the New Simple Volume Wizard, click Next and then enter the details for the new disk volume.
    After you have entered the required details, the Completing the New Simple Volume Wizard is displayed, as shown in the following figure:
    VMAdDsk4.png
  2. Click Finish.
    A new disk volume (New Volume F) is added as Disk 2, as shown in the following figure:
    VMAdDsk5.png

Viewing disks of an Azure VM

To view the existing disk details of an Azure VM using the legacy My Cloud Services Console, see To view the system disks for a server in the legacy console.

To view the existing disk details of an Azure VM using the new My Cloud Services Console, navigate to the My Resources > Server configuration and see the details in the HARDWARE pane.

Removing disks of an Azure VM

To remove the system disks of an Azure VM, see To remove a system disk from a server in the legacy console.

Notes

  • To remove a disk from a VM, you must first stop the VM.
  • You can remove only the added disks from a VM. You cannot remove the original OS disk that was assigned when the VM was provisioned.
  • You cannot remove the system disks by using the new My Cloud Services Console.

Back to top

Modifying CPU and memory of an Azure VM

You can modify CPU count and memory size for a server using the legacy My Cloud Services Console or the new My Cloud Services Console:

Note

To enable modification of CPU count and memory size of an Azure VM, BMC Cloud Lifecycle Management cloud administrators must first create Azure Instance, Memory, and CPU options and option choices for the Azure Provider. See Populating-the-Service-Catalog-for-the-Azure-provider for details.

Click here for the new My Cloud Services Console.
  1. Log on to My Cloud Services portal by using your end-user credentials.
  1. On the left side of the window, in RESOURCE TYPE, click Servers.
    The list of available servers is displayed, as shown in the following figure:

    MyRes.png
  2. Click the server name to view the server configuration to update the CPU and RAM details, as shown in the following figure:
    MyRes2.png
  3. On the left side of the window, in ADVANCED CONFIGURATION, click Update CPU and RAM.
  4. Select an available postdeployment Update CPU and RAM option from the displayed options, as shown in the following figure:
    UpdCPU1.png
  1. Click Submit Changes.
  2. In the Submit Changes dialog box, as shown in the following figure, click Yes to confirm the selected modifications of CPU or RAM to your server:
    UpdCPU3.png

The CPU or RAM details for the server are updated.

Click here for the legacy My Cloud Services Console.
  1. Log on to BMC Remedy Action Request System (AR System) by using your end-user credentials.
  2. On the left side of the window, click the vertical Applications menu, and select Cloud Lifecycle Management > My Cloud Services Console.
  3. On the My Services tab of My Cloud Services workspace, click the Servers link. 
  4. From the list of servers, select the server for which you want to modify the memory and CPU option choices. 
    The following figure shows the list of servers.
    ModCPU1.png
  5. Click Modify Actions ModifyCPU.gif and select an available post-deployment modify action (for example, Update CPU and RAM) from the list.
    The options available for modifying the CPU count and memory size of an Azure VM are displayed, as shown in the following figure:
    ModCPU2.png
  6. In the Submit Request dialog box, select your option and click Next. 
  7. Review your request details, as shown in the following figure, and click Submit.
    ModCPU3.png

Installing software on an Azure VM

You can install software on a server using the legacy My Cloud Services Console or the new My Cloud Services Console:

Note

BMC Cloud Lifecycle Management cloud administrators must first create installation software options and option choices for the Azure Provider. See Populating-the-Service-Catalog-for-the-Azure-provider for details.

Click here for the new My Cloud Services Console.
  1. Log on to My Cloud Services portal by using your end-user credentials.
  1. On the left side of the window, in RESOURCE TYPE, click Servers. 
    The list of     available servers is displayed, as shown in the following figure:

    MyRes1.png
  1. Click the server name to view the server configuration, as shown in the following figure:
    InstlSw1.png
  2. In the SOFTWARE pane, select the software to be installed, as shown in the following figure:
    InstlSw2.png
  3. Click Submit Changes.
  4. In the Submit Changes dialog box, as shown in the following figure, click Yes to confirm the installation of the selected software on your server:
    InstlSw3.png
    The software is deployed on the server.
Click here for the legacy My Cloud Services Console.
  1. Log on to BMC Remedy Action Request System (AR System) by using your end-user credentials.
  2. On the left side of the window, click the vertical Applications menu, and select Cloud Lifecycle Management > My Cloud Services Console.
  3. On the My Services tab of the My Cloud Services workspace, click the Servers link.
  4. From the list of servers, as shown in the following figure, select the server on which you want to install the software, and click Modify Actions ModifyCPU.gif.

    InstlSwLgc1.png
  5. From the menu, select an available post-deployment modify action.
  6. In the Submit Request dialog box, as shown in the following figure, select your options and click Next.

    InstlSwLgc2.png
  7. Review your request details, as shown in the following figure.

    InstlSw3.png
  8. Click Submit. 
    The software is deployed on the VM, as shown in the following figure:

    InstlSw4.png

Note

A post-deployment software installation from BMC Cloud Lifecycle Management might fail due to a change in the IP address of the provisioned VM under the following conditions:

  • The VM is restarted or shut down from the Azure Management Portal. 
  • Port 4750 is opened for a network path of a VM provisioned using a multi-tier blueprint.

See Azure Provider Limitations for details.

Back to top

Adding local OS users on an Azure VM

You can add local OS users on an Azure VM using the legacy My Cloud Services Console or the new My Cloud Services Console:

Note

To enable post-deployment user provisioning, BMC Cloud Lifecycle Management cloud administrators must first create a BLPackage with local properties and also define the Add local user option and option choice for the Azure Provider. See Populating-the-Service-Catalog-for-the-Azure-provider for details.

Click here for the new My Cloud Services Console.
  1. Log on to My Cloud Services portal by using your end-user credentials.
  1. On the left side of the window, in RESOURCE TYPE, click Servers. 
    The list of     available servers is displayed, as shown in the following figure:

    MyRes1.png
  1. Click the server name to view the server configuration.
  2. In the SOFTWARE pane, select Create User option.
  3. Enter the user name and password details.
  4. Click OK.
  5. Click Submit Changes.
  6. In the Submit Changes dialog box, click Yes to confirm the addition of user for the server.
Click here for the legacy My Cloud Services Console.
  1. Log on to BMC Remedy Action Request System (AR System) by using your end-user credentials.
  2. On the left side of the window, click the vertical Applications menu, and select Cloud Lifecycle Management > My Cloud Services Console.
  3. On the My Services tab of the My Cloud Services workspace, click the Servers link.
  4. From the displayed list of servers, as shown in the following figure, select the server on which you want to add a local user, and click Modify Actions ModifyCPU.gif.
    AdLclUsr1.png
  5. From the menu, select an available post-deployment modify action.

    AdLclUsr2.png
  6. In the Submit Request dialog box, as shown in the following figure, enter the user name and password details and click Next.

    AdLclUsr3.png
  7. Review your request details, and click Submit.

AdLclUsr4.png

A local user is added on the provisioned VM with the user name and password that you specified.

Managing network paths or endpoints of an Azure VM

You can perform the following operations to manage the network paths of an Azure VM. For more information about network paths, see Background information on network paths.

Note

For a multi-tier service offering that supports both network path and software installation operations, do not enable the network path in the 4750 port to avoid software installation failure. See Azure Provider Limitations for details.

  • Creating an inbound network path for a network instance

    Note

    BMC Cloud Lifecycle Management Administrators can also create network paths by defining the network paths or endpoints in the Azure Service Blueprint or defining the outbound network path for a network instance. See Managing-network-paths-administrator for details about defining the outbound network path from the Resources > Network Container panel.

    Click here for steps to create a network path for an Azure VM.
    1. Log on to BMC Remedy Action Request System (AR System) by using your end-user credentials.
    2. On the left side of the window, click the vertical Applications menu, and select Cloud Lifecycle Management > My Cloud Services Console.
    3. On the My Services tab of the My Cloud Services workspace, click the Servers link.
    4. From the list of servers, as shown in the following figure, select the server for which you want to create a network path, and click Manage Network Paths.

      MngNetPath1.png
    5. In the Manage Network Paths window, as shown in the following figure, specify the Network Interface as NIC0 to display the existing network path details of the VM.

      MngNetPath2.png
    6. Click Create Network Path Addicn.png.

      MngNetPath3.png

    7. In the Create Network Path window, for Direction, select Create Inbound Network Path.

      Note

      Select Create Outbound Network Path for the Direction only if you are creating the network path from the server network interface.

      MngNetPath4.png

    8. Click Next and specify Network Endpoint for Type and Internet for Name.
      For an Azure Instance, you can create a network path only from the Internet.

      MngNetPath6.png

      Note

      Select the Source Endpoint Type as Server Network Interface only if you are creating the network path from a server network interface.

      MngNetPath5.png

      Search for the Server Offering Instance and select the Server on which you want to create the network path.


    9. Click Next.
      The following figure shows the details of the Destination Endpoint.

      MngNetPath7.png

    10. Click Next and specify the network path constraints, as shown in the figure below:

      MngNetPath8.png

      Note

      Only the TCP and UDP Transport Protocol are supported for Microsoft Azure.


    11. Click Save.
      The network path is created for the selected server.
  • Deleting a network path

Back to top

Managing load balancers for an Azure VM

As a cloud administrator or end user, you can manage the load balancer pools by server in the following ways:

See Managing-load-balancers-for-the-Azure-Provider for considerations for configuring load balancers for the Azure Provider.

Viewing Availability Set of an Azure VM

Note

To add a VM to an Availability Set, BMC Cloud Lifecycle Management administrators must first define the Availability Set parameter for a server in the service blueprint. See Considerations for creating a service blueprint for Azure Provider for details.

As a cloud administrator or end user, you can view the Availability Set details of the provisioned VM in the server details, as shown in the figure below:

AvailSet.png

 

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