Project Bonneville has been introduced last year. Now the question is why VMware has introduced this project, the idea behind is that there is a strong difference between the constructs docker which used in the Linux Docker host and the constructs ESXi uses as a hypervisor. Finally Vmware analyzed that project Bonneville has allowed us to do is to run a docker image as a VM on top of a hypervisor.
Right now IT is facing one of the biggest problem is that their customers asks for “ big linux VMs” only to find out that they deployed containerized applications inside those instances. IT has no idea how to monitor and secure those applications. The Bonneville approach solves this problem by instantiating those applications as separate virtual machines.
After 18 months Vmware is presenting these technologies as a part of vSphere.
Now the customers have the option of access a feature of vSphere called vSphere Integrated Containers.
VSphere integrated container is made up of three different technologies which make them unique. Theses three technologies are discussed below and if you want to know more about the vSphere Integrated Containers , you can join VMware training at Getprotech .Getprotech provides the VMware training in Delhi.
VIC engine is a rebase of project Bonneville. The engineering team decided to re-write and include a so called Portlayer which means it is an interface that exposes vSphere objects and services as containers primitives on the top of that we can have different personalities.
In the virtual container host there is a small VM that works as the Docker endpoint. The IP of that VM is what the vSphere admin would hand over to the internal customers that need Docker. When the customer run “docker run – H <IP>busybox” the busybox docker image will be pulled from Docker Hub and it will be emerging as a VM inside the Virtual Container Host vApp.
As we all can see VIC Engine is the core component of vSphere Integrated Containers, vmware released that Enterprise beacuse customers were asking for more. So VMware has decided to create a product that would do more than just copy the behavior of a compatible Docker Engine. Because of this reason vSphere Integrated Containers also delivers Harbor, an enterprise Docker registry.
Then vSphere admins can hand over its FQDN or IP address to their internal customers. So that they can use the registry service by Harbor as a secure Docker registry stored inside the data center.
It is called an extension of vRealize Automation 7.2.
However given admiral can be built separately and operated without any help, VMware decided to add Admiral to the vSphere Integrated Containers product.
So Vmware is giving lot of advantage of admiral features in context of vSphere Integrated Containers which includes providing a user interface for Virtual Container hosts consumption and the capability of composing multi container applications to be arranged as article.
So admiral is still considered as a part of vSphere Integrated Containers.