The older hacking library has a cap on pbr <2.0, with the recent 2.0.0 release of PBR it's causing failures in the pep8 job. hacking isn't kept in sync via the typical proposal-bot updates. Do it manually to clear the gate issue. pep8 runtests: commands | flake8 ./os_collect_config/merger.py:45:22: W292 no newline at end of file return final_list Change-Id: If863d2e190a4e1701ebf1fcb99a783075cda2556 Related-Bug: #1668848
|6 years ago|
|os_collect_config||6 years ago|
|.coveragerc||8 years ago|
|.gitignore||9 years ago|
|.gitreview||10 years ago|
|.testr.conf||10 years ago|
|LICENSE||10 years ago|
|MANIFEST.in||10 years ago|
|README.rst||7 years ago|
|os-collect-config-and-friends.odg||9 years ago|
|os-collect-config-and-friends.svg||9 years ago|
|requirements.txt||7 years ago|
|setup.cfg||10 years ago|
|setup.py||8 years ago|
|test-requirements.txt||6 years ago|
|tox.ini||6 years ago|
Team and repository tags
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 been changed.
You must define what sources to collect configuration data from in /etc/os-collect-config.conf.
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 is changed, default.command will be run. A file will be written to the cache dir, os_config_files.json, which will be a json list of the file paths to the current copy of each metadata source. This list will also be set as a colon separated list in the environment variable OS_CONFIG_FILES for the command that is run. So in the example above, os-refresh-config would be executed with something like this in OS_CONFIG_FILES:
The previous version of the metadata from a source (if available) is present at $FILENAME.last.
When run without a command, the metadata sources are printed as a json document.
sudo pip install -U git+git://git.openstack.org/openstack/os-collect-config.git
Run it on an OpenStack instance with access to ec2 metadata:
That should print out a json representation of the entire ec2 metadata tree.
Recommend using LibreOffice draw to edit os-collect-config-and-friends.odg and regenerate the svg file. Alternatively edit the svg directly, but remove the .odg file if that is done.↩︎