Upgrading custom providers

When you installed BMC Cloud Lifecycle Management, you might have customized one or several providers in the solution to suit your business needs. This section covers information about how to port those customizations to version 4.x when you perform the upgrade.

• • Upgrading the OpenStack Provider
  • Before you begin
  • To upgrade the OpenStack Provider
  • Where to go from here
  • Related topic
  • Upgrading the Azure Provider
  • Before you begin the upgrade
  • To upgrade the Azure Provider
  • Postupgrade caveats for an upgraded SOI

Upgrading the OpenStack Provider

The following sections describe the process for upgrading to the latest version of OpenStack Provider by using the OpenStack Provider:

• • Before you begin
  • To upgrade the OpenStack Provider
  • Where to go from here
  • Related topic

Before you begin

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

• Successfully upgrade BMC Cloud Lifecycle Management to 4.5.00 or later and ensure that you use the compatible version of the OpenStack provider. For more information, see Upgrading.

• (4.5.00 and earlier) You have downloaded the OpenStack Provider version 4.5.00 or later installer file (setup.cmd or setup.sh) from CLM Zipkit - OpenStack at BMC Communities and stored it on your local computer.
• (4.6.00) To use BMC Cloud Lifecycle Management 4.6.00 with the OpenStack provider, install 4.6.03. DO NOT install the OpenStack provider separately.
• The following BMC Cloud Lifecycle Management stack components are running when you install or upgrade the OpenStack Provider:
  
  • Cloud Platform Manager
  • BMC Action Request System Server (BMC AR System Server)
• You have the same OS (Microsoft Windows or Linux) on the computer from which the installer is being run and on the computer on which 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.
• NSH is installed and the RSCD agent is running on the computer 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 or upgrading the OpenStack Provider in a high-availability (HA) environment, you must verify the following properties of the BMC AR System Server, Cloud Platform Manager, and host VMs according to your HA environment configurations:

• Ensure that in the <Platform_Manager_installation_directory>/configuration/config.ini
  file, the osgi.bundles parameter value (lib/openstack-1.0.jar@start) exists for the OpenStack Provider.

To upgrade the OpenStack Provider

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

Step	High-level task	Procedure
1	Perform the prerequisite steps	Complete the required prerequisite steps before you start the OpenStack upgrade process. For example, back up your database and take snapshots of product virtual machines.
2	Run the upgrade	Extract the setup.cmd or setup.sh file from CLM Zipkit - OpenStack at BMC Communities. Run the installer to upgrade the OpenStack Provider. Note: During upgrade, you must specify your enterprise AR System server or cloud AR System server details (for your environment).
3	Perform postupgrade configuration	Stop the Cloud Platform Manager service. On the Cloud Platform Manager computer, delete the BMC Software\BMCCloudLifeCycleManagement\Platform_Manager\configuration\org.osgi.eclipse folder. Start the Cloud Platform Manager service. 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 OpenStack resources are displayed correctly: Verify that the OpenStack Provider is registered, as shown in the following figure: Verify that multiple accounts for the OpenStack Provider were created, as shown in the following figure: Note:If you are upgrading an unregistered OpenStack Provider, verify the following items after the upgrade: In the Platform_Manager/lib folder, the openstack-2.0.jar file exists with the new time stamp (current date when the upgrade is done). The osgi.bundles parameter value exists for the OpenStack Provider in the <Platform_Manager_installation_directory>/configuration/config.ini file.  (OpenStack Provider 4.5.00 only) The Platform_Manager/lib folder contains the new util-1.0.0.jar file copied during the upgrade.

Where to go from here

Configuring-the-OpenStack-Provider

Related topic

OpenStack-Provider-issues

Upgrading the Azure Provider

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

• • Before you begin the upgrade
  • To upgrade the Azure Provider
  • Postupgrade caveats for an upgraded SOI

Before you begin the upgrade

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

• Met all of the installation requirements described in Prerequisites-for-installing-the-Azure-Provider.

• Successfully upgrade BMC Cloud Lifecycle Management to 4.5.00 or later and ensure that you use the compatible version of the Azure provider. For more information, see Upgrading.

• Ensure that prior to upgrading the Azure Provider, the osgi.bundles parameter values (lib/azure-1.0.0.jar@start and lib/azureconnect-1.0.0.jar@start) exist for the Azure Provider in the <Platform_Manager_installation_directory>/configuration/config.ini file.

To upgrade the Azure Provider

The following table lists the steps to upgrade the Azure Provider to the latest version:The [confluence_table-plus] macro is a standalone macro and it cannot be used inline. Click on this message for details.
This macro generates standalone content. As a consequence you need to make sure to use a syntax that separates your macro from the content before and after it so that it's on a line by itself. For example in XWiki Syntax 2.0+ this means having 2 newline characters (a.k.a line breaks) separating your macro from the content before and after it.

Postupgrade caveats for an upgraded SOI

After upgrading from Azure Provider 1.0.00 to BMC Cloud Lifecycle Management 4.5.00 (or later) or from Azure Provider 1.1.00 (only the upgraded SOIs from 1.0.00) to BMC Cloud Lifecycle Management 4.5.00 or later, consider the following caveats while performing 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.

  NoteYou might expect incorrect quota calculations for servers provisioned in an upgraded environment. The cloud administrator must ensure that the quota allocation is done correctly.
• If you transfer an upgraded SOI to another user, and the user performs the Add disk or Remove disk operation, the operations are performed on the original storage account in Microsoft Azure.
• If you or any other user performs the 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.