Portal Home > Knowledgebase > Information > Resource Cloud or Private Cloud Policies

Resource Cloud or Private Cloud Policies

Memory

Active Memory can not be over provisioned. Over provisioning of active memory causes disk swapping and balloning which causes excessive utlization of SAN resources.

To Check the Memory Ballooned or Swapped: 

Under the VSphere Client go to Home -> Inventory -> Host and Clusters
Click on your Resource Pool and select on the right screen the summary tab.
On the guest Memory section you will see the Ballooned and the Swapped Memory.
You can see which VM is Ballooning or Swapping Memory by clicking on each VM and looking at the Resource Allocation tab. 
If you see that you have Memory ballooning or Swapping you need to immediately fix it by reducing the active memory to some of your VMs.


CPU

The limitations on Resource Cloud/Private Cloud Solutions are as follow:

Product type ordered

  • 1 CPU-4 Cores are limited to a total vCPU weight of 12 
  • 1 CPU-6 Cores are limited to a total vCPU weight of 18.
  • 2 CPU with 4 Cores each are limited to a total vCPU weight of 24.
  • 2 CPU with 6 Cores each are limited to a total vCPU weight of 36.
  • 4 CPU with 4 Cores each are limited to a total vCPU weight of 48.

  • VMware Resource Cloud with 4GB - Up to 4 VMs are limited to a total vCPU weight of 4.
  • VMware Resource Cloud with 8GB - Up to 6 VMs are limited to a total vCPU weight of 6.
  • VMware Resource Cloud with 16GB - Up to 12 VMs are limited to a total vCPU weight of 12.
  • VMware Resource Cloud with 32GB - Up to 18 VMs are limited to a total vCPU weight of 18.
  • VMware Resource Cloud with 48GB - Up to 24 VMs are limited to a total vCPU weight of 24.
  • VMware Resource Cloud with 64GB - Up to 36 VMs are limited to a total vCPU weight of 36.


VM powered on weight

  • 1 vCPU Virtual Machine has a vCPU weight of 1
  • 2 vCPU Virtual Machine has a vCPU weight of 4
  • 3 vCPU Virtual Machine has a vCPU weight of 6
  • 4 vCPU Virtual Machine has a vCPU weight of 8
  • 5 vCPU Virtual Machine has a vCPU weight of 10
  • 6 vCPU Virtual Machine has a vCPU weight of 12
  • 7 vCPU Virtual Machine has a vCPU weight of 14
  • 8 vCPU Virtual Machine has a vCPU weight of 16

*Powered off VMs do not count against the vCPU weight and do not need to be calculated in the total.


Calculating totals

 

  1. Compare your product ordered to the "Product type ordered" list above to arrive at your total vCPU  weight.
  2. Each VM has a vCPU weight that can be cross referenced under the "VM powered on weight" list above.
  3. Total the vCPU weight of all VMs under a product.
  4. Compare the total arrived at in step 3 and if this total is above the total arrived at in step 1 you have overprovisioned your CPUs under the solution ordered.

 

Example:

Let's say you have a 1 CPU-4 Cores account which has a maximum vCPU weight of 12 you will be able to host on this account:
  • 12 x 1vCPU Virtual Machines
    (12)x(1)                             =12

  • 3 x 2vCPU Virtual Machines
    (3)x(4)                              =12

  • 2 x 2vCPU Virtual Machines AND 4 x 1vCPU Virtual Machines
    (2)x(4) =8                          + (4)x(1) =4                       =12

  • 1 x 4vCPU Virtual Machine AND 4 x 1vCPU Virtual Machine
    (1)x(8) =8                          + (4)x(1) =1                       =12
  • 1 x 4vCPU Virtual Machine AND 1 x 2vCPU Virtual Machine
    (1)x(8) =8                          + (1)x(4) =4                       =12

Notification

247RACK  will notfiy if customer exceeds policy guidelines and will provide up to 24 hours notice to bring the products in compliance.

247RACK  may, in addition, suspend Customer’s operations on Resource Cloud if, in 247RACK ’s sole discretion and reasonable consideration, there arises an emergency over-provisioning situation.


Also Read

Language: