path: root/requirements.txt
AgeCommit message (Collapse)AuthorFilesLines
2017-05-30Updated from global requirementsOpenStack Proposal Bot1-1/+1
Change-Id: Ife3a3ee576b940f1f8a06d26a0cb99d69423cf9f
2017-04-05Updated from global requirementsOpenStack Proposal Bot1-1/+1
Change-Id: I40ecce838d12c2e232d8d4284bfa3ef3b88cebe4
2017-01-14Updated from global requirementsOpenStack Proposal Bot1-1/+1
Change-Id: Icadcb1b27852d729608195f4890f914c8350ac8c
2017-01-11Fix error path for tools/process-templates.pySteven Hardy1-0/+1
The error path for this fails because we don't import six or install it in the templates tox venv Change-Id: Ie9f46332f2b03d48a1b0a4a432e9721757833569
2017-01-10Updated from global requirementsOpenStack Proposal Bot1-1/+4
Change-Id: I9ae60dfb2ef5e8fb5aae482ddb08206fc1980ca5
2016-11-30Add local template generation tox taskDan Prince1-0/+1
This patch adds a local version of our template processing routine so that developers can more quickly view the templates that are actually getting generated. I've noticed multiple developers now do a full deployment with 'overcloud deploy' only to download the swift container with the generated templates. This simple task avoids that step by allowing developers to generate it locally. It also aims to preserve the ability to use t-h-t templates directly with Heat (instead of going through Mistral) should users wish to do that. The new undercloud heat installer requires the ability to generate templates without requiring Mistral and Swift to do so. Ideally the Mistral API workflow would use this same code so perhaps in the future we might modify that routine to: -download swift tarball containing the templates -run this local routine that lives in t-h-t -re-upload the tarball of templates to the swift container Change-Id: Ie664c9c5f455b7320a58a26f35bc403355408d9b
2013-10-22Add release configuration.Chris Jones1-0/+1
We can now release through openstack.org infrastructure. Change-Id: I6dff6ae4a97db15bdc4ce419e46e9a125bec277c