Workflow issues when vCenter instance not correctly added to vRO

As part of my preparation work for VMworld 2018, I was looking into how one might be able to automate the deployment of VMs from vRealize Automation 7.4 with an appropriate policy for consuming the under-lying storage. In my case, this underlying storage was vSAN 6.7 (and vSphere 6.7), so I wanted to be able to select a vSAN policy for my VM Home namespace and disks. Fortunately, there is a vRealize Orchestration (vRO) plugin to do just that called the vRA SPBM Integration plugin. But, once I had this plugin installed, and followed the instructions, I hit a snag.…

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 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 CloudServer page takes me to the scality/S3 page. Anyway, let’s look at how to set this up.

Changing policies on-the-fly with VVols

Last week, I was presenting at the VMware User Group (VMUG) event in Poland. My topic was SPBM, Storage Policy Based Management. This is the framework for consuming data services, whether these are provided from vSAN, Virtual Volumes or VAIO (IO Filters). You can get the presentation from here. One of the attendees who had implemented Virtual Volumes (aka VVols) asked a very interesting question about changing policies of a VVol based VM on-the-fly. The question is whether a policy change causes a new VVol has to be instantiated, data synced to original VVol and then the original VVol is…

Slides from my Storage Policy Based Management presentation now available

My Storage Policy Based Management (SPBM) presentation slide deck is now available online. This is the presentation that I delivered at a number of VMUG (VMware User Group) meetings this year in Europe, primarily Norway and Poland. SPBM is an integral part of VMware’s software defined storage vision, and is deeply integrated into vSAN, Virtual Volumes (VVols) and VAIO, the vSphere APIs for I/O Filters. Hope you find it useful. 2017 VMUG Storage Policy Based Management from Cormac Hogan

Upcoming speaker session at the Poland/Polska VMUG (Warsaw)

I’m delighted to announce that I have been invited back to present at the next Poland/Polska VMUG, which will take place in Warsaw on Wednesday, October 25th, 2017. I have been asked to deliver the keynote at this VMware User Group meeting, and I will be using the opportunity to present on Storage Policy Based Management (SPBM), and how important it is to have a seamless, policy based approach to managing data. It would seem that I am one of the first speakers of the day, so I will have a lot of free time later in the morning and…

View 7.1 and vSAN 6.6.1 interop – nice fix

Last week, I was rolling out Horizon View v7.1 on my new vSAN 6.6.1 all-flash configuration in the lab. Now, one of the pet peeves a few of us have had with this configuration was that a warning was always reported around read cache reservations on all-flash vSAN. Of course, read cache is irrelevant to all-flash (AF) configurations as it does not use a read cache; this is only applicable to hybrid vSAN configurations. This is why it was such as annoyance.