When the metadata server starts first, it will wait for the engine to come up
and only then registers it's hostname and port and becomes available.
Signed-off-by: Tomas Sedovic <tomas@sedovic.cz>
Ref #115, rework API mapper to route by Action= query parameter,
not by path, and align heat CLI tool with revised API.
Signed-off-by: Steven Hardy <shardy@redhat.com>
In order for the Stack creation to fail, resources must raise an exception
when their creation fails. The Stack's create code will set the resource
state appropriately; resources should not silently do it themselves.
Signed-off-by: Zane Bitter <zbitter@redhat.com>
Replace 'events_list' with 'event-list' and 'jeos_create' with
'jeos-create'. This makes things consistent with the conventions of
OpenStack projects. The old versions will continue to work for now.
Signed-off-by: Zane Bitter <zbitter@redhat.com>
Previously we just printed an error message about not specifying a command
to get help about, and no hint about how to work out which commands even
existed.
Signed-off-by: Zane Bitter <zbitter@redhat.com>
Convert the Getting Started wiki page to ReStructuredText format and add it
to the repository. Also add a script that will extract the shell commands
from the document and run them, so we can use it as an integration test.
The script can be run using the command:
> bash -c "$(./tools/rst2script.sed docs/GettingStarted.rst)"
Related: #84
Signed-off-by: Zane Bitter <zbitter@redhat.com>
The database impl was raising an exception if no parsed template
exists. The logic that was looking up the parsed template
expects None to be returned if the template isn't stored.
* I also fixed some pep8 errors.
Calling stack.validate will modify the stack's template, which
we don't want to do. We just want to validate the template and move
on with an already parsed template.
The stack creation call to validate the stack was resetting the
stack template attribute. I've made a copy of the stack purely
for validation purposes.
Install tox via easy_install. Tox automates the creation of multiple
virtual environments, each of which can be used with a different
interpreter or specific custom tests (and is what StackForge uses).
Signed-off-by: Jeff Peeler <jpeeler@redhat.com>