Today I want to take a closer look at the new vSAN Data Persistence platform (DPp). I mentioned that this was a key reason for updating my VMware Cloud Foundation environment to version 4.2, which officially released last week. One of the services included in DPp is the MinIO S3 compatible object store. Although I have written about MinIO a number of time on this site, the fact that it is now incorporated as a service in the new DPp makes it even easier to deploy than ever before. In this post, we will look at the steps involved in…
VMware recently announced the release of VMware Cloud Foundation (VCF) version 4.2. I was particular interested in this release as it allows me to try out the new vSAN Data Persistence platform (DPp). My good pal Myles has an excellent introduction to DPp here and I plan to create a number of posts on it going forward. My VCF 4.1.0.1 environment is what we call a Consolidated Architecture , meaning that both the management domain and workload domain run on the same infrastructure. The primary application that I run in this environment is VCF with Tanzu (vSphere with Tanzu on…
To coincide with a new release of vSphere 7.0U1 and vSAN 7.0U1, there is also a new release of VMware Cloud Foundation releasing. This is VCF version 4.1. In this release, as well as a bunch of updates to the versions of the various VMware products that make up the VCF bill of materials, there are also some nice new enhancements. In this post, I’ll highlight the big features that I know a number of customers are interested in. Support for vVols as a Principal Storage for Workload Domains Virtual Volumes (vVols) is gaining more and more traction among VMware…
VMware recently announced that availability of VMware Cloud Foundation (VCF) 4.0.1. I was particularly interested in this release as it introduced some enhancements around vSphere with Kubernetes deployments on the VCF Management Domain. We refer to the deployment of an application onto the management domain as a VCF consolidated architecture. Whilst we were able to deploy vSphere with Kubernetes on the management domain in VCF version 4.0, it was not seamlessly integrated. In particular, it was not possible to select the management domain to do the necessary vSphere for Kubernetes validation tests. In VCF 4.0.1, it is now possible to…
Since the release of VMware Cloud Foundation (VCF) 4.0 over 1 month ago, I have been asked one question repeatedly – when can I run vSphere with Kubernetes (formerly known as Project Pacific) on a VCF 4.0 Consolidated Architecture? In other words, when can I deploy vSphere with Kubernetes on the Management Domain rather than building a separate VI Workload Domain to run it. The main reason for this request is because this reduces the number of ESXi hosts required to run vSphere with Kubernetes from 7 down to 4. So I am delighted to announce that we now have…
In my most recent VMware Cloud Foundation post (part 13), I highlighted the fact that if you used NSX-T as the networking platform for your workload domain (WLD), you could not attach vRealize Automation (vRA) to such a WLD via SDDC Manager. In that previous post, I showed how to manually deploy the vRA proxy agents on the Proxy VMs. These Proxy VMs were already deployed via SDDC Manager as part of the overall vRA deployment through SDDC Manager, but the agents were not installed at this point. If NSX-V was used as the networking platform for the WLD, then…
I’m still on my VMware Cloud Foundation v3.9 journey. My latest task was to connect my vRealize Components to my Workload Domains (WLDs). In part 2 I deployed vRealize Log Insight (vRLI) and vRealize Operations (vROps), and then in part 3 and part 4, I rolled out vRealize Automation. Now I wanted to connect them to the WLDs that I had rolled out previously. SDDC Manager makes this really easy. In just a couple of clicks I had connected vRLI and vROps to both VI WLDs. However, on trying to connect my vRealize Automation (vRA) 7.6 to my WLDs, I…