Today I am excited to announce our (Duncan and I) newest project. Over the next 7 days we will be gathering the best vSphere design considerations around and compiling it into a pocket-sized book. The current working title is “Tweet-sized vSphere design considerations”. As this book is created by people from the virtualization community for the virtualization community, this book will be available free of cost.
vSphere Design Considerations
In the vSphere clustering deepdive series we emphasized certain design consideration by calling them out in “Basic design principles” textboxes. Basic design principles provide quick and simple as well as deep and quintessential information to make architectural design decisions.
The technical deepdive books and their basic design principles focus on HA and distributed resource management features but there are a lot of basic design principles for the other elements in a virtual infrastructure.
We approached some of the industry leading minds to contribute their design considerations for various elements of the virtual infrastructure. However we believe that a lot of practitioners in the virtualization community can contribute to make the book a real success.
Time to gather and aggregate them into one single book that can become a pocketbook of inspiration for all virtual infrastructure architects, admins and consultants.
Call for entries
Do you have a design consideration that consistently apply in your customer environment? Here is your chance to share it with the rest of the virtualization community. If your design consideration is selected it will be featured in the book. Your name, title (vExpert, VCDX number) and twitter handle will be listed along your design consideration.
Each design consideration should be tweet-sized like. 140 characters might be a challenge, therefor we slight adjusted the limitation and we allow a maximum of 200 characters (excluding spaces).
We are looking for design consideration in the following categories:
- Host design
- Cluster design
- vCenter design
- Networking and Security design
- Storage design
To prevent oversaturation we do not allow more than a total of three design considerations per category. For example, you can provide us with three design considerations for the Host category but you could also choose to provide a single design consideration for each category. It’s up to you to decide which category and how many you want to provide. Be aware that we rather see one excellent design consideration than three mediocre ones.
Level of Quality
There are no requirements for submitting your design decision. You do not have to be a vExpert or VCDX to participate. However we strive to have a consistent level of quality of design considerations featured in the book. Please check out the “basic design principles” in one of the vSphere clustering Deepdive books, these are the level of quality we are looking for.
The selection process
Both Duncan and I encourage simplicity. Simplicity in design usually removes as much overhead as possible, which in turn increases flexibility. To quote Martin Fowler “The cost of flexibility is complexity” and in today’s cloud focused market flexibility is key. Be mindful of that.
Therefore try to aim for simplicity in both design and messaging. Similar to the architectural design try to simplify your message as much as possible. This does not mean that you are requested to dumb down your message. Use clear, clean communication, so that it could not be misunderstood.
The following five bloggers will judge the submitted entries:
- Frank Denneman
- Duncan Epping
- Cormac Hogan
- Jason Nash
- Vaughn Stewart
- Announcement and Call for Entries (Today)
- Deadline for Call for Entries (June, 18st)
- Deadline selection design considerations by judges (June 30th)
- Book design and print process
- Book Availability (VMworld 2013)
Once the book is complete we shall publicize the list of people mentioned in the book, we will not share information during the production process of the book.
This book is free!
PernixData generously offered to print the book. If your design consideration is included in the book, you will receive a copy of the book. At their booth at VMworld PernixData will have a copy available for people who submitted a winning design consideration. A limited number of books will be available for the community. More details will follow. After VMworld an E-book version of the book will be made publicly available.
Please note, the deadline for call for entries will close at Tuesday 18th June.