This commit was bulk generated and pushed by the OpenDev sysadmins as a part of the Git hosting and code review systems migration detailed in these mailing list posts: http://lists.openstack.org/pipermail/openstack-discuss/2019-March/003603.html http://lists.openstack.org/pipermail/openstack-discuss/2019-April/004920.html Attempts have been made to correct repository namespaces and hostnames based on simple pattern matching, but it's possible some were updated incorrectly or missed entirely. Please reach out to us via the contact information listed at https://opendev.org/ with any questions you may have.
|3 years ago|
|os_collect_config||3 years ago|
|zuul.d||3 years ago|
|.coveragerc||6 years ago|
|.gitignore||3 years ago|
|.gitreview||3 years ago|
|.stestr.conf||3 years ago|
|LICENSE||9 years ago|
|MANIFEST.in||9 years ago|
|README.rst||3 years ago|
|os-collect-config-and-friends.odg||8 years ago|
|os-collect-config-and-friends.svg||8 years ago|
|requirements.txt||4 years ago|
|setup.cfg||3 years ago|
|setup.py||5 years ago|
|test-requirements.txt||3 years ago|
|tox.ini||3 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+https://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.↩︎