Collect and cache metadata, run hooks on changes.

Go to file

Clint Byrum 140e527458 Detect invalid collectors. The program would blow up anyway, but provide users with a more friendly error message. Change-Id: If70fc27b61963058af036568b88535b7f2dcff3f		2013-07-07 08:55:28 -07:00
os_collect_config	Detect invalid collectors.	2013-07-07 08:55:28 -07:00
.gitignore	Rename to os-apply-config.	2013-06-14 15:30:14 +12:00
.gitreview	Fix .gitreview file	2013-06-26 12:53:07 -07:00
.testr.conf	Remove env vars we don't use.	2013-03-28 04:05:31 +01:00
.travis.yml	Aligned tests with OpenStack standards.	2013-03-28 03:40:38 +01:00
LICENSE	Aligned tests with OpenStack standards.	2013-03-28 03:40:38 +01:00
README.md	Correct inaccuracies in README.md	2013-07-03 12:54:14 -07:00
openstack-common.conf	Importing openstack-common using update.py and openstack-common.conf	2013-06-26 17:49:26 -07:00
requirements.txt	Fix problems exposed by trying against heat-api-cfn.	2013-07-03 12:44:37 -07:00
setup.cfg	Splitting os-collect-config into its own repo.	2013-06-26 12:40:25 -07:00
setup.py	Migrate to pbr and testr.	2013-03-28 02:37:45 +01:00
test-requirements.txt	Align to OpenStack Hacking rules.	2013-03-28 04:03:46 +01:00
tox.ini	Importing openstack-common using update.py and openstack-common.conf	2013-06-26 17:49:26 -07:00

README.md

os-collect-config

Collect configuration from cloud metadata sources.

What does it do?

It collects data from defined configuration sources and runs a defined hook whenever the metadata has changed.

Usage

You must define what sources to collect configuration data from in /etc/os-collect-config/sources.ini

The format of this file is

[default]
command=os-refresh-config

[cfn]
metadata_url=http://192.0.2.99:8000/v1/
access_key_id = ABCDEFGHIJLMNOP01234567890
secret_access_key = 01234567890ABCDEFGHIJKLMNOP
path = MyResource
stack_name = my.stack

These sources will be polled and whenever any of them changes, default.command will be run. OS_CONFIG_FILES will be set in the environment as a colon (":") separated list of the current copy of each metadata source. So in the example above, "os-refresh-config" would be executed with something like this in OS_CONFIG_FILES:

/var/run/os-collect-config/ec2.json:/var/run/os-collect-config/cfn.json

When run without a command, the metadata sources are printed as a json document.

Quick Start

sudo pip install -U git+git://github.com/stackforge/os-collect-config.git

run it on an OpenStack instance with access to ec2 metadata:

os-collect-config


That should print out a json representation of the entire ec2 metadata tree.