OpenStack Controller configuration

Available since MOSK 23.2

The OpenStack Controller enables you to modify its configuration at runtime without restarting. MOSK stores the controller configuration in the openstack-controller-config ConfigMap in the osh-system namespace of your cluster.

To retrieve the OpenStack Controller configuration ConfigMap, run:

kubectl get configmaps openstack-controller-config -o yaml

Example of an OpenStack Controller configuration ConfigMap

apiVersion: v1
data:
  extra_conf.ini: |
    [maintenance]
    respect_nova_az = false
kind: ConfigMap
metadata:
  annotations:
    openstackdeployments.lcm.mirantis.com/skip_update: "true"
  name: openstack-controller-config
  namespace: osh-system

OpenStack Controller extra configuration parameters

Section	Parameter	Default value	Description
[osctl]	wait_application_ready_timeout	1200	The number of seconds to wait for all application components to become ready.
	wait_application_ready_delay	10	The number of seconds before going to the sleep mode between attempts to verify if the application is ready.
	node_not_ready_flapping_timeout	120	The amount of time to wait for the flapping node.
[helmbundle]	manifest_enable_timeout	600	The number of seconds to wait until the values set in the manifest are propagated to the dependent objects.
	manifest_enable_delay	10	The number of seconds between attempts to verify if the values were applied.
	manifest_disable_timeout	600	The number of seconds to wait until the values are removed from the manifest and propagated to the child objects.
	manifest_disable_delay	10	The number of seconds between attempts to verify if the values were removed from the release.
	manifest_purge_timeout	600	The number of seconds to wait until the Kubernetes object is removed.
	manifest_purge_delay	10	The number of seconds between attempts to verify if the Kubernetes object is removed.
	manifest_apply_delay	10	The number of seconds to pause for the Helm bundle changes.
[maintenance]	instance_migrate_concurrency	1	The number of instances to migrate concurrently.
	nwl_parallel_max_compute	30	The maximum number of compute nodes allowed for a parallel update.
	nwl_parallel_max_gateway	1	The maximum number of gateway nodes allowed for a parallel update.
	respect_nova_az	true	Respect Nova availability zone (AZ). The true value allows the parallel update only for the compute nodes in the same AZ.
	ndr_skip_instance_check	false	The flag to skip the instance verification on a host before proceeding with the node removal. The false value blocks the node removal until at least one instance exists on the host.
	ndr_skip_volume_check	false	The flag to skip the volume verification on a host before proceeding with the node removal. The false value blocks the node removal until at least one volume exists on the host. A volume is tied to a specific host only for the LVM back end.