A first look at vFile – Sharing a persistent volume between containers

Regular readers will have noticed that I have been doing a bit of work recently with docker swarm, and what you need to do to get it to work on VMs running on vSphere. The reason why I had taken such an interest is because I wanted to look at a new product that our Project Hatchway team have been cooking up, namely vFile. In a nutshell, vFile provides simultaneous, persistent volume access between nodes in the same Docker Swarm cluster. In some ways, it can be thought of as an extension to vDVS, the vSphere Docker Volume Service (from…

Validating overlay network when docker swarm running on Centos VMs on vSphere

I got a chance to revisit my docker swarm deployment this week after a bit of a break. I was a little curious about my setup because when I spoke to some of our ‘Project Hatchway‘ engineers, I was told that I should be able to launch a single instance of Nginx in Docker Swarm (“docker service create –replicas 1 -p 8080:80 –name web nginx”) and I should be able to access the web service using the following command from any swarm node – “curl 127.0.0.1:8080”. This was not what I was seeing. When I launched the Nginx service, the…

Building a Docker Swarm with Photon OS

I’ve decided to take a look at our new vFile docker volume plugin. If you haven’t heard, vFile volume plugin for Docker provides simultaneous persistent volume access between hosts in the same Docker Swarm cluster for the base volume plugin service such as VDVS [vSphere Docker Volume Service], with zero configuration effort, along with high availability, scalability, and load balancing support. As you can see, this has a requirement on Docker Swarm. Since I hadn’t set this up in a while, I decided to set it up on a recent release of Photon OS, but ran into a small issue.

Project Hatchway hitting the mainstream – persistent storage for containers

Regular readers will be aware that I “dabble” from time to time in the world of Cloud Native Apps. For me, a lot of this dabbling is trying to figure out how I can go about providing persistent storage to container based applications. Typically this in the shape of container volumes that are carved out of the underlying storage infrastructure, whether that is VMFS, NFS, vSAN or even Virtual Volumes. VMware Project Hatchway has enabled me to do this on multiple occasions. Project Hatchway was officially announced at VMworld 2017, but I’ve been working with this team since the early…

A closer look at Scality S3 running on vSAN

After last week’s post of Minio running on top of vSAN to provide an S3 object store, a number of folks said that I should also check out Scality S3 server. After a bit of research, it seems that Scality S3 server is akin to the CloudServer from Zenko.io. I “think” Zenko CloudServer is an umbrella for a few different projects, one of which is the S3server. In fact, clicking on the GitHub link on the Zenko.io CloudServer page takes me to the scality/S3 page. Anyway, let’s look at how to set this up.

A closer look at Minio S3 running on vSAN

While we are always looking at what other data services vSAN could provide natively, at the present moment, there is no native way to host S3 compatible storage on vSAN. After seeing the question about creating an S3 object store on vSAN raised a few times now, I looked into what it would take to have an S3 compatible store running on vSAN. A possible solution, namely Minio, was brought to my attention. While this is by no means an endorsement of Minio, I will admit that it was comparatively easy to get it deployed. Since the Minio Object Store…

Project Hatchway – VMware Persistent Storage for Containers

Earlier yesterday, I had the opportunity to sit in on a VMworld 2017 session delivered by one of my colleagues, Tushar Thole. Tushar presented “Project Hatchway” to the audience, and like the description of this post suggests, this is all about providing VMware persistent storage to containers. In a nutshell, volumes can now be created on VMFS, NFS and on vSAN in the form of VMDKs, and these volumes can now be consumed by containers instantiated within a container host, i.e. a virtual machine. But there have been some interesting new enhancements which Tushar shared with us in the session.