Customizing OpenStack attributes

You can change the OpenStack attributes in your environment file to control logging, quotas and uploading images.

1. Update the following attributes in your environment file. Most attributes are in the override_attributes section of your environment, while some of the logging attributes might be in the default_attributes section, depending on your topology
   • openstack.compute.config.quota_*, openstack.network.quota.*, and openstack.block-storage.quota_*: The environment file provides default quota settings for the IBM® Cloud Manager with OpenStack compute, network, and block storage components. Set the quotas as needed for your deployment. If your deployment is part of a multi-region cloud environment, quotas settings are unique to each region. For more information, see the OpenStack manage quotas documentation.
   • openstack.compute.config.force_config_drive: set to always to force injection to take place on a config drive. If this attribute is not set to always, you could instead use config drive by adding 'config-drive = true ' into a nova boot command or by setting the config_drive attribute in a Heat template file.
   • openstack.image.upload_image and openstack.image.upload_images: These attributes allow an image to be uploaded to OpenStack as part of your deployment. openstack.image.upload_image is a set of key-value pairs where the key is the image name and the value is the URL location of the image. openstack.image.upload_images is a list of keys from openstack.image.upload_image that you want to upload. For example:

     "openstack": {
       "image": {
         "upload_image": {
           "myimage": "https://myimagesource.com/myimage"
         },
         "upload_images": [
           "myimage"
         ]
       }
     }

   • openstack.identity.debug and openstack.identity.verbose: Set to true or false for the desired logging level for the OpenStack identity service.
   • openstack.image.debug and openstack.image.verbose: Set to true or false for the desired logging level for the OpenStack image service.
   • openstack.network.debug and openstack.network.verbose: Set to true or false for the desired logging level for the OpenStack network service.
   • openstack.compute.debug and openstack.compute.verbose: Set to true or false for the desired logging level for the OpenStack compute service.
   • openstack.block-storage.debug and openstack.block-storage.verbose: Set to true or false for the desired logging level for the OpenStack block storage service.
   • openstack.telemetry.debug and openstack.telemetry.verbose: Set to true or false for the desired logging level for the OpenStack telemetry service.
   • openstack.orchestration.debug and openstack.orchestration.verbose: Set to true or false for the desired logging level for the OpenStack orchestration service.

   Note: For more information about customizing the OpenStack values, see the following configuration options. To map the OpenStack configuration file options to the IBM Cloud Manager with OpenStack attributes, see Mapping attributes to services.

   • cinder.conf (block-storage attributes) configuration options
   • glance-api.conf (image.api attribute) configuration options
   • glance-registry.conf (image.registry attribute) configuration options
   • keystone.conf (identity attributes) configuration options
   • nova.conf (compute attributes) configuration options
   • neutron.conf (network attributes) configuration options
2. When complete, return to the relevant topology deployment or update process and complete the remaining steps.