The Operational Verification documentation provides step-by-step instructions for verifying that the management components in Region A in the Software-Defined Data Center (SDDC), deployed according to the VMware Validated Design for Software-Defined Data Center, are operating as expected.
Operational verification is defined as a validation that a system or a component is operational and functioning within expected parameters. Operational verification is performed in the following scenarios:
- Initial deployment of a component or system
- Upgrading or patching of a component or system
- Generic maintenance of a component or system
The Operational Verification documentation is intended for cloud architects, infrastructure administrators, cloud administrators, and cloud operators who are familiar with and want to use VMware software to manage an SDDC that meets the requirements for capacity, scalability, backup and restore.
Supported VMware Cloud Foundation Version
VMware Validated Design Operational Verification is compatible with VMware Cloud Foundation™ 4.2.
Required VMware Software on VMware Cloud Foundation
Operational Verification is compliant and validated with certain VMware Workspace ONE Access and vRealize Suite product versions on VMware Cloud Foundation. See VMware Validated Design Release Notes.
Before You Apply This Guidance
You apply the instructions in Operational Verification on an environment with a certain configuration. Following the prescriptive path of VMware Validated Design, you deploy the virtual infrastructure of the management domain and workload domains by using VMware Cloud Foundation, then manually adding a region-specific Workspace ONE® Access™ instance for central user management in VMware NSX-T® Data Center. Then, you use vRealize Suite® Lifecycle Manager™ in VMware Cloud Foundation mode to deploy the vRealize Suite components. For information on the deployment workflow of the SDDC components, see Deployment of VMware Validated Design in Introducing VMware Validated Design.
VMware Validated Design follows an example naming convention. The naming provides uniqueness of the objects across the SDDC. You can identify managed objects directly if you use many components that are linked together, for example, multiple vCenter Server systems working in Enhanced Linking Mode or management dashboards in vRealize Operations Manager monitoring multiple instances of the same component. For information on the naming convention, see Planning and Preparation Workbook.
|Domain||Management Component||Deployment Method|
|Management domain||VMware ESXi™ hosts||Manual deployment|
|VMware vCenter Server®||Automated deployment by using Cloud Builder|
|NSX-T Manager and NSX-T Edge nodes with a region-specific and cross-region virtual network segments||Automated deployment by using Cloud Builder|
|VMware vSAN™ as principal storage||Automated deployment by using Cloud Builder|
|NFS as supplemental storage||Manual deployment|
|VMware Cloud Foundation® SDDC Manager™||Automated deployment by using Cloud Builder|
|Region-specific Workspace ONE Access instance connected to NSX-T and vRealize Log Insight||Manual deployment|
|vRealize Suite Lifecycle Manager in VMware Cloud Foundation mode||Automated deployment by using SDDC Manager|
|Cross-region Workspace ONE Access instance connected to vRealize Operations Manager, vRealize Log Insight, and vRealize Automation||Automated deployment by using vRealize Suite Lifecycle Manager in VMware Cloud Foundation mode|
|VMware vRealize® Operations Manager™||Automated deployment by using vRealize Suite Lifecycle Manager in VMware Cloud Foundation mode|
|VMware vRealize® Log Insight™||Automated deployment by using vRealize Suite Lifecycle Manager in VMware Cloud Foundation mode|
|VMware vRealize® Automation™||Automated deployment by using vRealize Suite Lifecycle Manager in VMware Cloud Foundation mode|
|Virtual infrastructure workload domain or vSphere with Tanzu workload domain||ESXi hosts||Manual deployment|
|vCenter Server||Automated deployment by using SDDC Manager|
|NSX-T Manager and NSX-T Edge nodes||Automated deployment by using SDDC Manager|
|Principal storage||Automated deployment by using SDDC Manager|
|Supplemental storage||Manual deployment|
|vSphere with Tanzu workload domain||Kubernetes control plane node||Validation by using SDDC Manager and manual deployment|
|Tanzu Kubernetes cluster control plane node||Manual deployment|
|Tanzu Kubernetes cluster control worker node||Manual deployment|
To use this document, you must be acquainted with the following guidance:
- Introducing VMware Validated Designs
- Optionally, the following architecture and design documentation:
- Architecture and Design for the Management Domain
- Architecture and Design for a Virtual Infrastructure Workload Domain or Architecture and Design for a vSphere with Tanzu Workload Domain
- Architecture and Design for Cloud Operations and Automation
- Planning and Preparation Workbook
- Deployment of the Management Domain in the First Region
- Deployment of a Virtual Infrastructure Workload Domain in the First Region or Deployment of a vSphere with Tanzu Workload Domain in the First Region
- Deployment of Cloud Operations and Automation in the First Region
The same requirement applies if you are following the VMware Cloud Foundation documentation to deploy the operations and automation solutions. See the VMware Cloud Foundation documentation.