Clarify a comment which says we require KeyName - which is incorrect

The Nova create API requires a name, image, and flavor.  The key_name
is not mandatory.  Possibly in AWS InstanceType (flavor) is not
mandatory but it is with Nova.

blueprint native-nova-instance

Change-Id: I6f5a77d7999ea4d8e91402ae215179b982a947f6
add error flow tests for volume detach

engine.resources.volume.VolumeAttachment lacks tests for some
exception flows

Fixes bug #1183239

Change-Id: I3d84fadb1ff60c622fbfbd634e003aaab382b405
Allow stacks to be created without a timeout

This should be the default for nested stacks, rather than the default
timeout of 60 minutes for stacks created through the API.

Change-Id: Iacee6eaf8f345e506b417e776f696db6b11bbf20
Implement timeouts for nested stacks

This also means that if no default is specified, nested stacks will not
time out (previously they used the default timeout of 60 minutes). Of
course, like other resources, creation of the nested stack will stop if and
when the parent stack times out.

Change-Id: Ibd55c32d63e971f79319ed40321fa4be52b65419
Create stacks with a co-routine

This will allow nested stacks to be created in parallel with other stack
resources in the future.

Change-Id: If1817bddcea50fdd7b640dee5b5d12257aada651
Create nested stacks in parallel

Use check_create_complete() to advance the nested stack creation, so that
it can occur in parallel with other resources in the parent stack.

Implements blueprint concurrent-resource-scheduling

Change-Id: I841b4c93b257409eecd0d2a43b35d9bee114ab87
Handle metadata updates during stack creation

Don't try to recalculate the metadata on an instance that hasn't yet been
stored in the database.

Fixes bug #1185530

Change-Id: I39f2733e2ba4730ea05a4a50962cb30f044ef752
Merge "Clarify a comment which says we require KeyName - which is incorrect"
Merge "add error flow tests for volume detach"
scheduler: Fix inifinite loop for no-wait tasks

When a task run by a DependencyTaskGroup completed immediately (i.e. it
was marked as done right after calling start()), the corresponding entry in
the dependency graph was never removed. As a result the DependencyTaskGroup
would continue running forever (or until it timed out).

Fixes bug #1186389

Change-Id: I9715b54a61d1c3adc22403bc39f8673306bffead
Log at DEBUG level in unit tests

By default, only INFO and higher severities were logged.

Change-Id: I5791cd163a54224b798bcc2987ac792b3b7b4030
Fix an intermitting failure in test_metadata_refresh

Given that resource creation can happen in parallel, the call to
check_create_complete may not follow the call to handle_create, so mock
those without checking the order.

Change-Id: Icf40f7339dc4c6e885c4a42f3a2c3f546f14c08d
Fix Hacking H304 Warnings

And also enable it permanently.

Change-Id: Iae319ecaee86049bc25330e25c4f672e3b158851
a minor fix to volume.py

There seems a typo with the exception name and the comment.

Change-Id: I5c0abe48c81a69e4b879b080236899031bb40e97
Merge "a minor fix to volume.py"
Merge "Fix Hacking H304 Warnings"
Merge "Log at DEBUG level in unit tests"
Merge "Handle metadata updates during stack creation"
tests : fix cut/paste test name shadowing

Fix test class duplication

Change-Id: I4ff21b60ad6c70d8d4563db54c9afd83f59d6957
Relax lxml version requirements.

This was preventing devstack from starting on Fedora 18 due to the
package python-lxml-3.2.1-1.fc18.x86_64 being too new.

This change is aligns the lxml rule with the requirements project.

Change-Id: Idd3697596dcefb830d60f8e44171b8c50e78178a