VMware vSphere Integrated Containers: Introduction

2018-07-13 711 words 4 minutes

Contents

I´m very keen on everything related to Cloud-Native and all topics around the decoupling of a process from the underlying operating system and as well much more on the infrastructure underneath in order to run those distributed systems, which are the result by the end of the day.

For me personally, it became so present in 2016 for the first time and far more when I decided to work for VMware. Did you know that VMware is a huge contributor to Open Source Projects and a Platinum Member at the Cloud Native Computing Foundation - CNCF? You´ll find an overview of our open source projects here.

One of these Open Source Projects is vSphere Integrated Containers aka VIC. With vSphere Integrated Containers, Container Images get instantiated as a Virtual Machine by using PhotonOS, a minimal Linux Distribution by VMware, basically to be up and running in a few seconds.

Running Containers as a Virtual Machine means that IT-Ops Teams still have the ability to treat them like classical workload before. Therefore you don´t have to build out a separate, tailored infrastructure stack and can continue to leverage existing Scalability, Security and Monitoring capabilities.

/img/posts/201807_vic_getting_started/CapturFiles-20180710_094308.jpg — Figure I: Virtual Container Host vs. Docker Container Host

vSphere Integrated Containers also supports running native Docker container hosts on vSphere. It allows developers to self-provision Docker container hosts for use as a development sandbox, a build server or a swarm cluster. Now you can treat a Docker host as ephemerally as a container.

In my role as a VMware Technical Account Manager I have the chance to meet individuals in various roles at Enterprises. Many share the same strategic priority: Transform some of their monolithic applications.

vSphere Integrated Containers can leverage a solution for use cases like App Repackaging and Developer Sandbox. Just to name a few.

VMware vSphere Integrated Containers Version 1.4 was already launched by our Cloud-Native Business Unit (CNABU) on the 15th of March this year.

And while I´m writing this series…

vSphere Integrated Containers 1.4.1 has just been released - Docs: https://t.co/ZWmmWQ8zHO; RN: https://t.co/Uj2K57ueCx; DL: https://t.co/B2mjmsgpVQ @cloudnativeapps #Docker #vSphere #RunAllTheThings
— Bjoern Brundert (@bbrundert) July 13, 2018

…VIC version 1.4.1. has been released and includes:

Added the ability to manage use of DRS VM affinity groups for existing VCHs using vic-machine configure.
When copying a CLI command on the Summary page of the VCH Creation Wizard, a confirmation message is now shown.
New Built-In Repositories view in vSphere Integrated Containers Management Portal provides better visibility on all repositories that reside in the vSphere Integrated Containers Registry.
Security and bug fixes.

More details through the Release-Notes here.

VIC Component Overview

You´ll get an quick overview over the VIC components through this Lightboard Video by Patrick Daigle:

Components

vSphere Integrated Containers Engine, a container runtime for vSphere that allows you to provision containers as virtual machines.
vSphere Integrated Containers Plug-In for vSphere Client, that provides information about your vSphere Integrated Containers setup and allows you to deploy virtual container hosts directly from the vSphere Client.
Harbor, an enterprise-class container registry server that stores and distributes container images.
Multi-tenant content signing and validation
Security and vulnerability analysis
Audit logging
Identity integration and role-based access control
Image replication between instances
Extensible API and graphical UI
vSphere Integrated Containers Management Portal based on project Admiral.