The IBM Cloud Manager with Openstack 4.1.0.5 cmwo 4.1.0.5 interim fix 4 Readme

• Update cookbook versions (4.1.0.3)
• New openstack-compute attributes (4.1.0.3)
• Create new openstack-powervc-driver password data bag item (4.1.0.1)
• Configure self-service portal fix information (no longer required)
• Update the deployed topology

Fix pack 3 and later includes a tool that can be used to automatically perform certain environment updates:

• Update cookbook version constraints
• Move attributes - notably options in attributes like misc_nova - when a cookbook change requires different override attributes in the chef environment.

To update an environment named 'my-environment' stored in the chef server use this command:
  knife os manage update environment my-environment

To update a JSON environment file named 'my-environment.json' use this command:
  knife os manage update environment my-environment.json

The file name must end with the '.json' extension. If the file refers to an existing chef environment, the file will also be uploaded to the chef server.

If the fix pack requires other environment changes, you can edit the environment(s) used for your topologies using the following procedure.

Installing the fix pack updates the example environments:
  example-ibm-os-allinone
  example-ibm-os-single-controller-n-compute
  example-ibm-sce

If you have created an environment for your topology, or have created an environment file, these must be updated manually. If you do not do this, future deploys or updates will continue to use the original cookbook.

1. Change to the directory where you have created your topology files.

2. If you do not have your environment file, you can download the current environment from the chef server:
  # knife environment list
  _default
  example-ibm-os-allinone
  example-ibm-os-single-controller-n-compute
  example-ibm-sce
  test-environment

Identify the environment to change, e.g. test-environment and download it:
  # knife environment show test-environment -d -F json > test-environment.json

3. Edit the environment file and modify it as required.

4. Save the file.

5. Upload the modified environment to the chef server:
  # knife environment from file test-environment.json
  Updated Environment test-environment

This fix pack contains cookbook updates which require updates to the chef environment(s) for your topologies.

If any of the following conditions are true, no action is required to update cookbook versions, and you should continue with the next section of this README file.

• You have not created an environment
• You created your environment after installing fix pack 4.1.0.5 or later.
• You updated the cookbook versions for your environment after installing fix pack 4.1.0.5 or later.

Use the 'knife os manage update environment' command as described in 'Automated environment updates' to update your environment or environment file.

This table lists the updated cookbook versions and the fix pack that includes them.

New attributes were added to the openstack-compute cookbook. Changes are required to your environment if it contains the following the configuration options in the openstack.compute.misc_nova attribute.

Use the 'knife os manage environment update' command as described in 'Automated environment updates' to update your environment or environment files.

Fix pack 4.1.0.1 adds an openstack-powervc-driver password to the service_passwords data bag. This password is required to deploy a topology that includes the OpenStack PowerVC driver.

If you did not create a custom service_passwords data bag prior to installing this fix pack, or you are not using PowerVC, no action is required to update the service_passwords data bag, and you should continue with the next section of this README file.

1. Change to the directory where you stored the files for the topology that you deployed. Change your-deployment-name to the name for your deployment.
2. Create a local directory to contain the new password. Change your_env_service_passwords to the name of the data bags for your environment. The openstack.secret.*_data_bag JSON attributes in your environment file contain the data bag names to use.
     # mkdir -p data_bags/your_env_service_passwords
     # cp /opt/ibm/cmwo/chef-repo/data_bags/service_passwords/* data_bags/your_env_service_passwords
     # chmod -R 600 data_bags/
3. Change the openstack-powervc-driver password in your environment data bag. This is done by changing the value for the data bag item's name. Using the your_env_service_passwords/openstack-powervc-driver.json data bag item, change the value at CHANGEME to the password.
     {
       "id": "openstack-powervc-driver",
       "openstack-powervc-driver": "CHANGEME"
     }
4. Upload the data bag items for the password changed in the previous step. Run the following command from the parent of the data_bags directory that you created. Change your-secret-key-name to the secret key for your topology. The secret_file JSON attribute in your topology file contains the secret file to use.
     # knife data bag from file your_env_service_passwords
     openstack-powervc-driver.json --secret-file your-secret-key-name
5. Remove the local data bag items since they are no longer needed.
     # rm -rf data_bags/

Starting with fix pack 3, the self-service portal is updated to the latest fix pack level automatically when you update your deployed topology or deploy a new topology. It is no longer necessary to update your environment to configure the self-service portal fix pack or JRE updates.

After making the changes described above, update your deployed topology to apply the fixes contained in this fix pack.

If you did not deploy a topology prior to installing this fix pack, no further action is required.

The IBM Cloud Manager with OpenStack Knowledge Center has more information on updating a deployed topology.