USER STORIES:

* As a cloud operator, I want to change placement of services across roles/nodes without any service disruption so that I can change my architecture on-fly.

Example use case:

* As a cloud operator I want to separate my RabbitMQ from Controller into standalone role so that I increase my performance of control plane.

In this case, user wants to remove RabbitMQ from Controller heat-template and create new heat-template called MessageBus which contains that service, trigger stack update and end up with new architecture.

Target is to apply similar use case to any of the roles which we defined as they can be "standalone" and support these changes after user deployed his stack. From deployment framework, we should be capable of providing flexible model which would allow to expand this scope to more services through out the time (not just limited set).

We are targeting this effort to be on top of containers, therefor moving to OSP13.