Skip to main content

Visual Studio 2010 Lab Management and Virtualization

Good to see some serious efforts being undertaken to have lab management and automation.

You (or the someone you know) may be asking yourself - why is this a good thing? Here's what the Visual Studio guys told me:

* 30% of testing time is spent in setting up machines and labs
* Under 30% utilization of test and dev assets
* “No Repro” bugs often slip into production impacting project success

The guys also told me:

Unlike other tools, Microsoft’s capabilities around lab management are fully integrated to Visual Studio Team System allowing teams to collaborate more effectively and not have to deal with disparate tools. Lab management is fully integrated with the testing capabilities allowing generalists testers to take quick checkpoints on failures & record rich bugs with links to the environment in the bug that the developer can then open. It is also integrated into the build process allowing customers to automatically trigger a virtual environment provisioning, build deployment & testing of the build.

Lab Management leverages virtualization and allows multiple checkpoints to be created across lab environments (consisting of multiple VMs). Since the checkpoints are part of the same image as opposed to having to clone at every state snapshot, that reduces the proliferation. In addition, lab management ties the environments to the notion of a project which allows the lab administrator to clean up the images as projects are completed.

Lab Management is built on top of System Center Virtual Machine Manager, and thanks to SCVMM managing VMs on multiple hypervisors, Lab Management supports both Hyper-V and VMware ESX out of the box.


Source

Comments

Popular posts from this blog

Security: VMware Workstation 6 vulnerability

vulnerable software: VMware Workstation 6.0 for Windows, possible some other VMware products as well type of vulnerability: DoS, potential privilege escalation I found a vulnerability in VMware Workstation 6.0 which allows an unprivileged user in the host OS to crash the system and potentially run arbitrary code with kernel privileges. The issue is in the vmstor-60 driver, which is supposed to mount VMware images within the host OS. When sending the IOCTL code FsSetVoleInformation with subcode FsSetFileInformation with a large buffer and underreporting its size to at max 1024 bytes, it will underrun and potentially execute arbitrary code. Security focus

Linux, Linux : Get started with VMWare and Knoppix or Ubuntu Live CD!

Well everyone's talking about it now and you're wondering "what the heck is Linux?". So you've finally come face to face with yourself and say it loudly(errum..In your head first , please). I want to learn it! I admit it, I've been a fool! I hafta learn this kool OS! OK chill! You're faced with a challenge of all that installation crap. And boy, ask the veterans they've made lot's of money just installing Linux and installing Oracle on Linux was a big thing. And talking about setting about clusters was only for Big Boys and doing Oracle RAC setup was only for BEEEG BOYZ!!! Ok I can see you're already sleeping on my story. And Hey! Stop drooling on my shoulder! Wake up!!! You yell back at me " WHAT DO I HAFTA DO? WHERE I GOTTA KLIK? I Don't wanna fight with my wife over installing Linux at home? And my Microsoft Boss is angry because I made my colleagues so scared when I installed Linux at work? Ok Ok I get it. You want to learn it'...