You must meet the hardware, software, and other requirements listed in this section before you can start the Delivery and Acceptance (DA) process.
The Delivery and Acceptance process verifies that all VMware and custom partner pipelines run successfully against the servers to be used for the program. There are two stages as part of this process, Stage-1 and Stage-2.
The requirements listed below are the minimum requirements which you must provide to enable VMware to complete the 2 stage process for the VCPS program.
Requirement | Details | Notes |
---|---|---|
2 VMs (per stage) |
|
|
External Services |
|
|
Network Underlay |
The SDDC deployed during Delivery and Acceptance must be deployed on a network underlay that meets the following requirements:
|
Additional VMware services can require additional VLANs. |
8 ESXi Hosts | The ESXi hosts are the subject of the Delivery and Acceptance (DA) process. The pipelines will execute against these hosts. Within a cluster, the hosts must have identical hardware profiles. See the vSAN documentation for the minimum configuration that is required for the vSAN ready nodes.
Note: If a provider has multiple server hardware bill of materials (BOM), Stage-1 and Stage-2 processes must be run against each server models in the fleet for delivery and acceptance.
|
ESXi hosts have to be provided as a "configuration target" for the Stage-1 and Stage 2 VMs.
Note:
The minimum requirement for validation is 8 ESXi hosts. With this minimum, Stage-1 and Stage-2 share the same hosts but run independently in a serial fashion with a host cleanup run between stages. |
SDDC Input Spec File | The spec file must contain the information about the following:
|
The spec file is used to make a REST API call to the LCM Controller Service to initiate bring-up and to certify the test environment. See the JSON Specification file for an example. |
Golden Repository |
|
|
Pipelines or Binaries | If you create any pipelines or binaries, you must maintain it in your source control systems and are responsible to populate them into the provisioning VM. |