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
Labels:

Comments

Post a Comment

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
Post a Comment
Read more

Splunk that!

Saw this advert on Slashdot and went on to look for it and found the tour pretty neat to look at. Check out the demo too! So why would I need it? WHY NOT? I'd say. As an organization grows , new services, new data comes by, new logs start accumulating on the servers and it becomes increasingly difficult to look at all those logs, leave alone that you'd have time to read them and who cares about analysis as the time to look for those log files already makes your day, isn't it? Well a solution like this is a cool option to have your sysadmins/operators look at ONE PLACE and thus you don't have your administrators lurking around in your physical servers and *accidentally* messing up things there. Go ahead and give it a shot by downloading it and testing it. I'll give it a shot myself! Ok so I went ahead and installed it. Do this... [root@tarrydev Software]# ./splunk-Server-1.0.1-linux-installer.bin to install and this (if you screw up) [root@tarrydev Software]# /op
Post a Comment
Read more