Visual Studio Lab Management 2010 enables teams to accelerate setup/tear down and restoration of complex virtual environments to a known state for test execution and build automation. It extends build automation by automating virtual machine provisioning, build deployment and build verification in an integrated manner. It also allows testers to file rich bugs with links to environment checkpoints that developers can use to recreate complex environments, effectively reducing wasted time and resources in your development and test lifecycle.
A week ago at my main customer SD Worx in Antwerp, I managed to install a full-blown Team Foundation Server 2010 (RC), including Visual Studio Lab Management (RC) in an isolated environment.
I really got spoilt and got two physical servers at my disposal with each 20GB of RAM. This is the current configuration:
- Physical Server 1 (Windows Server 2008 R2 with Hyper-V):
- TFS2010AT_A: Application Tier TFS2010 (Windows Server 2008 R2 – 4GB RAM)
- TFS2010AT_B: Application Tier TFS2010 (Windows Server 2008 R2 – 4GB RAM)
- TFS2010DT: Data Tier TFS2010 (Windows Server 2008 R2 – 4GB RAM)
- Physical Server 2 (Windows Server 2008 R2 with Hyper-V):
- VS2010: Client with VS2010 Ultimate (Windows XP Pro with SP3 – 3GB RAM)
- TFSBUILD2010_A: Build Server (Windows Server 2008 R2 – 2GB RAM)
- TFSBUILD2010_B: Build Server (Windows Server 2008 R2 – 2GB RAM)
- TESTVM: Virtual Environment for testing Lab Management (Windows Server 2008 R2 – 2GB RAM)
Note that the Team Foundation Server 2010 is setup with Network Load Balancing (NLB) for TFS services. I also should setup NLB for Reporting Services and WSS on both AT servers. SQL Reporting Services is installed on the application tier while SQL Analysis Services is installed on the data tier. One Team Project Collection is created with one MSF Agile Team Project. A Build Controller for the Team Project Collection is setup on Build Server A that manages a Build Agent on Build Server A and another Build Agent on Build Server B.
The second physical server will also serve as the HyperVHost machine, the VmmMachine and LibraryMachine for Visual Studio Lab Management.
This setup should give the opportunity for a small workgroup to further test the benefits of the entire Team Foundation Server 2010 environment. In total I must have spent about 4 days in installing and configuring this setup. I did follow the guidelines on the Visual Studio Lab Management Blog where the team posted a series on Getting Started with Lab Management.
I was really happy with the fact that the installation/configuration of System Center Virtual Machine Manager and the other more IT Pro related stuff was pretty straightforward. More information on Lab Management can also be found at MSDN.
Next step is to schedule some internal workshops with the team to kick-off all the testing on the platform. Pretty excited to see this evolve!
I also want to thank the Lab Management Product Team for their support and follow-up of this installation at my client. To be continued!