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
Ensure that you complete the following tasks before you manually install or upgrade the OpenStack Provider:
- Complete the tasks listed in Prerequisites-for-installing-or-upgrading-the-OpenStack-Provider.
Download and extract the following OpenStack Provider installer files and store them on your local computer:
Deploying OSGi files on the Cloud Platform Manager
- 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
- 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
- <Platform_Manager_installation_directory>/configuration/lib/errorresources-1.0.0.jar
- Stop the BMC_CSM service.
- Copy the following .jar files to the <Platform_Manager_installation_directory>/configuration/lib folder:
- errorresources-1.0.0.jar
- openstack-1.0.jar
- Copy the Openstack.properties files to <Platform_Manager_installation_directory>/configuration folder.
- Open the config.ini file and set the osgi.bundles parameter value as follows:
osgi.bundles=lib/openstack-1.0.jar@start - (Applies only to upgrading OpenStack 1.0) Delete the following folder contents and folder:
- <Platform_Manager_installation_directory>/cache folder contents
- <Platform_Manager_installation_directory>/configuration/org.eclipse.osgi folder
- Start the BMC_CSM 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
Ensure that you have completed 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
- Click File > Import.
- Select ObjectDefinitions and click Next.
The Import Objects window is displayed. - In the Import File field, browse to the .def file and select it.
- Click Next.
The selected object details are displayed in the Object Selection. - Click Finish.
The .def file is imported. 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
- Click Save.
To import other .def files
- Click File > Import.
- Select ObjectDefinitions and click Next.
The Import Objects window is displayed. - In the Import File field, browse to the .def file and select it.
- Click Open.
- Select the Replace Objects on the Destination Server box.
- Select the Delete Excess fields box.
- In Handle Conflicting Types, select Display Conflict Error.
- Click Finish to import the .def file.
- Repeat for each required .def file.
To import data files
- Log on to the BMC Remedy Import Tool.
- Select File > Preferences, and then select Generate New Id For All Records under Handle Duplicate Requests.
- Select File > New Mapping.

The Import Mappings page is displayed.
Enter the field values that apply to importing the .arx files. In the Target Server field, select the Target Server name from the list:
- Click Auto Map.
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
- Log on to BMC Remedy User Tool and connect to the cloud AR System server.
- Open the BMC.CORE:BMC_ConcreteCollection join form.
- Search for Existing OpenStack Logical Data Centers.
Two entries must be displayed. - Select one of the Logical Data Center entries and ensure that you have modified the following details:
- 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 Others (as shown in the following figure):

- On the Custom tab, check the value of the CloudClass field (as shown in the following figure):
- 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:
- Log on to the Mid Tier Configuration Tool at the following link:
http://<midTierHost>:<portNumber>/arsys/shared/config/config.jsp - In the left navigation pane, click Cache Settings.
- Click Flush Cache.
- Clear the browser cache.
Verifying the OpenStack installation
See to verify that the installation was completed successfully.