Frequently Asked Questions (FAQ) - Developer Ready Infrastructure
- How is this different from the Architecture, Design and Implementation of vSphere with Tanzu Workload Domain release under VMware Validated Designs?
The Developer Ready Infrastructure for VMware Cloud Foundation validated solution does not provide design or implementation guidance relating to the Virtual Infrastructure (VI) Workload Domain implemented by VMware Cloud Foundation – it focuses on the design, implementation and operational processes for expanding a functional VI Workload Domain to support vSphere with Tanzu.
The validated solutions includes:
- Infrastructure-as-code using a purpose built Microsoft PowerShell module to automate implementation tasks. Previous documentation required manual implementation steps.
- Guidance for scaling vSphere with Tanzu within a single Supervisor Cluster and within a VI Workload Domain.
- Additional guidance and links to resources for backup and recovery using Velero.
- Three sample application blueprints you can use to start deploying Kubernetes applications both in the Supervisor Cluster and into a Tanzu Kubernetes cluster deployed by Tanzu Kubernetes Grid Service.
- Which architecture model for VMware Cloud Foundation is used in the solution?
The solution is optimized for the standard architecture model with VMware Cloud Foundation instances consisting of a management domain and one or more workload domains.
There are no known technical blockers to using this solution in the consolidated architecture, however you should consider the following:
- This combination is not explicitly tested by the VMware Validated Solution team
- While the Planning & Preparation workbook will display the management domain values instead of the workload domain values, but there may be nuances where the process slightly differs in the management domain vs the workload domain.
- You should ensure Management Domain performance is not effected by leveraging resource pools and by regular monitoring of resource consumption.
- Must I follow the naming and IP addressing format mentioned within the VMware Validated Solution?
No. Customers should utilize the VMware Cloud Foundation Planning and Preparation Workbook to capture their own naming and IP addressing requirements and then use the workbook when following the implementation procedures.
- Can I build on top of this with Tanzu Standard/Advanced/Enterprise?
This solution is loosely coupled with Tanzu Basic, but you may build on top of it using any of the tooling included with other Tanzu license bundles.
- Must I use Microsoft Active Directory users and groups for Role Based Access Control? Can I just use vsphere.local users in vCenter Single Sign On?
To deploy a compliant solution, you must use Active Directory users/groups for Role Based Access Control (RBAC). That said, vCenter SSO users will work fine. You should use an enterprise solution for access control to ensure auditability of logins and actions performed.
- Does the VMware Validated Solution provide any automation of initial deployment or on-going tasks?
Yes. The solution includes the optional use of Microsoft PowerShell module to perform many of the deployment and configuration procedures. The PowerValidatedSolutions PowerShell module must be installed from the PowerShell Gallery along with some supporting modules. The subsequent procedure options will set the minimally required variables and automate the procedure.
- Must I use the PowerValidatedSolutions PowerShell module to perform the installation and configuration procedures?
No. Each VMware Validated Solution provides manual implementation steps. The use of the PowerValidatedSolutions PowerShell module is completely optional.
Where can I find more resources related to the Developer Ready Infrastructure for VMware Cloud Foundation validated solution?
All resources are available at https://core.vmware.com/developer-ready-infrastructure-vmware-cloud-foundation