03416a844c
According to Openstack summit session [1], stestr is maintained project to which all Openstack projects should migrate. Let's switch to stestr as other projects have already moved to it. [1] https://etherpad.openstack.org/p/YVR-python-pti Change-Id: Ifa7bb85e6290898c073859cbaf38f566ece2dff9 |
||
|---|---|---|
| HOWTO | ||
| doc/source | ||
| instack | ||
| .gitignore | ||
| .gitreview | ||
| .stestr.conf | ||
| AUTHORS | ||
| 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