@Lab Management for everyone

Matteo Emilihttp://blogs.ugidotnet.org/j3rhttp://mattvsts.blogspot.com

matteo.emili@domusdotnet.org@MattVSTS

…

Grazie agli sponsor

@• Multiple environments• “On my machine!”• Give the package to the test team and forget

• Is it seamless?

How do we test our software today?

@• First release of the Microsoft’s solution for automating Quality Assurance tasks

• It needs a huge infrastructure effort (Active Directory in place, Hyper-V, System Center Virtual Machine Manager)

Visual Studio Team Lab Management 2010

@• Windows 8 provides us Hyper-V like server OSes, but without their limits

• Visual Studio Team Lab Management 2012 provides us a new set of features

New technologies on the edge!

@Hyper-V

Hardware (VT-x or AMD-V capable)

Hypervisor (Hyper-V)

VMBus

Kernel

Device

Drivers

VSP

WMI ProviderVM Management

Service

vmwp.exevmwp.e

xevmwp.exevmwp.e

xe

VMBus

KernelVSC

Applications

Parent Partition Child Partition

@•Hardware virtualization capable CPU (Intel VT, AMD-V)•NX Bit support on CPU and motherboard (Intel XD bit, AMD Enhanced Virus Protection)•SLAT capable CPU (Intel Core iX, Xeon L/E/X55xx, AMD Phenom, Athlon II)•For Windows 8 Hyper-V

Hyper-V Requirements

@• Fast dedicated HDDs (7200rpm+)• Gigabit Ethernet connection (if you

want to do storage move)• Tons of RAM!

Nice to have…

@• Dynamic Memory• Dynamic allocation of memory based on consumption

• Live storage move (while they are running, and without a shared storage!)• VHDX file format for Virtual Hard Drives up to 64TB each• Support for hybernation and sleep (so you can use it on a laptop!)

Hyper-V features for the vDev

@• Expanding developers’ needs to a common, shared testing environment• The testing environment must be predictable and capable of managing multiple, complex infrastructures• You might need allowing someone else interacting with it• You might need integration with Team Foundation Server

Developer -> Team

@• New VSTLM 2012 mode

• No infrastructure requirements• The only requirements are Microsoft Test Manager 2012, Team Build and the Visual Studio Agents

Visual Studio Standard Environment

@“Feedback client?” Yes.“Deploy to it with Team Build?” Yes.“Physical machines?” Yes.“Use it on my laptop?” Yes.

FAQs over Standard Environment

“VMWare support?” Yes.

@DEMO

A lap around Standard Environmentsa.k.a. Lab Management for Everyone

@• Virtual labs can be employed in thousand of different scenarios

• It’s a quality enabler at all levels• Developers can have a ‘certified’

environment for testing• Continuous Delivery• Stakeholders’ feedback

Virtual labs as a foundation for everything

@• SysprepBuilt-in into Windows, it enables creation of a clean base OS with all you need• Snapshots

Hyper-V feature which allows taking snapshots to have certain states saved. Be careful: do not use it with Domain Controllers

Tips for management

@• Use a separate high speed drive (7200rpm+) for VMs

• Mark the environments ‘In Use’ if shared

• Use Dynamic Memory and set the OS as if it should save as much energy as possible

Best practices

@Questions & Answers