A short time back, I showed you how to change the Project Harbor configuration to use persistent storage provided by docker volume driver for vSphere and save your images on Virtual SAN. In this post, I will show you how to use Project Harbor by adding a new user to Harbor, create a new project for this user, login to Harbor via docker, and then push and pull image from the Project Harbor repo. While these instructions are simplified just to get you started, you should refer to the official project hard documentation which is available on the github site. The user guide can be found here.
Project Harbor is another VMware initiative in the Cloud Native Apps space. In a nutshell, it allows you to store and distributes Docker images locally from within your own infrastructure. While Project Harbor provides security, identity and management of images, it also offers better performance by having the registry closer to the build and run environment for image transfers. Harbor also supports multiple deployments so that you can have images replicated between them for high availability. You can get more information (including the necessary components) about Project Harbor on github.
In this post, we will deploy Project Harbor in Photon OS, and then create some docker volumes on Virtual SAN using the docker volume driver for vSphere. This will provide an additional layer of availability for your registry and images, because if one of the physical hosts in your infrastructure hosting Project Harbor fails, there is still a full copy of the data available. Special thanks to Haining Henry Zhang of our Cloud Apps team for helping me understand this process.
As my take-3 tenure in the VMware Cloud Native Apps (CNA) team draws to a close, the guys over at #vBrownBag have kindly invited me to come on their show and talk about the various VMware project and initiatives that I have been lucky enough to be involved with. All going well, I hope to be able to demonstrate the Docker Volume Driver for vSphere, some overview of Photon Controller CLI and Photon Platform with Docker Swarm, and maybe Kubernetes as well as some vSphere Integrated Containers (VIC). If you are interested, you can register here. I’d be delighted if you can make it. The show is on at 7pm (local time) tomorrow, Tuesday July 26th. See you there.
This is part of a series of articles describing how to use the new features of vSphere Integrated Containers (VIC) v0.4.0. In previous posts, we have looked at deploying your first VCH (Virtual Container Hosts) and container using the docker API. I also showed you how to create some volumes to provide consistent storage for containers. In this post, we shall take a closer look at networking, and what commands are available to do container networking. I will also highlight some areas where there is still work to be done.
Also, please note that VIC is still not production ready. The aim of these posts is to get you started with VIC, and help you to familiarize yourself with some of the features. Many of the commands and options which work for v0.4.0 may not work in future releases, especially the GA version.
This video will show you the steps involved in deploying Apache Mesos on VMware’s Photon Controller product using the “cluster” mechanism available in Photon Controller. It uses Photon Controller CLI to create a tenant, resource ticket and a project. It then shows how to create an appropriate image for VMs to run Mesos, how to enable the Photon Controller deployment for Mesos clusters, and finally the creation of the cluster. After the deployment has succeeded, you are shown some command outputs and Photon Controller UI views of the running cluster. I decided to pick Mesos in this case, as I have already written a lot on Docker Swarm and Kubernetes, and have shown how to deploy these both natively, and using the Photon Controller “canned” cluster mechanism.
*** Note that at the time of writing, stand-alone Photon Controller is still not GA ***
*** Steps highlighted in this video may change in the GA version of the product ***
I decided to put together a very short video on VIC – vSphere Integrated Containers v0.4.0. In the video, I show you how to create your very first VCH (Virtual Container Host) and then I show you how you can create a very simple container using a docker API endpoint. I also show you how this is reflected in vSphere. Of course, VIC v0.4.0 is still a tech preview, and is not ready for production. Also note that a number of things may change before the VIC becomes generally available (GA). However, hopefully this is of interest to those of you who wish to get started with v0.4.0.
For more information on VIC v0.4.0, visit us on github.
I mentioned yesterday that VMware made vSphere Integrated Containers (VIC) v0.4.0 available. Included in this version is support for container volumes. Now, as mentioned yesterday, VIC is still a work in progress, and not everything has yet been implemented. In this post I want to step you through some of the enhancements that we have made around docker volume support in VIC. This will hopefully provide you with enough information so that you can try this out for yourself.