Skip to main content

Config files from cloud metadata

Project description

Team and repository tags

https://governance.openstack.org/tc/badges/os-apply-config.svg

os-apply-config

Apply configuration from cloud metadata (JSON)

What does it do?

It turns metadata from one or more JSON files like this:

{"keystone": {"database": {"host": "127.0.0.1", "user": "keystone", "password": "foobar"}}}

into service config files like this:

[sql]
connection = mysql://keystone:foobar@127.0.0.1/keystone
...other settings...

Usage

Just pass it the path to a directory tree of templates:

sudo os-apply-config -t /home/me/my_templates

By default it will read config files according to the contents of the file /var/lib/os-collect-config/os_config_files.json. In order to remain backward compatible it will also fall back to /var/run/os-collect-config/os_config_files.json, but the fallback path is deprecated and will be removed in a later release. The main path can be changed with the command line switch –os-config-files, or the environment variable OS_CONFIG_FILES_PATH. The list can also be overridden with the environment variable OS_CONFIG_FILES. If overriding with OS_CONFIG_FILES, the paths are expected to be colon, “:”, separated. Each json file referred to must have a mapping as their root structure. Keys in files mentioned later in the list will override keys in earlier files from this list. For example:

OS_CONFIG_FILES=/tmp/ec2.json:/tmp/cfn.json os-apply-config

This will read ec2.json and cfn.json, and if they have any overlapping keys, the value from cfn.json will be used. That will populate the tree for any templates found in the template path. See https://opendev.org/openstack/os-collect-config for a program that will automatically collect data and populate this list.

You can also override OS_CONFIG_FILES with the –metadata command line option, specifying it multiple times instead of colon separating the list.

os-apply-config will also always try to read metadata in the old legacy paths first to populate the tree. These paths can be changed with –fallback-metadata.

Templates

The template directory structure should mimic a root filesystem, and contain templates for only those files you want configured. For example:

~/my_templates$ tree
.
+-- etc
    +-- keystone
    |    +-- keystone.conf
    +-- mysql
          +-- mysql.conf

An example tree can be found here.

If a template is executable it will be treated as an executable template. Otherwise, it will be treated as a mustache template.

Mustache Templates

If you don’t need any logic, just some string substitution, use a mustache template.

Metadata settings are accessed with dot (‘.’) notation:

[sql]
connection = mysql://{{keystone.database.user}}:{{keystone.database.password}}@{{keystone.database.host}}/keystone

Executable Templates

Configuration requiring logic is expressed in executable templates.

An executable template is a script which accepts configuration as a JSON string on standard in, and writes a config file to standard out.

The script should exit non-zero if it encounters a problem, so that os-apply-config knows what’s up.

The output of the script will be written to the path corresponding to the executable template’s path in the template tree:

#!/usr/bin/env ruby
require 'json'
params = JSON.parse STDIN.read
puts "connection = mysql://#{c['keystone']['database']['user']}:#{c['keystone']['database']['password']}@#{c['keystone']['database']['host']}/keystone"

You could even embed mustache in a heredoc, and use that:

#!/usr/bin/env ruby
require 'json'
require 'mustache'
params = JSON.parse STDIN.read

template = <<-eos
[sql]
connection = mysql://{{keystone.database.user}}:{{keystone.database.password}}@{{keystone.database.host}}/keystone

[log]
...
eos

# tweak params here...

puts Mustache.render(template, params)

Quick Start

# install it
sudo pip install -U git+https://opendev.org/openstack/os-apply-config.git

# grab example templates
git clone https://opendev.org/openstack/tripleo-image-elements /tmp/config

# run it
os-apply-config -t /tmp/config/elements/nova/os-apply-config/ -m /tmp/config/elements/seed-stack-config/config.json -o /tmp/config_output

Project details


Release history Release notifications | RSS feed

Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distribution

os-apply-config-14.0.0.tar.gz (28.2 kB view details)

Uploaded Source

Built Distribution

os_apply_config-14.0.0-py3-none-any.whl (32.0 kB view details)

Uploaded Python 3

File details

Details for the file os-apply-config-14.0.0.tar.gz.

File metadata

  • Download URL: os-apply-config-14.0.0.tar.gz
  • Upload date:
  • Size: 28.2 kB
  • Tags: Source
  • Uploaded using Trusted Publishing? No
  • Uploaded via: twine/5.0.0 CPython/3.11.7

File hashes

Hashes for os-apply-config-14.0.0.tar.gz
Algorithm Hash digest
SHA256 8c44ef209268bc8ec2f45e34e734f8bb381decd517b6221f2714c22a00eda99d
MD5 784adda8c69cf85d6d539480ecde4bc0
BLAKE2b-256 6cd6a324904b9f1549290241c4349828893534ad1745cd35f04a39ebd52a2cc3

See more details on using hashes here.

File details

Details for the file os_apply_config-14.0.0-py3-none-any.whl.

File metadata

File hashes

Hashes for os_apply_config-14.0.0-py3-none-any.whl
Algorithm Hash digest
SHA256 0c4541dad0930f553cc577d16523c277ffd2b42aa9e08f649b2c193e05779bbf
MD5 a8f9fac99090005d5c22907e777bf734
BLAKE2b-256 5687ca051a2f5505b1fe693e9c6cc5e546d6e11f3c697d0a5a1222689c4d8ec1

See more details on using hashes here.

Supported by

AWS AWS Cloud computing and Security Sponsor Datadog Datadog Monitoring Fastly Fastly CDN Google Google Download Analytics Microsoft Microsoft PSF Sponsor Pingdom Pingdom Monitoring Sentry Sentry Error logging StatusPage StatusPage Status page