Contribute: Tweet sized vSphere Design Considerations

Most of you have probably seen the announcement Frank did yesterday… Frank, Cormac, Vaughn and I are working on this book project called “Tweet sized vSphere Design Considerations” and we need YOU, the community, to contribute! What are you saying? You are writing a book and want us to do the work for you? Yes indeed, but this book belongs to all of us! As Frank stated:

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.

So how does it work, let me briefly recap Frank’s blog post, what are the rules:

• Each design consideration should be tweet-sized like, maximum of 200 characters (excluding spaces)
• Should fit in on one the following categories:
  • Host design
  • vCenter design
  • Cluster design
  • Networking and Security design
  • Storage design
• Max 3 submissions per category per person

So what would that look like? I know some folks have already submitted entries, but for those who are considering and don’t know where to start or are not certain of what they are thinking about will meet the requirements here are two examples of what I submitted:

1. For your “Management Network” portgroup ensure to combine different physical NICs connected to different physical switches. This will increase resiliency and decrease chances of an HA false positive.
2. Ensure syslog is correctly configured for your virtual infrastructure and log files are offloaded to a safe location outside of your virtual infrastructure. This will allow for root cause analysis in case disaster strikes.

So head-over to Frank’s blog, read the rules a couple of times and start entering those design considerations! You might end-up in this cool book, if you do you will get a free paper copy provided by PernixData. It will also be made available to everyone for free through the various channels as an ebook.