Deploying With Crowbar
- About This Guide
- I Architecture and Requirements
- II Setting Up the Administration Server
- 3 Installing the Administration Server
- 4 Installing and Setting Up an SMT Server on the Administration Server (Optional)
- 5 Software Repository Setup
- 6 Service Configuration: Administration Server Network Configuration
- 7 Crowbar Setup
- 8 Starting the SUSE OpenStack Cloud Crowbar installation
- 9 Customizing Crowbar
- III Setting Up OpenStack Nodes and Services
- IV Setting Up Non-OpenStack Services
- V Maintenance and Support
- VI Proof of Concepts Deployments
- A VMware vSphere Installation Instructions
- B Using Cisco Nexus Switches with Neutron
- C Documentation Updates
- Glossary of Terminology and Product Names
14 Configuration Files for OpenStack Services #
- File Name: depl_ostack_configs.xml
- ID:
Typically, each OpenStack component comes with a configuration file, for
example: /etc/nova/nova.conf.
These configuration files can still be used. However, to configure an
OpenStack component and its different components and roles, it is now
preferred to add custom configuration file snippets to a
SERVICE.conf.d/ directory
instead.
14.1 Default Configuration Files #
- File Name: sec.depl.ostack.configs.default
- ID:
By default, a configuration snippet with a basic configuration for each OpenStack component is available in the following directory:
/etc/SERVICE/SERVICE.conf.d/010-SERVICE.conf
For example: /etc/nova/nova.conf.d/010-nova.conf
Those files should not be modified.
14.2 Custom Configuration Files #
- File Name: sec.depl.ostack.configs.custom
- ID:
To adjust or overwrite settings for the respective OpenStack component, add a
custom configuration file to the same directory,
/etc/SERVICE/SERVICE.conf.d/.
The same applies if you want to configure individual components or roles of
an OpenStack component, like nova-api or
nova-compute, for example. But in this case, add your
custom configuration file to the following directory:
/etc/SERVICE/ROLE.conf.d/
For example: /etc/nova/nova-api.conf.d/
All custom configuration file must follow the rules listed in Section 14.3, “Naming Conventions for Custom Configuration Files”.
14.3 Naming Conventions for Custom Configuration Files #
- File Name: depl_ostack_configs.xml
- ID: sec-depl-ostack-configs-custom-naming
Use the following rules for any configuration files you add:
The file name must start with a 3-digit number and a dash. For example:
/etc/nova/nova.conf.d/500-nova.confThe file must have the following file name extension:
.confFor configuration management systems (for example: Crowbar, Salt), use numbers between
100and499.To override settings written by the configuration management system, use numbers starting from
500. They have higher priority.
14.4 Processing Order of Configuration Files #
- File Name: depl_ostack_configs.xml
- ID: sec-depl-ostack-configs-custom-order
The configuration files are processed in the following order:
/etc/SERVICE/SERVICE.conf/etc/SERVICE/SERVICE.conf.d/*.conf(in dictionary order)/etc/SERVICE/ROLE.conf.d/*.conf(in dictionary order)
If conflicting values are set for the same parameter, the last configured value overwrites all previous ones. In particular, values defined in
/etc/SERVICE/SERVICE.conf.d/XXX-SERVICE.conf
overwrite configuration values in
/etc/SERVICE/SERVICE.conf
14.5 For More Information #
- File Name: depl_ostack_configs.xml
- ID: sec-depl-ostack-configs-custom-more
For details, also see
/etc/SERVICE/README.config.