Sample VCDX-DCV Architecture Outline

This post covers my approach to writing my VCDX-DCV Architecture Guide. I’ve been debating in my mind for a while whether I should write this post or not. I hesitated for a few reasons. First, I’m just a regular guy that happened to jump through the VCDX hoops and have no “insider” information on how they score. Those that do know the scoring rubric can’t disclose it anyway. Second, there are 1000 different ways to write your VCDX-DCV architecture document. Third, there’s no “magic template” or “sure fire” outline that ensures your design gets accepted. Do not view this post as shortcut or cheat sheet.

What matters is your content, how it aligns to the VCDX blueprint, and that you convey expert level knowledge to the reader. It’s NOT about speeds and feeds, but rather the full traceability of customer requirements, constraints,  assumptions and risks throughout your design. Who cares if you’ve thrown every VMware product and feature at a solution if you haven’t met the business requirements? #Fail

So why did I publish this article? I know when I started the VCDX process it was a bit daunting to read the DCV blueprint and try to come up with an architecture guide that hit all the areas in a logical manner. I’ve heard from other candidates they experienced the same “VCDX writer’s block.” In fact several of us have scrapped our first attempts, and started over. Bottom line is you need to do what feels right to YOU, and what works for YOUR design while covering all the blueprint areas. You may not like my methodology or outline, which is perfectly fine and a valid way to feel.

I’ve also heard comments from VMware customers (like myself when I went through the process) that think since they aren’t a partner and don’t have access to the VMware SET templates that they are at a disadvantage. That’s not true,  IMHO. Yes the VMware SET docs are structured and may help you, but they aren’t directly aligned to the VCDX blueprint and need augmentation.

With all those caveats, I wanted to share my DCV architecture guide outline. Maybe it will help someone with writer’s block, or enable you to see some the areas that a VCDX design could cover. Your design may need additional areas, or less coverage. This is certainly not all inclusive, and it’s guaranteed your outline will be different. It is your responsibility to ensure your documents cover all blueprint areas, makes sense for your design, and something you feel comfortable with. Own your documentation.

Before I go any further, let me state that how I chose to incorporate the specific VCDX bootcamp book recommendations is somewhat unique to my style. Of the submissions I’ve seen none did it exactly this way, which proves that there is no “magic” template or style for VCDX submissions. I just felt it gave a better overall flow to the document.

You will see some common sub-sections in all design areas (e.g. cluster, storage, compute, etc.). For example, in most areas I had specific conceptual, logical and physical sections. This helped me show the traceability of customer input through the entire design process. Each major section also concludes with a Design Justification which is a summary of how I met the customer requirements and sites all of the applicable requirements, assumptions, constraints, and risks.

At the end of the Design Justification section I had two tables to help distill down the critical information. First, I had a summary table, shown below. All of the design quality items (e.g. C02) were referenced elsewhere in that section as applicable. Possibly overkill, but I liked the compact summary.

2014-10-06_17-38-00

The second table was that of the applicable design decisions, each with the decision, impact, decision risks (after all, nearly every decision has a risk), and risk mitigation. A sample design decision is below.

2014-10-06_17-49-53

WordPress was not cooperating with me for a clean outline format, so I’ve inserted a series of screen captures to maintain formatting.

Sample VCDX-DCV Architecture Outline

2014-10-06_16-48-18

2014-10-06_16-50-08  2014-10-06_16-52-34

2014-10-06_16-53-59

2014-10-08_8-39-36
2014-10-06_16-59-52

Print Friendly, PDF & Email
(Visited 1 times, 1 visits today)

6
Leave a Reply

avatar
4 Comment threads
2 Thread replies
0 Followers
 
Most reacted comment
Hottest comment thread
4 Comment authors
scott@nvermandeShaneVaseem Mohammed Recent comment authors
  Subscribe  
newest oldest most voted
Notify of
Vaseem Mohammed
Guest
Vaseem Mohammed

Wow! I am still at the very begning of journy in vmware, that architecture outline, after going to each bullet point, I am like 'get me one joint please'.
I am studying for VCAP and long long way to go and gain experience.

Shane
Guest
Shane

Derek. I like your layout. When I did my submission (VCDX #95), I also found it challenging to work out how to tie design decisions back to business requirements. I used one main table at the beginning of the document outlining each requirement, with references pointing to the relevant sections throughout the design that outline how that requirement was met. Each relevant section also had references that tied it back to the main table. Two ways of doing it. Both obviously met the requirements. Well done on your successful achievement, by the way.

@nvermande
Guest

Hi mate! I personally think this is just too much. VCDX application/design shouldn't include "everything you can think about" within the DC. This is supposed to be real life deliverables and most of the customers (except government) won't require that level of documentation. Remember to get your VCDX you just have to do what is required to pass, not more, not less. My DCV design was 100 pages and I passed, My NV design was 70 and I passed too. You're just freaking everyone out with this outline IMHO 🙂

scott
Guest
scott

I would love to read one of these full documents once. I keep just seeing the outlines.