Large Hosts Questions (96-128 Gigs of RAM, 10+ VM environments, storing VMs in the library)

Mar 4, 2012 at 3:31 AM
Edited Mar 4, 2012 at 3:40 AM

We are looking at buying 7 HOST machines with between 96 Gigs of RAM and 128 Gigs of RAM for our lab management environment.

1) We are looking at moving to TFS11 and SCVMM 2012 but we are concerned about the following from the guidance:

"Do not go beyond 48GB machines. There are several reasons for this:  A Hyper-V host is the minimum unit that can be allocated to a team project in Team Foundation Server (by creating a separate SCVMM host group). That is why, if you have very large hosts (for example, 64 GB), there are NO mechanisms in SCVMM or in Team Foundation Server to partition that host into smaller quotas and assign those quotas to a team project. "

What's the story for TFS11, 48Gigs of RAM is cheap now a days and this guidance seems out of date.

Also our environments are now averaging between 12-28 VMs (Biztalk, SharePoint, SQL Server, etc) and our applications are becoming more multi-tenant.

2) Does this guidance of 10 VMs per environment still apply for TFS11 and SCVMM 2012.

"Do not create network isolated environments that have more than 10 virtual machines. All virtual machines of a network isolated environment are co-placed on the same host by Lab Management. Whenever any operation is performed on such an environment, all the corresponding SCVMM jobs get spawned in parallel on that host. SCVMM recommends not having more than 10 VM creation jobs in parallel on a host. You can have multiple isolated environments on a single host, or you can use multiple hosts to allow isolated environments to be spread across multiple hosts, providing all virtual machines for each environment reside on a single host."

 3) What is the current recommendation around storing a mix of network isolated machines, domain joined machines(to CorpNet), and workgroup based machines across multiple library servers? Does the previous guidance still apply: "A best practice is to make sure all virtual machines in the Library are workgroup machines and are not domain-joined."