Virtual Servers - gotta love 'em, gotta hate 'em.

If you ever have to support a large number of dev and test servers in your IT environment and have found yourself frustrated with the administrative and technical overhead, a virtual machine architecture *might *be for you. It's all the rage these days, but (trust me on this one, I should know) there's lots of ways to de-optimize (read: screw up) a virtual machine/server environment. To make it work effectively, there are a few things that you need to know and do to make your environment hum like a well-oiled (virtual) machine.

The problem is, until recently there has been relatively little prescriptive architecture for using virtual environments for specific test environments. In the case of Microsoft Virtual Server, there is now a reference architecture and detailed documentation that you can take advantage of by just downloading the documents:

Windows Server System Reference Architecture Virtual Environments for Development and Test* (WSSRA-VE) can help large organizations and enterprises create environments for development and testing that emulate their own production environments. The guidance describes the architectural blueprint, planning considerations, deployment practices, and operational considerations for creating and supporting a virtualized instantiation of the Windows Server System Reference Architecture. It leverages the power of Virtual Server 2005 and automated deployment and configuration tools to minimize the physical infrastructure and logistical overhead necessary to deploy emulations of various data center services. *

Like WSSRA itself, the WSSRA-VE is intended to aid users in their own effort to model their operational environment and condense it to a scale that can be representative of the infrastructure integration challenges facing developers and testers of distributed, message-based applications and IT services, and still be inexpensive and relatively economical to build and use throughout a large-scale IT organization.