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

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:

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
    • <Platform_Manager_installation_directory>/configuration/lib/errorresources-1.0.0.jar
  3. Stop the BMC_CSM service.
  4. Copy the following .jar files to the <Platform_Manager_installation_directory>/configuration/lib folder:
    • errorresources-1.0.0.jar 
    • openstack-1.0.jar
  5. Copy the Openstack.properties files 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-1.0.jar@start
  7. (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
  8. 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:
    SwchMode.png

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

Warning

Note

You must import the following .def files using the following steps to set the field permissions correctly after adding the forms in the application:

  • LDC_Search_ForAllProviders.def
  • Multiple_AccountIcon_AL.def
  • OST_ActiveLinkGuide.def
  • OST_ActiveLink.def
  • OST_Filters.def
  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.
    DatImp1.png
     The Import Mappings page is displayed.
    DatImp2.png
  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

Warning

Note

You must perform this procedure only when upgrading OpenStack 1.0).

  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:
    • On the Custom tab, check the value of the CloudClass field (as shown in the following figure):
      UpgMan1.png
    • 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):
      UpgMan2.png
  5. 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.

 

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

BMC Cloud Lifecycle Management 4.0