At the moment we have 10 VMs per ESXi host.
We have a monitoring system which tracks memory and CPU usage on each ESXi host
and we plan to use this data to review number of VMs per ESXi host later. There
is some room to add more VMs per host.
As for computers, each VM computer is configured with the same specs - 2 vCPU,
Then VCL has per image settings, which is what a VM will get when made
available or during reservation.
The per image setting will define how much resources you want to assign to this
image, but it cannot be more that VM configuration (2 vCPU/4GB in my case).
In VCL 2.2.1 per image default is 1 vCPU / 64MB (512MB). If you left it by
default for all images, all your running VMs would use very little resources,
which could affect performance …
When you considering running large number of VMs per ESXi, make sure that you
storage can handle it. VCL design is using shared storage, more ESXi servers
you add, faster your storage should be.
You could configure VM Host profile to use ESXi's local storage for running
images. This would off-load shared storage, since you are only going to read
from it (except when you create/update an image).
Virtual Computing Lab Systems Engineer, TSD - Ent Servers & Messaging
223 Aquia Building, Ffx, MSN: 1B5
Phone: (703) 993-6175
Fax: (703) 993-3404
On Monday, May 7, 2012 at 15:59 , Pablo J. Rebollo-Sosa wrote:
> Hi Dimitri,
> ¿How many virtual machines you can handle per blade? ¿What specs have the
> virtual machines?
> On 4/9/12 3:50 PM, Dmitri Chebotarov wrote:
> > Pablo
> > I can tell what hardware we use for VCL - other people may have different
> > setups.
> > We use IBM's Blade Center H chassis with HS21/22 blades (7870 type):
> > - 2xCPUs, from Xeon X5550 (older) to X5660 (newer),
> > - 24GB to 48GB of memory,
> > - 2x73GB RAID1 local storage (system only, can be replaced by embedded
> > VMWare)
> > CPU and memory per blade will depend on how many VMs you would like to have
> > on a ESXi host, or what is an application's hardware requirement if you
> > plan to use xCAT.
> > Storage is N6040 (NetApp FAS3140 equivalent), using NFS - very flexibile
> > and fast (NetApp works well with VMWARE).
> > I would recommend to have de-duplication license, it saves a lot of space
> > on the volume where you store images.
> > You will need two separate networks - Private (to be used by VCL) and
> > Public (users access to reservations).
> > I hope it helps.
> > Let me know if you want to know something else...
> > Thanks.
> > --
> > Dmitri Chebotarov
> > Virtual Computing Lab Systems Engineer, TSD - Ent Servers & Messaging
> > 223 Aquia Building, Ffx, MSN: 1B5
> > Phone: (703) 993-6175
> > Fax: (703) 993-3404
> > On Monday, April 9, 2012 at 15:00 , Pablo J. Rebollo-Sosa wrote:
> > > Hi,
> > >
> > > I'm interested to know about the typical hardware used to implement the
> > > VCL solution in terms of chassis, CPU/cores, memory, storage, etc.
> > >
> > > Thanks in advanced.
> > >
> > > Pablo J. Rebollo-Sosa