Unsupported content

 

This version of the product has reached end of support. The documentation is available for your convenience. However, you must be logged in to access it. You will not be able to leave comments.

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

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:
Verifications for OpenStack Provider in HATasks
Validating BMC AR System Server properties

Ensure that the values of the following properties of the .xml files are set correctly according to your HA environment configurations:

  • BusinessServiceManagementInstalledConfiguration.xmlBMC_AR_PORT
  • BMCCloudLifeCycleManagementInstalledConfiguration.xml:
    • BMC_API_SERVER_OSGI_HOST
    • BMC_API_SERVER_OSGI_PORT
    • BMC_API_SERVER_OSGI_PROTOCOL

Note: You can find these .xml files in the installation directories of the BMC AR System Server and BMC Cloud Lifecycle Management application in your environment.

Setting up the Cloud Platform Manager services

Ensure that you have performed the following tasks to set up the Cloud Platform Manager services in an HA environment:

  1. The cluster services and all disks are available on the primary node of the Cloud Platform Manager.
  2. Disable the Generic Services of the Platform Manager.
  3. From the Services panel, set the BMC_CSM service type to Automatic.
Verifying BMC AR System Server
  • Ensure that the primary BMC AR System Server has the AR Admin Operation Permission.
  • Ensure that BMC AR System Server is running on a primary node.
Validating the RSCD servicesEnsure that the RSCD services are running on all the host VMs on which the BMC Cloud Lifecycle Management is installed.

  • 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:

StepHigh-level taskProcedure
1Perform 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.

2Run the upgrade
  1. Extract the setup.cmd or setup.sh file from CLM Zipkit - OpenStack at BMC Communities.
  2. 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).
3Perform 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.

4Verify the upgrade

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

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

  2. 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

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