Massachusetts Open Cloud offers virtual machine based IaaS services on top of OpenStack. We recently started offering containers as a service using OpenShift by tightly integrating it with the OpenStack services. Our deployment uses Keystone to authenticate users, Swift to host the Docker registry and Cinder to automatically provision persistent volumes for containers. We use the OpenShift Console to expose our OpenStack cluster to container users in a generic way where they have access to compute, networking, and storage. By coupling container and VM users we are able to achieve a higher density in our cluster usage. We will present our architecture, the challenges we faced while setting up this service (e.g. in case of failures/updates in OpenStack), the best practices we formed (e.g. network patterns we identified to work best) for offering a reliable service, and the experiences of the first large-scale user of our service, a medical imaging service on the cloud.
We are offering containers as a service using OpenShift by tightly integrating it with the OpenStack services. Our OpenShift deployment uses Keystone to authenticate users, Swift to host the Docker registry and Cinder to automatically provision persistent volumes for containers. We use the OpenShift Console to expose our OpenStack cluster to container users in a generic way where they have access to compute, networking, and storage without making changes to Horizon. We will present our architecture, the challenges we faced while setting up this service (e.g. in case of failures/updates in OpenStack), the best practices we formed (e.g. network patterns we identified to work best) for offering a reliable service, and the experiences of the first large-scale user of our service, a medical imaging service on the cloud.