Home OpenStack-Ansible Installation Guide
OpenStack has many configuration options available in configuration files which take the form of .conf files (in a standard INI file format), policy files (in a standard JSON format) and also in YAML files (only in the Ceilometer project at this time).
OpenStack-Ansible provides the facility to include any options referenced in the OpenStack Configuration Reference through the use of a simple set of configuration entries in /etc/openstack_deploy/user_variables.yml.
This section provides guidance for how to make use of this facility. Further guidance is available in the Developer Documentation in the section titled Setting overrides in configuration files.
The most common use-case for implementing overrides are for the <service>.conf files (eg: nova.conf). These files use a standard INI file format.
As an example, if a deployer wishes to add the following parameters to nova.conf:
[DEFAULT]
remove_unused_original_minimum_age_seconds = 43200
[libvirt]
cpu_mode = host-model
disk_cachemodes = file=directsync,block=none
[database]
idle_timeout = 300
max_pool_size = 10
This would be accomplished through the use of the following configuration entry in /etc/openstack_deploy/user_variables.yml:
nova_nova_conf_overrides:
DEFAULT:
remove_unused_original_minimum_age_seconds: 43200
libvirt:
cpu_mode: host-model
disk_cachemodes: file=directsync,block=none
database:
idle_timeout: 300
max_pool_size: 10
Overrides may also be applied on a per host basis with the following configuration in /etc/openstack_deploy/openstack_user_config.yml:
compute_hosts:
900089-compute001:
ip: 192.0.2.10
host_vars:
nova_nova_conf_overrides:
DEFAULT:
remove_unused_original_minimum_age_seconds: 43200
libvirt:
cpu_mode: host-model
disk_cachemodes: file=directsync,block=none
database:
idle_timeout: 300
max_pool_size: 10
This method may be used for any INI file format for all OpenStack projects deployed in OpenStack-Ansible.
To assist deployers in finding the appropriate variable name to use for overrides, the general format for the variable name is: <service>_<filename>_<file extension>_overrides.
Deployers may wish to adjust the default policies applied by services in order to implement access controls which are different to the norm. Policy files are in a JSON format.
As an example, the deployer wishes to add the following policy in Keystone’s policy.json:
{
"identity:foo": "rule:admin_required",
"identity:bar": "rule:admin_required"
}
This would be accomplished through the use of the following configuration entry in /etc/openstack_deploy/user_variables.yml:
keystone_policy_overrides:
identity:foo: "rule:admin_required"
identity:bar: "rule:admin_required"
This method may be used for any JSON file format for all OpenStack projects deployed in OpenStack-Ansible.
To assist deployers in finding the appropriate variable name to use for overrides, the general format for the variable name is <service>_policy_overrides.
For convenience, this is a (possibly incomplete) list of overrides available: