mirror of
https://github.com/openshift/openshift-docs.git
synced 2026-02-05 12:46:18 +01:00
27 lines
1.6 KiB
Plaintext
27 lines
1.6 KiB
Plaintext
// Module included in the following assemblies:
|
|
//
|
|
// * installing/installing_vmc/installing-restricted-networks-vmc.adoc
|
|
// * installing/installing_vmc/installing-restricted-network-vmc-user-infra.adoc
|
|
// * installing/installing_vmc/installing-vmc-customizations.adoc
|
|
// * installing/installing_vmc/installing-vmc-network-customizations.adoc
|
|
// * installing/installing_vmc/installing-vmc-network-customizations-user-infra.adoc
|
|
// * installing/installing_vmc/installing-vmc-user-infra.adoc
|
|
// * installing/installing_vmc/installing-vmc.adoc
|
|
|
|
[id="vmc-sizer-tool_{context}"]
|
|
= VMC Sizer tool
|
|
|
|
VMware Cloud on AWS is built on top of AWS bare metal infrastructure; this is the same bare metal infrastructure which runs AWS native services. When a VMware cloud on AWS software-defined data center (SDDC) is deployed, you consume these physical server nodes and run the VMware ESXi hypervisor in a single tenant fashion. This means the physical infrastructure is not accessible to anyone else using VMC. It is important to consider how many physical hosts you will need to host your virtual infrastructure.
|
|
|
|
To determine this, VMware provides the link:https://vmc.vmware.com/sizer/quick-sizing[VMC on AWS Sizer]. With this tool, you can define the resources you intend to host on VMC:
|
|
|
|
* Types of workloads
|
|
* Total number of virtual machines
|
|
* Specification information such as:
|
|
** Storage requirements
|
|
** vCPUs
|
|
** vRAM
|
|
** Overcommit ratios
|
|
|
|
With these details, the sizer tool can generate a report, based on VMware best practices, and recommend your cluster configuration and the number of hosts you will need.
|