The main idea of this blueprint is to be able to run ManageIQ components is separate containers. This would allow a better scale out of the application with the provisionning of more workers, possibly on different nodes. With an [anti-]affinity policy for container placement, ManageIQ could enforce high availability.
One of the direct application could be the deployement of containers on top of OpenShift, leveraging the auto-scaling features of OpenShift to handle ManageIQ. I know that ManageIQ will have the ability to deploy an OpenShift environment, so we might fall into a chicken/egg issue.
This could also be used to deploy ManageIQ on top of OpenStack with the Docker Nova driver and use Heat to handle high availability and auto-scaling. Same feeling with chicken/egg.
This feature will probably need ManageIQ to run on CentOS 7 to use Docker. BTW, migrating ManageIQ to CentOS 7 would be a nice move…