Manage Compute service ConfigMaps

You can customize the Compute service (nova) behavior by configuring the default nova-extra-config ConfigMap (CR). The nova-extra-config CR applies to all node sets and allows you to tailor the Compute service for specific features or workloads in your environment.

The nova-extra-config ConfigMap
Copy link

You can use the default nova-extra-configConfigMap CR to apply generic Compute service configuration to all node sets without creating a custom service.

The Compute service (nova) provides the nova-extra-configConfigMap CR, where you can add generic configuration that applies to all the node sets that use the default nova service. If you use this default ConfigMap to add generic configuration to be applied to all the node sets, then you do not need to create a custom service.

Example of a generic feature configuration:

apiVersion: v1
kind: ConfigMap
metadata:
  name: nova-extra-config
  namespace: openstack
data:
   <integer>-<service>-<feature>.conf: |
     [<section>]
     <config_option>=<value>

where:

<integer>
Specifies an integer that indicates when the configuration should be applied in the series of configuration files that are applied to etc/<service>/<service>.conf.d/ in the <service> container when the service is deployed. Numbers below 25 are reserved for the OpenStack services and Ansible configuration files.
<service>
Specifies the name of the service.
<feature>
Specifies a string that identifies the feature.
<section>
Specifies the section to which you want to add the configuration.
Warning

You can configure only whole node sets. Reconfiguring a subset of the nodes within a node set is not supported. If you need to reconfigure a subset of nodes within a node set, you must split the node set via scaling in the current node set, remove the scaled in nodes from the node set, and add them to a new node set.

If your deployment has more than one node set, changes to the nova-extra-configConfigMap might directly affect more than one node set, depending on how the node sets and the DataPlaneServices are configured.

Identify node sets affected by ConfigMap changes
Copy link

Before you modify the nova-extra-config ConfigMap in a multi-node-set deployment, verify which node sets will be affected by the change. This helps you avoid applying unintended configuration to node sets that should remain unchanged.

Procedure
Copy link

  1. Check the services list of the node set and find the name of the OpenStackDataPlaneService CR that points to the nova service.
  2. Verify that the value of the edpmServiceType field of the OpenStackDataPlaneService CR is set to nova.
  3. Check the dataSources list of the OpenStackDataPlaneService CR for a configMapRef named nova-extra-config.

    If the dataSources list contains a configMapRef named nova-extra-config, then this node set uses this ConfigMap and will be affected by the configuration changes in this ConfigMap.

  4. If some of the affected node sets should not be reconfigured, create a new OpenStackDataPlaneService CR that points to a separate ConfigMap for these node sets.