Lab Management support for VM running on non Hyper-V infrastructure
currently only VM running on Hyper-V are directly supported.
All other virtualization solution requires treating the VM like physical machine and therefore it is not easily possible to test a multiple machine setup. Especially ESX based virtualization is very common.
Daniel Steiner
shared this idea
This is a commonly asked feature. We will make some more headway in supporting non-Hyper-V platforms. However, the first class experience will continue to be offered on SCVMM and Hyper-V platform, at least for the next release.
Vijay Machiraju, Principal Program Manager, Visual Studio Test and Lab Management
- Update (7/12/2012) -
In Visual Studio 2012 and Team Foundation Server 2012, we have improved on a concept of Standard Environments which will really help with non-SCVMM environments. It will allow you to use them in the Build, Deploy, Test workflow without any additional changes. Lab Management will even reach out to each of the machines in your environment and install the Visual Studio Agents automatically. I would love for everyone to give Standard Environments a try and then let us know if this meets what you would like or what else you would like us to do more. Thanks for trying it out!
Ed Blankenship, Program Manager, Lab Management – Visual Studio ALM
9 comments
-
Anonymous
commented
This has been a request since before the 2010 beta which was back in 2008 and you're just now starting it how disappointing!
-
Ed Blankenship commented
Thanks a ton! Keep the feedback coming! How would others prioritize the two scenarios?
-
Ed Ferguson
commented
Yes agreed #1 would be the preferred added support feature. We are VMware shop I don’t want to support two virtual platforms.
-
Rory Primrose
commented
Hi Ed,
Can't have both? I get that there must be priorities :)
I think that #1 provides more power and flexibility than #2 so #1 would ultimately be more important for me. For example, if we have a lab that pushes out a test DC along with other machines, each tester can have their own isolated setup with #1. #2 alone doesn't make this possible without significant infrastructure and manual work.
Congrats on the new position BTW.
-
Hi Rory! Perfect- that's exactly what I was getting after. It sounds like rollback/snapshot and the self-service creation & provisioning pieces are what you are really after with VMware-based Lab Management environments.
Next question - and I would love to hear what people think on this one - which is more important for VMware support?
1. Self-Service Creation & Provisioning of New Environments
2. Snapshot & Rollback of EnvironmentsThanks again!
-
Rory Primrose
commented
I don't think anything is missing from what is provided in the new standard environments. I like what I have read about it so far :). The issue for me is that I can't use the full dynamically deployed labs (including snapshot revert) with an infrastructure that is VMWare.
-
Thanks Rory - for you and your customers, what specific pieces are missing from standard environments that you would like to see? Thanks a ton!
Standard Environments in TFS 2012 do have additional support from the old "physical environment concept." For example, standard environments now support the Build, Deploy, Test workflow where they didn't for physical environments in TFS 2010.
-
Rory Primrose
commented
Not having played with 2012 yet, my understanding of standard environments is that it is like using VMs as physical machines in TFS 2010 lab management, only it automates the configuration of the agents.
While this is great, it unfortunately does not hit the mark with many companies that I work for. Most organisations that I deal with use VMWare however I still want the full flexibility of dynamic labs that SCVMM provides. I hope this gets some traction in the next version.
-
Please help try out the new Standard Environment feature of Visual Studio 2012 and Team Foundation Server 2012 and let us know what you think. The release is just around the corner!
