WilliamLam.com

  • About
    • About
    • Privacy
  • VMware Cloud
  • Tanzu
    • Application Modernization
    • Tanzu services
    • Tanzu Community Edition
    • Tanzu Kubernetes Grid
    • vSphere with Tanzu
  • Home Lab
  • Nested Virtualization
  • Apple
You are here: Home / Home Lab / How to change the default CPU and Memory requirements for deploying the VMC vCenter Cloud Gateway

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

01.13.2019 by William Lam // 2 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.

Step 2 - Open a terminal (Windows, Mac or Linux) and change into the vcgw folder which contains the VCG OVA file. To update OVA, we first need to convert it to an OVF using OVFTool (which is bundled in the same directory called ovftool). The command below is for a Windows system, simply replace the path of ovftool based on your OS:

ovftool\win32\ovftool.exe --skipManifestGeneration VMware-vCenter-Cloud-Gateway-6.8.1.20000-11187510_OVF10.ova VMware-vCenter-Cloud-Gateway-6.8.1.20000-11187510_OVF10.ovf


Step 2 - Open the .json configuration file using your favorite editor and update both the cpu and memory requirements. This file is used by both the UI and CLI Installer to validate that your deployment environment has enough resources.

{
    "medium": {
        "cpu": 2,
        "memory": 8096,
        "host-count": 400,
        "vm-count": 4000,
        "disk-swap": "50GB",
        "disk-core": "50GB",
        "disk-log": "25GB",
        "disk-db": "25GB",
        "disk-dblog": "25GB",
        "required-disk-space": "190GB",
        "label": "vCenter Cloud Gateway",
        "description": "TDB"
    }
}

Step 3 - Now open the OVF file using your favorite editor and search for the following section and then replace the "VirtualQuantity" value of both vCPU and Memory with the values you wish to use. In the example below, I am changing the default configuration to use 2 vCPU and 8GB of memory which should be plenty for evaluation purposes. Once you are done, save your changes.

      <Item configuration="medium">
        <rasd:AllocationUnits>hertz * 10^6</rasd:AllocationUnits>
        <rasd:Description>Number of virtual CPUs</rasd:Description>
        <rasd:ElementName> 8 virtual CPUs</rasd:ElementName>
        <rasd:InstanceID>1</rasd:InstanceID>
        <rasd:ResourceType>3</rasd:ResourceType>
        <rasd:VirtualQuantity>2</rasd:VirtualQuantity>
      </Item>
      <Item configuration="medium">
        <rasd:AllocationUnits>byte * 2^20</rasd:AllocationUnits>
        <rasd:Description>Memory Size</rasd:Description>
        <rasd:ElementName> 24576 MB of memory</rasd:ElementName>
        <rasd:InstanceID>2</rasd:InstanceID>
        <rasd:ResourceType>4</rasd:ResourceType>
        <rasd:VirtualQuantity>8192</rasd:VirtualQuantity>
      </Item>

In addition, we also need to update the referenced size of our .json configuration file from its original contents within the OVF. In my example, the original file size was 376 bytes and the modified file is now 375. To do so, open the OVF file and search for "vmcg-layout.json" and then update the value of the size.

<ovf:File ovf:href="VMware-vCenter-Cloud-Gateway-6.8.1.20000-11187510_OVF10-file1.json" ovf:id="vmcg-layout.json_id" ovf:size="375"/>

Step 3 - Finally, we need to re-create the OVA by running the command below. Before doing so, make sure to rename the original OVA to some other file so you have a backup of the original file.

ovftool\win32\ovftool.exe VMware-vCenter-Cloud-Gateway-6.8.1.20000-11187510_OVF10.ovf VMware-vCenter-Cloud-Gateway-6.8.1.20000-11187510_OVF10.ova


Step 4 - Once the new OVA has been generated, you can now deploy the VCG using either the UI or CLI Installer.

As you can see in the screenshot below, our new VCG has been deployed with 2 vCPU and 8GB of memory.

More from my site

  • Enhancements to Hybrid Linked Mode (HLM) in VMC using the new vCenter Cloud Gateway
  • vSphere Event-Driven Automation using VMware Event Router on VMware Cloud on AWS with Knative or AWS EventBridge
  • Using Terraform to activate Tanzu Kubernetes Grid Service on VMware Cloud on AWS
  • vSphere Event-Driven Automation using Tanzu Application Platform (TAP) on Tanzu Community Edition
  • vSphere Event-Driven Automation using Tanzu Application Platform (TAP) on Tanzu Kubernetes Grid Service
Share this...
  • Twitter
  • Facebook
  • Linkedin
  • Reddit
  • Pinterest

Categories // Home Lab, OVFTool, VMware Cloud on AWS Outposts, vSphere Web Client Tags // vCenter Cloud Gateway, VMware Cloud on AWS

Comments

  1. Daniel Rethmeier says

    10/16/2019 at 7:46 am

    Excellent description! Did work for me in my homelab. However, with VCG 6.8.7, the UI installer isn't working anymore with that modifications, it seems to have the CPU/Mem checks hard-coded. The CLI installation does work.

    Reply
  2. Fabio says

    11/22/2021 at 4:03 am

    great job, in the latest version of vCenterCloudGateway I also had to edit the layout.json file in the folder... ui-installer\win32\resources\app\dist\resources\
    modifying the Medium Layout

    Reply

Thanks for the comment! Cancel reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.

Search

Author

William Lam is a Senior Staff Solution Architect working in the VMware Cloud team within the Cloud Infrastructure Business Group (CIBG) at VMware. He focuses on Cloud Native technologies, Automation, Integration and Operation for the VMware Cloud based Software Defined Datacenters (SDDC)

Privacy & Cookies: This site uses cookies. By continuing to use this website, you agree to their use.
To find out more, including how to control cookies, see here: Cookie Policy

Connect

  • Email
  • GitHub
  • LinkedIn
  • RSS
  • Twitter
  • Vimeo

Support

Recent

  • A first look at the new vSphere+ & vSAN+ Cloud Service 07/01/2022
  • Quick Tip - Prepare VMware Photon OS for use with vSphere Guest OS Customization and cloud-init 06/29/2022
  • Using the new vSphere Guest OS Customization with cloud-init in vSphere 7.0 Update 3 06/27/2022
  • How to forcefully disconnect a vSphere VM Console session? 06/24/2022
  • Quick Tip - Using ESXi Scripted Installation (kickstart) to configure IPv6 networking 06/21/2022

Advertisment

Copyright WilliamLam.com © 2022

 

Loading Comments...