OK, I promised, so here we go! The other seven parts of this series have all dealt with the technical aspects of vSwitches, pNICs, Port Groups and such. This part will deal with the more mundane aspect of naming standards. While maybe not as glamorous, this is definitely one of the most important aspects of building your virtual infrastructure. Oh, by the way, the names I used in this series of article (i.e. PG_APP1, PG_VMotion, etc.) are really bad names for a production environment!
A naming standard is exactly what the title sounds like – a standard for defining the names of things. In my opinion, a naming standard should achieve a couple things:
- Provide a simple, consistent method for assigning names to objects – there is nothing “arbitrary” about a naming standard
- Be flexible enough to accommodate most, if not all, use cases
- Provide an effective means for all parties involved to understand what is being described