Manually installing or upgrading the OpenStack Provider

The following topics describe the steps to follow to manually install or upgrade the OpenStack Provider:

• • Before you begin
  • Deploying OSGi files on the Cloud Platform Manager
  • Deploying .def and .arx files on the BMC AR System server
  • Updating existing Logical Data Centers on the cloud AR System server
  • Clearing the Mid Tier and browser caches
  • Verifying the OpenStack installation

Before you begin

Ensure that you complete the following tasks before you manually install or upgrade the OpenStack Provider:

• Complete the tasks listed in Prerequisites-for-installing-the-OpenStack-Provider.
• If you have failed to install the OpenStack Provider correctly using the installer, BMC recommends you to cleanup your incomplete OpenStack Provider installation prior to installing it manually.

• You can choose either of the upgrade paths:

  • OpenStack Provider 1.0.00 on both one AR System server and two AR System servers to OpenStack Provider 2.0.00 on BMC Cloud Lifecycle Management 4.1.00
  • OpenStack Provider 1.0.00 on both one AR System server and two AR System servers to OpenStack Provider 4.1.1 on BMC Cloud Lifecycle Management 4.1.00
  • OpenStack Provider 2.0.00 on BMC Cloud Lifecycle Management 4.1.00 to OpenStack Provider 4.1.1 on BMC Cloud Lifecycle Management 4.1.00

  To perform the upgrade you must download and extract the following OpenStack Provider installer files and store them on your local computer:

Deploying OSGi files on the Cloud Platform Manager

1. On the Platform Manager host, navigate to the <Platform_Manager_installation_directory> folder:
   
   • (Windows) C:\Program Files\BMC Software\BMCCloudLifeCycleManagement\Platform_Manager
   • (Linux) /gfs/bmc/BMCCloudLifeCycleManagement/Platform_Manager
2. Make a backup copy of the following files in the <Platform_Manager_installation_directory> folder:
   
   • <Platform_Manager_installation_directory>/configuration/config.ini
   • <Platform_Manager_installation_directory>/configuration/providers.json
   • <Platform_Manager_installation_directory>/configuration/cloudservices.json
   • <Platform_Manager_installation_directory>/configuration/import_node_list.json.imported
3. Stop the Platform Manager service.
4. Copy the openstack-2.0.jar and (Applies for OpenStack Provider 4.1.1) util-1.0.0.jar file to the <Platform_Manager_installation_directory>/lib folder.
5. Copy the Openstack.properties file to <Platform_Manager_installation_directory>/configuration folder.

6. Open the config.ini file and set the osgi.bundles parameter value as follows:

   osgi.bundles=lib/openstack-2.0.jar@start

   Note

   If you are upgrading, and the osgi.bundles parameter value exists as

   lib/openstack-1.0.jar@start

   you must remove it and set the osgi.bundles parameter value as

   lib/openstack-2.0.jar@start 

7. (Applies only to upgrading OpenStack) Delete the following folder contents, folder, and file:
   • <Platform_Manager_installation_directory>/cache folder contents
   • <Platform_Manager_installation_directory>/configuration/org.eclipse.osgi folder
   • <Platform_Manager_installation_directory>/configuration/lib/openstack-1.0.jar file

8. Start the Platform Manager service and monitor the .csm log files at the following location:

   <Platform_Manager_installation_directory>\Logs

Deploying .def and .arx files on the BMC AR System server

You must import the .def and .arx files and configure the forms on the BMC AR System server computer by using the procedures in the following sections.

Before you begin

Complete the following tasks before you deploy the files:

• Log on to the BMC Remedy Developer Studio as Administrator.
• Switch the mode to Base Development, as shown in the following figure:
  

To import the openstack_newforms.def file and configure the BMC Remedy AR forms

1. Click File > Import.
2. Select ObjectDefinitions and click Next.
   The Import Objects window is displayed.
3. In the Import File field, browse to the .def file and select it.
4. Click Next.
   The selected object details are displayed in the Object Selection.
5. Click Finish.
   The .def file is imported.

