The first post in the series went over the design goals and the logical diagram of the Kubernetes environment. This […]
The first post in the series went over the design goals and the logical diagram of the Kubernetes environment. This […]
In an effort to get caught-up with the Cloud Native space, I am embarking on an effort to build a […]
I had the opportunity to attend the CoreOS Fest 2017 in San Francisco for a day this past week. There […]
In preparing for my recent VCDX Defense, I read a great deal of articles and a few books to better understand how to properly document and justify the design decisions I was making. One book in particular provided valuable insight that has helped me not just with the VCDX certification, but also in becoming a better Infrastructure Architect.
In this blog post, I will cover the approach taken when preparing my VCDX documentation with regards to providing insight and justifications for the design decisions made within my VMware Integrated OpenStack architecture.
During the process of writing the documentation necessary for the VCDX certification, I read several books and a fair number of blog articles. One article in particular that I found helpful was from Derek Seaman’s blog.
In the spirit of paying it forward, I am going to share my own table of contents for others to use as a starting point. No two will be the same and some of the things I included may not be necessary in your own design — you may even feel there are sections that are missing from my own. If nothing else, I hope it can be a starting point for you in the journey towards earning the VCDX certification.