trove related enhancements

This adds some enhancements that are needed by the trove barclamp. We allow (default off) to enable access to rabbitmq via the public network so that the trove-guest-agent can reach it.

Note: This has some security implications. As it doesn't seem possible to restrict access to rabbitmq vhosts by IP address (only by user). All vhost/queues will be accessible on the public network, provided you know a valid username/password combination for that vhost :(

This is still missing a few things, which will follow soon:
* creating a special vhost, a user and setting permissions for trove
* testing if this works with HA enabled
* UI changes (I guess these can be optional as trove support is just a Tech preview)
 

Does it make sense to deallocate it in a `else`? Although it might be opening a can of worms (not sure how well that works :-))