All Posts

Hello everybody, Can we use these document to build a vCloud Diretor for SP solution ? I can read terms like AZ and region but no mention about vCloud Director for SP product. Best rega... See more...
Hello everybody, Can we use these document to build a vCloud Diretor for SP solution ? I can read terms like AZ and region but no mention about vCloud Director for SP product. Best regards
Another addition, using this model provides the following benefits: 1. Isolation of management and compute vCenter Server operations 2. Simplified capacity planning 3. Separated upgrade 4. Se... See more...
Another addition, using this model provides the following benefits: 1. Isolation of management and compute vCenter Server operations 2. Simplified capacity planning 3. Separated upgrade 4. Separated roles
Hi SK84, that was what i thought about the scalability and the impact of a vCenter failure. Thank you for your confirmation.
Is it a must to have 2 vCenter? What is the reason? Nothing in this document is a must. It is a guide for the best way to build a SDDC. It's therefore more an advisory or collection of best p... See more...
Is it a must to have 2 vCenter? What is the reason? Nothing in this document is a must. It is a guide for the best way to build a SDDC. It's therefore more an advisory or collection of best practices. However, VMware can guarantee that your SDDC stack will deliver the best possible performance, availability and scalability if you follow this architecture and design document. The reasons for 2 vCenters (one for management and one for compute) are availability and scalability. vCenter has limitations on the maximum virtual network ports available or a maximum for VMs it can manage, for example (and some more). And even if the management cluster fails, the impact on the productive virtual machines is less.
Hi everybody. In the Architecture and Design document for SDDC, the SDDC logical design for Single Availability Zone scheme shows 2 vCenters, one for the Management and the other for the Compute... See more...
Hi everybody. In the Architecture and Design document for SDDC, the SDDC logical design for Single Availability Zone scheme shows 2 vCenters, one for the Management and the other for the Compute. Is it a must to have 2 vCenter? What is the reason? Does it depend on the infrastructure components installed (for example if NSX is not used, do we have to have 2 vCenter)? In advance thank you for your answer. Philippe.
VMware Validated Design for Management and Workload Consolidation 4.3 Design Decision Checklist This document provides all 268 decisions in the VMware Validated Design for Management and Work... See more...
VMware Validated Design for Management and Workload Consolidation 4.3 Design Decision Checklist This document provides all 268 decisions in the VMware Validated Design for Management and Workload Consolidation 4.3 Architecture and Design into a simple spreadsheet for quick reference. It includes columns for determining your level of adherence to the architecture and any justification for deviations.       
VMware Validated Design for Software-Defined Data Center (VVD for SDDC) 4.3 Architecture Reference Poster. Update to reflect updates incorporated in the 4.3 release.
VMware Validated Design for SDDC 4.3 Design Decision Checklist Updated 17 July 2018 This document provides you all 375+ design decisions in the VMware Validated Design for Software Defined ... See more...
VMware Validated Design for SDDC 4.3 Design Decision Checklist Updated 17 July 2018 This document provides you all 375+ design decisions in the VMware Validated Design for Software Defined Data Center 4.3 Architecture and Design into simple spreadsheet for quick reference. It includes columns for determining your level of adherence to the architecture and any justification for deviations.
Hi mabrown76​, Just reading through and noticed that Table 2-3 Jumbo Frames Design Decisions mentions that Geneve overlay required an MTU value of 1600 bytes or greater. Then later in the do... See more...
Hi mabrown76​, Just reading through and noticed that Table 2-3 Jumbo Frames Design Decisions mentions that Geneve overlay required an MTU value of 1600 bytes or greater. Then later in the document under Table 2-16 Geneve Overlay Design Decisions & in the NSX-T - Physical Network Requirements sections it mentions that MTU size of 1700 or greater. Pretty sure it should be a consistent minimum of 1700 or greater. Regards, Scott Holliday
Thanks! The VVD requires NSX-V in the management cluster. It's not an NSX-T requirement but a VVD one. Mike
Hey Mike, great work! I was wondering though why figure 1-4 shows an NSX-V prepared management cluster? It looks like NSX-V is a requirement for an NSX-T VVD, while surely it is not?
mabrown76 converted the discussion to document for easier tracking and update (revision control and history)
As many of you may know, we opened this Early Access sub-community to provide you an opportunity to download and discuss pre-released design materials for the VMware Validated Designs. We want yo... See more...
As many of you may know, we opened this Early Access sub-community to provide you an opportunity to download and discuss pre-released design materials for the VMware Validated Designs. We want you discover the latest content for blueprints that are in development and learn about the direction of the next generation architectures. Today I get to announce the fruits of the past few months of my labor, NSX-T in a Workload Domain. This early access design covers the architecture and design elements for adding NSX-T to a  VMware Validated Design workload domain. Got feedback? We want to hear from you. So dive into this latest early access content and share your feedback directly with our architects and product managers! This document was generated from the following discussion: Early Access: VMware Validated Design for NSX-T in a Workload Domain
As many of you may know, we opened this Early Access sub-community to provide you an opportunity to download and discuss pre-released design materials for the VMware Validated Designs. We want yo... See more...
As many of you may know, we opened this Early Access sub-community to provide you an opportunity to download and discuss pre-released design materials for the VMware Validated Designs. We want you discover the latest content for blueprints that are in development and learn about the direction of the next generation architectures. Today I get to announce the fruits of the past few months of my labor, NSX-T in a Workload Domain. This early access design covers the architecture and design elements for adding NSX-T to a  VMware Validated Design workload domain. Got feedback? We want to hear from you. So dive into this latest early access content and share your feedback directly with our architects and product managers!
Updated: 09 May 2018 This document provides all 246 decisions in the VMware Validated Design for Management and Workload Consolidation 4.2 Architecture and Design into a simple spreadsheet for... See more...
Updated: 09 May 2018 This document provides all 246 decisions in the VMware Validated Design for Management and Workload Consolidation 4.2 Architecture and Design into a simple spreadsheet for quick reference. It includes columns for determining your level of adherence to the architecture and any justification for deviations.
It is my pleasure to share the updated architecture reference poster for the VMware Validated Design for Software-Defined Data Center 4.2. This poster depicts many portions of the fundamental ... See more...
It is my pleasure to share the updated architecture reference poster for the VMware Validated Design for Software-Defined Data Center 4.2. This poster depicts many portions of the fundamental architecture for both quick reference and discussion. The poster has six major sections. Logical Components Architecture – This section illustrates the logical architecture and the how the solutions are deployed and integrated across a full-stack, dual-region Software-Defined Data Center. From vCenter Servers and load-balanced Platform Services Controllers to cross-region and cross-vCenter NSX, through cloud operations and automation with the vRealize Suite, this section touches it all. Core and Domain Architecture – This section illustrates the concent of Workload Domains used in the design and how they are constructed and deployed to provide a common set of scalable building blocks for your Software-Defined Data Center. Distributed Logical Networking and Application Virtual Networks – This section illustrates the design’s use of distributed logical routing across a dual-region Software-Defined Data Center by incorporating VMware NSX into the management stack. It also depicts the deployment of the full-stack of SDDC solutions with Application Virtual Networks and network services provided by NSX. Storage – This section illustrates the use of vSAN and NFS in the design. VMware Validated Designs are designed and tested with VMware vSAN in the management & shared edge and compute domains for primary storage and NFS for secondary storage (templates, archives, and backups.) Workload Domains – This section illustrates, at a high-level, how the network works inside the workload domains. Region Protection and Disaster Recovery – This section illustrates how the design protects vRealize Automation, vRealize Orchestrator, vRealize Operations, and vRealize Business for Cloud using Site Recovery Manager along with NSX. If you’d like to print the poster and hang it on your office wall, the PDF size is 51in x 31in. Let us know if you have any questions or have feedback by posting comments in here in the community. For more information on VMware Validated Design for SDDC 4.2: VMware Validated Design for SDDC 4.2 Release Notes What’s New in the VMware Validated Design for SDDC 4.2 Blog Read the documentation at vmware.com/go/vvd-docs This document was generated from the following discussion: VMware Validated Design for SDDC 4.2 Architecture Reference Poster
It is my pleasure to share the updated architecture reference poster for the VMware Validated Design for Software-Defined Data Center 4.2. This poster depicts many portions of the fundamental ... See more...
It is my pleasure to share the updated architecture reference poster for the VMware Validated Design for Software-Defined Data Center 4.2. This poster depicts many portions of the fundamental architecture for both quick reference and discussion. The poster has six major sections. Logical Components Architecture – This section illustrates the logical architecture and the how the solutions are deployed and integrated across a full-stack, dual-region Software-Defined Data Center. From vCenter Servers and load-balanced Platform Services Controllers to cross-region and cross-vCenter NSX, through cloud operations and automation with the vRealize Suite, this section touches it all. Core and Domain Architecture – This section illustrates the concent of Workload Domains used in the design and how they are constructed and deployed to provide a common set of scalable building blocks for your Software-Defined Data Center. Distributed Logical Networking and Application Virtual Networks – This section illustrates the design’s use of distributed logical routing across a dual-region Software-Defined Data Center by incorporating VMware NSX into the management stack. It also depicts the deployment of the full-stack of SDDC solutions with Application Virtual Networks and network services provided by NSX. Storage – This section illustrates the use of vSAN and NFS in the design. VMware Validated Designs are designed and tested with VMware vSAN in the management & shared edge and compute domains for primary storage and NFS for secondary storage (templates, archives, and backups.) Workload Domains – This section illustrates, at a high-level, how the network works inside the workload domains. Region Protection and Disaster Recovery – This section illustrates how the design protects vRealize Automation, vRealize Orchestrator, vRealize Operations, and vRealize Business for Cloud using Site Recovery Manager along with NSX. If you’d like to print the poster and hang it on your office wall, the PDF size is 51in x 31in. Let us know if you have any questions or have feedback by posting comments in here in the community. For more information on VMware Validated Design for SDDC 4.2: VMware Validated Design for SDDC 4.2 Release Notes What’s New in the VMware Validated Design for SDDC 4.2 Blog Read the documentation at vmware.com/go/vvd-docs
Gary, I like the concept of the spreadsheet.  I'm just starting research on this and wondering how the Decision ID numbers correspond to the document.  Think I'm probably missing something obviou... See more...
Gary, I like the concept of the spreadsheet.  I'm just starting research on this and wondering how the Decision ID numbers correspond to the document.  Think I'm probably missing something obvious.  Thanks  Mike
Unfortunately we can not publically comment or share our roadmap in a public forum. However, please consider periodically checking with the early access sub-community for early access designs. We... See more...
Unfortunately we can not publically comment or share our roadmap in a public forum. However, please consider periodically checking with the early access sub-community for early access designs. We continue to publish new designs under consideration there as we did for the consolidated design and the streched cluster / AZ design.
Latest VMware Validated Design 4.2 SDDC do not support NSX-T. For more information, see https://docs.vmware.com/en/VMware-Validated-Design/4.2/rn/vmware-validated-design-42-release-notes.html