Ram Cherala Principal Program Manager Microsoft Corporation TL37.

Improving Code Quality With Visual Studio Team System 2010 Lab Management

Virtualization To The Rescue!!

Ram CheralaPrincipal Program ManagerMicrosoft Corporation

TL37

Agenda

Dev Challenges

How Lab Management addresses them – Demo!!

Build workflow

Architecture

Lab Management in a nut shell

Q & A

Can You Relate To This?

Tester

Developer

Can You Relate To This?

Bug “ping-pong”

Expensive context switches

“Double-hop” issues

Slow turnaround – How can we be Agile?

Rich bug & lab environment

demo

NO MORE BUG

PING-PONG!!

Creating A Rich bug

demo

CREATINGA

RICH BUGIS EASY!!

RecapRich bug and Lab environment

Rich bug

• Action and video log• System information• Event logs, historic debugging and lab environment

Lab Environment

• Group of Virtual Machines with an identity which can be rapidly provisioned• Can be copied, check pointed, shared

Dev Access to Environment

• Developer has access to tester’s environment• Direct access to test machines makes debugging easy!!• Network fencing enables you to run a copy of the environment

Traditional Build Workflow

Compile Code

Deploy Applicati

on

Run Tests

Lab Management Build Workflow

Compile Code

Restore Environ-

ment

Deploy Application

Take Checkpoint

Run Tests

Lab Management Architecture

Team Foundation Server (TFS)

Lab Manageme

nt

System Center Management Stack

Operations Manager

Virtualization Platform

Hyper-V

Lab Management In A Nut Shell

Improves Productivity

• Along with historic debugging support, makes “No-Repro” bugs a thing of the past!!

• Easily revert to a baseline configuration

Improves Efficiency

• Self-service library of machines• Reduces significant setup time• Scheduled build/test cycle on steroids

Enables Parallelism

• Share your environment with others• Network fencing comes to the rescue!!

Call To Action

Get familiar with virtualization – any virtualization!!

Try Visual Studio Team System hands on labs

Tell your test buddies about Lab Management

VSTS 2010 Hands On Labs

HOL Code Title

TLHOL07 VSTS 2010: Project Planning, Management, and Design

TLHOL08 VSTS 2010: Architecture Tools

TLHOL09 VSTS 2010: Team Foundation Server

TLHOL10 VSTS 2010: Software Quality

TLHOL11 VSTS 2010: Diagnostics and Performance

My A's To Your Q's

Please submit session evaluation form at http://microsoftpdc.com

Feedback/questions, email to vslmpdc@microsoft.com

Evals & Recordings

Please fill

out your

evaluation for

this session at:

This session will be available as a recording at:

www.microsoftpdc.com

Please use the microphones provided

Q&A

© 2008 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market

conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

Appendix

Lab Management Network Fencing

IIS DB10.10.1.5 10.10.1.6

172.22.48.15 172.22.48.16

Copy 1

IIS DB10.10.1.5 10.10.1.6

172.22.48.17 172.22.48.18

Copy 2

Fence network(Internal) Lab network

(External)

What

• Create multiple copies of environment

• They can run in parallel without conflicts

• No application reconfiguration

How• Internal fence network is created

for all VMs• A VM gets the same MAC & IP

address, and computer name in all copies

• VMs are also connected to the external lab network