7f36b61922
This is a mechanically generated patch to complete step 1 of moving the zuul job settings out of project-config and into each project repository. Because there will be a separate patch on each branch, the branch specifiers for branch-specific jobs have been removed. Because this patch is generated by a script, there may be some cosmetic changes to the layout of the YAML file(s) as the contents are normalized. See the python3-first goal document for details: https://governance.openstack.org/tc/goals/stein/python3-first.html Change-Id: I8ab3b15a4a2dae363b760987ab36b71fa11f2789 Story: #2002586 Task: #24341 |
||
---|---|---|
HOWTO | ||
doc/source | ||
instack | ||
.gitignore | ||
.gitreview | ||
.stestr.conf | ||
.zuul.yaml | ||
HACKING.rst | ||
LICENSE | ||
MANIFEST.in | ||
README.md | ||
babel.cfg | ||
openstack-common.conf | ||
requirements.txt | ||
setup.cfg | ||
setup.py | ||
test-requirements.txt | ||
tox.ini |
README.md
Team and repository tags
instack
instack executes diskimage-builder style elements on the current system. This enables a current running system to have an element applied in the same way that diskimage-builder applies the element to an image build.
instack, in its current form, should be considered low level tooling. It is meant to be used by higher level scripting that understands what elements and hook scripts need execution. Using instack requires a rather in depth knowledge of the elements within diskimage-builder and tripleo-image-elements.
An example of higher level tooling that uses instack to install a TripleO style undercloud is at: https://github.com/rdo-management/instack-undercloud