Stan Lagun 53abad42ab Always declare agent RabbitMQ queues ... Murano uses 1 RMQ queue per agent + 1 queue for agent listener. Listener queue is declared upon listener startup which happens when the first agent command sent. The agent queues were created by explicit call to Agent.prepare() which was done from Instance.deploy() method. This creates a problem if RabbitMQ server is restarted after deployment, all non-persistent queues disappear and then an action get called. If that action is not calling Instance.deploy() (because it assumes instance to be deployed by that time) and sends a command to an agent it will never be received. This commit removes explicit prepare() method. Now the queues are going to be created on demand, similar to listener queues do. Change-Id: I21ae1efd483f32bb7c8e3dc1849af656b3bed56f Closes-Bug: #1645419		2016-11-28 20:29:09 +00:00
..
meta	[test-runner] Refactor mock unit-tests	2016-01-11 12:18:01 +03:00
system	Always declare agent RabbitMQ queues	2016-11-28 20:29:09 +00:00
__init__.py	File Downloable Feature	2015-03-12 13:12:56 +01:00
test_mock_context_manager.py	Use more generic "type" name instead of "murano_class"	2016-02-26 17:25:25 +03:00
test_package_loader.py	Increase unit test coverage for Engine Package Loader.	2016-10-11 09:25:09 -04:00