vSphere Integrated Containers – The Next Step

VMware has been working on integrating container technology into it’s core products. For this the descision was made to do it in an open-source project. This ofcourse is a different strategy for VMware as everything has been closed source until recently. The open source project has made progess over the last year and we are now getting to the point that it is actually becoming a product that can be used in production by vSphere customers.

During VMworld 2015 VMware announced vSphere Integrated Containers. At the time this was just the project that came out of Project Bonneville; the integration of Docker containers within vSphere. Today VMware announced that it is not only the integration of containers in vSphere, which is now know as vSphere Integrated Containers Engine (VIC Engine), but also a Container Management Portal (Project Admiral) and a Container Registry (project Harbor). This now will be know in as vSphere Integrated Containers and provides vSphere administrators with a full set of tools that can be used to provide containers to developers and container users.

In this post I’ll explain what vSphere Integrated Containers (VIC) is and what the components do that make up VIC.

So as you can see on the marchitecture above, vSphere Integrated Containers consists out of there components :

  • VIC Engine
  • Container Management Portal (Project Admiral)
  • Container Registry (Project Harbor)