6. Navigate to Application's list and add the forms in the following applications.

   Application name	Form name
   BMC Cloud Management Foundation	CMF:OpenStack_UserCredentials
   BMC Cloud Management Foundation	CMF:ProviderOpenstack_v
   BMC Cloud Management Administrator	CMA:MultipleOpenStackAccount

7. Click Save.

To import other .def files

1. Click File > Import.
2. Select ObjectDefinitions and click Next.
   The Import Objects window is displayed.
3. In the Import File field, browse to the .def file and select it.
4. Click Open.
5. Select the Replace Objects on the Destination Server box.
6. Select the Delete Excess fields box.
7. In Handle Conflicting Types, select Display Conflict Error.
8. Click Finish to import the .def file.
9. Repeat for each required .def file.

To import data files

1. Log on to the BMC Remedy Import Tool.
2. Select File > Preferences, and then select Generate New Id For All Records under Handle Duplicate Requests.
3. Select File > New Mapping.
   
    The Import Mappings page is displayed.
   

4. Enter the field values that apply to importing the .arx files. In the Target Server field, select the Target Server name from the list.
5. Click Auto Map.

6. Click Import > Start Import.
   An entry is created in the following forms when the respective data file is imported.

   Form name	Details of entry created
   AR System Online Help Mapping	Openstack Help instance
   SRS:CFGAdvancedInterface	-
   CMF:CloudAIFConfig	-
   CMF:ProviderVendorFormMapping	Provider = “OpenStack”

Updating existing Logical Data Centers on the cloud AR System server

1. Log on to BMC Remedy User Tool and connect to the cloud AR System server.
2. Open the BMC.CORE:BMC_ConcreteCollection join form.
3. Search for Existing OpenStack Logical Data Centers.
   Two entries must be displayed.

4. Select one of the Logical Data Center entries and ensure that you have modified the following details:

   Click Save.

   • On the Custom tab, check the value of the CloudClass field (as shown in the following figure):
     
   • If the value of CloudClass field is logicaldatacenter, click the Custom 2 tab and set the value of HostingEnvironmentType to Other (as shown in the following figure):
     
5. Go to the BMC.CORE:BMC_ConcreteCollection form and search the Logical Data Center entry with CloudClass as logicaldatacenter, as shown in the figure below:
   
   1. Click View Relationships and search the relationship with name NETWORKSERVESLDC, as shown in the following figure:
      
   2. Click View Relationship to display the details, as shown in the following figure:
      

1. 1. Rename the relationship name NETWORKSERVESLDC as NETWORKINLOGICALDATACENTER.
   2. Click the Custom 2 tab and set the value of Source.CloudClass value to logicaldatacenternetwork instead of network.
   3. Click Save.
   4. Repeat step a - e for every relationship with the name NETWORKSERVESLDC.
2. Open the BMC.CORE:BMC_ConnectivityCollection form.
   1. Search an existing OpenStack network.
   2. In the Custom 2 tab, change the CloudClass value tologicaldatacenternetwork instead of network, as shown in the following figure:
      

1. 1. In the Custom 4 tab, change the value of isCustomNetwork to True if it is false.
   2. Click Save.
   3. Click View Relationships and search the relationship with name REALIZEDBY, as shown in the following figure:
      

1. 1. Click View Relationship to display the details, as shown in the following figure:
      
   2. In Custom 2 tab, change the Source.CloudClass value to logicaldatacenternetwork from network.
   3. Click Save.
   4. Search for the relationship name PROVIDERPROVIDESINSTANCE, as shown in the figure below:
      

1. 1. Click View Relationship to display the details, as shown in the following figure:
      
   2. In Custom tab, change the Destination.CloudClass value to logicaldatacenternetwork from network.
   3. Click Save.
   4. Repeat step a - l for all the existing OpenStack networks.
2. Click Save.

Clearing the Mid Tier and browser caches

Perform the steps listed below to clear the BMC Remedy Mid Tier and the web browser cache:

1. Log on to the Mid Tier Configuration Tool at the following link:
   http://<midTierHost>:<portNumber>/arsys/shared/config/config.jsp
   
2. In the left navigation pane, click Cache Settings.
3. Click Flush Cache.
4. Clear the browser cache.

Verifying the OpenStack installation

See to verify that the installation was completed successfully.