• Skip to primary navigation
  • Skip to main content
  • Skip to primary sidebar

Yellow Bricks

by Duncan Epping

  • Home
  • Unexplored Territory Podcast
  • HA Deepdive
  • ESXTOP
  • Stickers/Shirts
  • Privacy Policy
  • About
  • Show Search
Hide Search

Archives for February 2011

Want a free HA/DRS Technical Deepdive Book?

Duncan Epping · Feb 10, 2011 ·

Want a free HA/DRS Technical Deepdive Book? Watch vChat 15!

In Episode 15 of our vChat series, we have a couple of special guests with us whom I’m sure you would have heard of or if not met before, Frank Denneman and Duncan Epping. These guys embody almost all things deep-dive when it comes to vSphere and with the recent release of their new book VMware HA/DRS Deepdive and we take the opportunity to ask about the background behind the book, whether an electronic version is in the pipeline along with their plans for any future publications. We discuss VMware Partner Exchange (PEX) 2011. Other topics, as you’d imagine, cover the VMware iPad app (and the potential security issues) and their home vSphere labs.

Watch it here!

Storage Performance

Duncan Epping · Feb 3, 2011 ·

This is just a post to make it easier finding these excellent articles/threads on VMTN about measuring storage performance:

  • Scott Drummonds – Storage System Performance Analysis with Iometer
  • VMTN Unofficial Storage Perf Thread I – http://communities.vmware.com/thread/73745
  • VMTN Unofficial Storage Perf Thread II – http://communities.vmware.com/thread/19784

All these have one “requirement”  and that is that Iometer is used.

Another one that I wanted to point out are these excellent scripts that Clinton Kitson created which collects and processes vscsistats data. That by itself is cool, but what is planned for the next update is even cooler. Live plotted 3d graphs. Can’t wait for that one to be released!

Using the vSphere Plan & Design Kit

Duncan Epping · Feb 2, 2011 ·

As part of my role I very often review design documents that other consultants/architect have written, and not only those of VMware employees but also from external people. On top of that of course I also see a lot of VCDX application packages pass by. Something struck me the other day when I was doing the 3rd review in just a couple of hours and I started thinking about the designs I had reviewed so far and noticed there was a common theme.

Before I get started I want to make sure everyone understands that I believe there’s a very strong value to using standardized templates / frameworks. So don’t misinterpreted this article.

I know that many of you are consultants/architects and leverage the Plan & Design kit that VMware PSO created or have an internally developed template that might or might not be based on this P&D Kit. (If your a VMware Partners and wonder what this kit is, log in to the partner portal and look around!) The Plan & Design kit is basically a template, although the hot word these days is framework, that lays out the foundation for a vSphere 4.x design. I guess “framework” or “template” already reveals how it should be used but lately I have been noticing, and yes even VCDX submissions, that people are trying to cut corners and skip sections or use the defaults. I guess by now most of you are thinking “well that doesn’t apply to me”, but lets be honest here when you use the same template for years you start to get lazy. I know I do.

While there is absolutely nothing wrong with using the template and adopting the best practices mentioned in this template, this only goes when they are used in the right context. The framework that VMware for instance provides contains many examples of how you could implement something, and the ones provided are usually the best practice. That doesn’t necessarily mean though that this best practice meets your customer’s requirement or can be used based on the constraints this environment/customer has. Just to give an example of something that I see in 90% of the designs I review:

  • Max amount of VMs per datastore 15
  • Datastore size 500GB
  • Justification: To reduce SCSI reservations

This used to be a best practice and probably a very valid design decision in most cases. However over the last 3 version the locking mechanism has been severely improved. On top of that even more recently VAAI was introduced and the risks were reduced because of that. Along the way the number 15 got bumped up to 20-25, depending on the workload and the RTO. Based on those technology changes your best practice and template should have been updated, or at a minimum explain what the “new” reason is for sticking with these values.

Every single time you write that new design challenge your decisions, go over these best practices and make sure they still apply. Every time a new version of the product is released validate the best practices and standardized design decisions and change them accordingly to benefit from these features.

Calling all virtual appliance vendors!

Duncan Epping · Feb 1, 2011 ·

Lately I have been playing around in my Lab a lot. I tried many virtual appliances as I wanted to use a variety of workloads. I downloaded many appliances and hoped to have all of them up and running in a bare minimum amount of time. Apparently I miscalculated / underestimated the amount of work to get a virtual appliance up and running. Yes of course there are a whole bunch that will work out of the box, and all of these have one thing in common:

OVF

Yes, deploying virtual appliances is a lot easier when they are packaged as an OVF or even an OVA for that matter. Packaging a virtual appliance which is “tarred” and “gzipped” using an old version of VMware Workstation with a sparse disk format doesn’t cut it any more in the age of automation and transportability. Although that works great on the workstation you developed it on it doesn’t really make it easy for your customer to deploy it.

I am not saying this to make my life easier, but I truly believe that the adoption of a standard like OVF will also increase the adoption of your product. Instead of jumping through hoops to get the appliance running people can focus on what it really is about, your product.

It is time to start adopting OVF.

  • « Go to Previous Page
  • Page 1
  • Page 2
  • Page 3

Primary Sidebar

About the Author

Duncan Epping is a Chief Technologist and Distinguished Engineering Architect at Broadcom. Besides writing on Yellow-Bricks, Duncan is the co-author of the vSAN Deep Dive and the vSphere Clustering Deep Dive book series. Duncan is also the host of the Unexplored Territory Podcast.

Follow Us

  • X
  • Spotify
  • RSS Feed
  • LinkedIn

Recommended Book(s)

Also visit!

For the Dutch-speaking audience, make sure to visit RunNerd.nl to follow my running adventure, read shoe/gear/race reviews, and more!

Do you like Hardcore-Punk music? Follow my Spotify Playlist!

Do you like 80s music? I got you covered!

Copyright Yellow-Bricks.com © 2026 · Log in