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.

Upgrading the Azure Provider

The following sections describes the process for upgrading to the latest version of Azure Provider by using the Azure Provider installer.

Note

 To troubleshoot an Azure Provider upgrade issue, see Azure-Provider-issues.

Before you begin

Ensure that the following prerequisites have been met before you perform the Azure Provider upgrade procedure:

  • You have downloaded the Azure Provider installer file (Azure Windows Installer 1.1.00.zip or Azure Linux Installer 1.1.00.tar) from Azure 1.1.00 Windows or Linux Installer for CLM 4.1.00.zip or CLM Zipkit - Azure Provider at BMC Communities and extracted the file contents and stored it on your local computer.
  • The following BMC Cloud Lifecycle Management stack components are running when you install the Azure Provider:
    • Cloud Platform Manager
    • BMC Remedy Action Request System Server (BMC AR System Server)
  • You have the same OS (Microsoft Windows or Linux) in the computer from where the installer is being run and the computer where BMC Cloud Lifecycle Management stack components are installed.
  • You have the following privileges on the computer on which you want to run the installer and on which the BMC Cloud Lifecycle Management stack components are installed:
    • (Microsoft Windows) Administrator
    • (Linux) root
  • BMC Server Automation Network Shell (NSH) is installed and the RSCD agent is running on the computer on which you want to run the installer and on which the BMC Cloud Lifecycle Management stack components are installed.
  • Ensure that you have Java 1.7.x 64 bit installed and have set the environment variables (JAVA_HOME and jre PATH).

  • If you are installing the Azure Provider in a high-availability (HA) environment, you must check and set up the following properties of the BMC AR System Server, Cloud Platform Manager, and host VMs according to your HA environment configurations:

  • Ensure that prior to upgrading to Azure Provider 1.0.00 to 1.1.00, the osgi.bundles parameter values (lib/azure-1.0.0.jar@start and lib/azureconnect-1.0.0.jar@start) exists for the Azure Provider in the <Platform_Manager_installation_directory>/configuration/config.ini file.
  • If you have a previous version of BMC Cloud Lifecycle Management, you have successfully upgraded to 4.1.00. For more information, see Upgrading.

To upgrade Azure Provider

The following table lists the steps to upgrade the Azure Provider to the latest version:

Task sequence

High-level task

Procedure

1

Perform the prerequisites for the upgrade

Complete the required prerequisite steps before you start the Azure upgrade process. For example, back up your database and take snapshots of product virtual machines.

2

Run the upgrade

  1. Extract the setup.cmd or setup.sh file from CLM Zipkit - Azure Provider at BMC Communities.
  2. Run the installer to upgrade the Azure Provider.
    Note: During upgrade, you must specify your enterprise AR System server or cloud AR System server details (as applicable for your environment).

3

Perform postupgrade configuration

  1. Stop the Cloud Platform Manager service.
  2. On the Cloud Platform Manager computer, delete the BMC Software\BMCCloudLifeCycleManagement\ Platform_Manager\configuration\org.osgi.eclipse folder.
  3. Start the Cloud Platform Manager service.
  4. Log on at http://<hosts>:8080/arsys/shared/config/config.jsp and flush the BMC Remedy Mid Tier cache.

4

Verify the upgrade

Log on to the BMC Remedy Mid Tier and verify that the following Azure resources are displayed correctly:

  1. Verify that the Azure Provider is registered, as shown in the following figure:

    AzProv.png

  2. Verify that multiple accounts for the Azure Provider were created, as shown in the following figure:
    MulAc.png

Note:

If you are upgrading a non-registered Azure Provider, then ensure the following after upgrade:

  • The azure-1.0.0.jar and azureconnect-1.0.0.jar files exists with the new time stamp (current date when the upgrade is done) in the Platform_Manager/lib folder.
  • The osgi.bundles parameter value exists for the Azure Provider in the <Platform_Manager_installation_directory>/configuration/config.ini file.


Postupgrade caveats for an upgraded SOI

After upgrading from Azure Provider 1.0.00 to 1.1.00, consider the following caveats while performing the Day 2 operations on an upgraded SOI:

  • An upgraded SOI is not covered under Quota calculations, as Quota management is supported only for the servers provisioned by Azure Provider 1.1.00.
    Note:You may expect incorrect quota calculations for servers provisioned in an upgraded environment. 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, then the operations are performed on the original storage account in Microsoft Azure.
  • If you or any other user perform Add server operation on an upgraded SOI, then 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.

Where to go from here

Configuring-the-Azure-Provider

 

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