If you run VMware Cloud Foundation 9.1 nested in a homelab, VCF Automation (VCFA) is the appliance that will make your host fans spin. It ships as a single “one size fits all” deployment sized at a minimum of 24 vCPU + 96 GB RAM, and internally it’s a full Kubernetes platform. Drop that onto a modest nested host and you’ll see high CPU, contention, and – if you start “optimizing” the wrong things like me – a spectacular cascade of failures. In this blog I’ll describe my journey to get a stable and performing VCFA appliance in my homelab.
Tag: Homelab Page 1 of 4
VMware Cloud Foundation (VCF) 9.1 has been released a few weeks ago. Although I’m already a bit late to the game, I’ve finally found the time to deploy it in my lab environment. This blog post provides a step-by step guide how to prepare my lab and it provides a deep-dive guide how to deploy the complete VCF 9.1 stack on a single physical ESX host.
In the previous blog posts, I’ve outlined how to setup the foundational infrastructure to enable the cloud consumption experience on our private VMware Cloud Foundation cloud platform by using VCF Automation (VCFA).
In this blog post, we’ll have a look at how to setup everything as the service provider side, and how to finally access the self-service cloud as a tenant.
In VMware Cloud Foundation (VCF) 9 there are two options to deploy VCF Automation (VCFA) 9. The first is through the VCF Installer, the second is through Fleet Management in VCF Operations.
In this blog post, I’ll demonstrate how to deploy VCFA 9 as day-n action through VCF Fleet Management.
VMware Cloud Foundation (VCF) 9 now supports a variety of storage types as principal storage, such as vSAN ESA/OSA, Fibre Channel, and NFS v3. In this blog article, I’ll demonstrate the necessary steps to deploy the Management Domain of a VCF9 instance with NFS as principal storage.