Hello,
I'm trying to model a diagram of an EDW and just the hardware related to it. I'm not including development environments or any networking configurations, just databases, test servers, SAN and application servers. Does anyone know of a best practice on creating server implementation diagrams and to what extent should that show dynamic load balancing and all of the virtualized controllers and load balancers? My audience for this diagram is developers - to be aware of what environment they are working in or to quickly find what services will be affected if a server goes down.

If the developers need blade data, then you need to show it in your diagram. If they need subsystem or thunk data only, then you don't need physical details.

-PatP