Fix issues with EIP unit test

The resource was not being destroyed correctly, but errors were ignored.

Change-Id: I1caa9d092f58f458bd6da46f4cba4ad027b1fd38
Assert on Resource double-create()

There's no valid case in which we should be creating a resource multiple
times.

Change-Id: Id90edd3a09ec15d3814a322ac0b7ec75fd0be54a
Propagate creation errors with exceptions

Change-Id: I567f1901e1203930d282620112368ac32440b9ed
Mark resources as failed when creation aborted

Previously resources would be left in the CREATE_IN_PROGRESS state in the
event of a timeout or the thread being cancelled (due to a delete being
requested while the stack was still being created). We should instead put
these resources into the CREATE_FAILED state when this occurs, thus
creating an event with the reason.

Change-Id: I05956aa9ef26941b79cef9dbf0cb6a347047d199
Mock delete_network in Quantum unit tests

Change-Id: I0a1f0e56ed84aa4efcdf7c65c7c634f738bdddda
Propagate deletion errors with exceptions

Change-Id: Ib8380f6d985e328c56d53b326700d6c9df636f40
Optionally allow ec2token config to come from .conf

Just like keystoneclient.middleware.auth_token
first checks paste.ini file then .conf file when fetching
a config value

Change-Id: I9db9744d0ab12fcf486de9a9d3f8e870a4ff66de
Move ec2token defaults from paste.ini to .conf

paste.ini files can now be considered not user-editable
(in normal circumstances)

Change-Id: Ia2a6d784ed2fad009de9e77717e6e0dc00c5e2f4
Consolidated api-paste.ini file

Load a single api-paste.ini file, specified by config
Delete unused paste.ini files
Update docs for new paste.ini and config arrangement

There will be a corresponding devstack change, and once this is in
I will email the packagers on the packaging implications

Change-Id: Ic10b1a486094d15bfd832f0f934e6268ec323085
Do not initialize anything during import phase

The structure of the program is compromised by doing too much logic in
the import phase. We can read the code more cleanly if we can see where
the intended initialization code is called. This may make tests slightly
more tedious to write, but that should be handled by writing generic
fixtures which can be reused for exactly this purpose.

Change-Id: I1d221e2f90d1f6e89717a37d2128caabd077d30a
Merge "Optionally allow ec2token config to come from .conf"
Merge "Move ec2token defaults from paste.ini to .conf"
Merge "Propagate creation errors with exceptions"
Merge "Mark resources as failed when creation aborted"
Merge "Mock delete_network in Quantum unit tests"
Merge "Propagate deletion errors with exceptions"
Merge "Consolidated api-paste.ini file"
Send RPCs to 'engine' topic not 'engine.$host'

Fixes bug #1173573

We currently send engine RPCs to the 'engine.$host' topic means that
it is impossible to run heat-api and heat-engine on different
machines because you can't configure heat-api with the hostname of
heat-engine.

Fix this simply by sending RPCs to 'engine' which heat-engine. We have
always listened on this topic, so there is no backwards compat
concerns.

This is somewhat related to the multiple-engines blueprint, but
doesn't really help or hinder it.

Change-Id: Ibd4dc948ace4476bfa8e7fdc86e948a622416e58
Remove engine_topic configuration option

Fixes bug #1173575

This is currently broken since heat-engine always listens to the
'engine' topic and there isn't actually a good use case for this to be
configurable, so let's kill it.

Change-Id: I35c0292c921f81857f80a7f111df5ac330d54ecf
Merge "Do not initialize anything during import phase"