WilliamLam.com

How to change the default CPU and Memory requirements for deploying the VMC vCenter Cloud Gateway

by // 3 Comments

When deploying the VMware Cloud on AWS (VMC) vCenter Cloud Gateway (VCG), there is a minimum amount of vCPU and memory that is required for deployment. For customers who wish to evaluate this solution for non-production usage, such as a lab environment, it would be nice to be able to reduce the requirements purely for testing purposes. Today, the vCPU and Memory is not configurable and is currently encoded within a JSON configuration file as well as the VCG OVA. The fact that this is not part of the installer itself but within the OVA means we can actually change the default 🙂 Below are the instructions for updating the vCPU and Memory requirements for the VCG.

Step 1 - Download the VCG ISO from MyVMware and extract the ISO.

[Read more...]

Supermicro Home Lab Group Buy

by // 35 Comments

Happy New Years everyone! I was supposed to get this out right before the holidays but #babylam got really sick and I had to put this on hold.

Back in November I threw out an idea on Twitter to see if the #vCommunity would be interested in doing a group buy for some Supermicro kits, especially for those looking to upgrade their personal home labs to take advantage of all the new VMware goodies such as vSAN, NSX and PKS for example.

Within minutes, I had several dozen replies and it was clear that folks were definitely interested in refreshing their lab, especially with a smaller and more modern platform. Over the last few weeks, I have been working with MITXPC (who I have worked with before) on putting together some packages that would appeal to the majority of the community. Initially, I was thinking about three options: system-only (no memory/storage), system with memory (no storage) and system with memory and storage. To be clear, system means complete chassis with CPU and motherboard included. Please see the product links below for more details. 

Disclaimer: I am not affiliated with MITXPC nor am I receiving any referral bonus/compensation for the discounts listed below.

[Read more...]

Is a DNS server still required when using a Static IP for VCSA?

by // 7 Comments

When deploying a vCenter Server Appliance (VCSA), customers have two options for setting up a static network address: using either a hostname (Fully Qualified Domain Name) or just a static IP Address (e.g. no DNS). In the first option when using an FQDN, it should be no surprise that you need to also specify a valid DNS Server which the VCSA UI/CLI Installer will automatically validate both the forward and reverse address. This is the most common deployment model for customers in both production as well as for development environments such as a vSphere home lab.

In the second scenario, where a static IP Address is used, a DNS server is not required because we are NOT using an FQDN for the hostname but rather an IP Address. Having said that, if you have ever used the VCSA UI or CLI, you will find that the DNS Server entry is actually a required field and you can not proceed without providing an address.

VCSA UI Installer:

VCSA CLI Installer:

"network": {
    "ip_family": "ipv4",
    "mode": "static",
    "ip": "192.168.30.151",
    "dns_servers": [
        "192.168.30.1"
    ],
    "prefix": "24",
    "gateway": "192.168.30.1",
    "system_name": "192.168.30.151"
}

As mentioned earlier, we know that it should not be required but currently the VCSA Installer is a bit overly cautious in its pre-checks and does require a value today. This is something that has already been shared internally and the team will be relaxing this requirement in the future.

With that said, this leads us back to the original question posed in the blog title, do we need a valid DNS server when using a static IP for the VCSA?

[Read more...]