Dedicated Cluster

From Cloud Avenue
Jump to navigation Jump to search

Overview

The vDC provided to our Customers are based on shared resources.

To meet specific Customer constraints (for example the need to use the Customer's Microsoft SPLA ), Cloud Avenue propose the privatization of a group of physical servers within the shared platform.

Cloud Avenue provides the necessary tools allowing the Customer to verify that its VMs have not been able to operate outside its dedicated cluster, so that the Customer can ensure that it is compliant with its software editor rules.

The basics

The Customer orders several physical servers in order to constitute a dedicated Provider vDC, and on which one (or more) vDC is built, thus grouping together all the resources embedded in the physical servers.

The recommended resource allocation mode is the Reservation Pool. This way of allocating resources has several advantages:

  • The limits are set at the vDC level, which are, in our case, aligned with the capabilities of the physical cluster; which allows VMs to access more resources, as long as they are available in the vDC ("burst mode").
  • The percentage of guaranteed resources and the vCPU frequency can be set when creating the vDC, which will allow the Customer to manage the consolidation ratio himself.

The parameters that can be set when creating the vDC are:

  • CPU reservation percentage
  • RAM reservation percentage
  • The frequency of vCPUs in GHz

In addition to these parameters, the overbooking rate will be given by the number of VMs that the Customer will create in the vDC.

More information on the "Reservation Pool" resource allocation model on the vmware site.

High availability

To preserve the availability of the applications if a node is missing, the sizing of the cluster must take into account the loss of a blade. A defective blade will be replaced within 48 hours. However, within this time frame, VMs should be able to run on a blade-less cluster without significant performance impact to hosted applications.

Notepad.png
Note!
The Customer is responsible for the sizing of its cluster.


Capacity management

Capacity management is at the Customer's initiative. Cloud Avenue will provide the VMware metrics to monitor the overall performance of the cluster, as well as the performance of the VMs. The decision to change the cluster size is Customer's responsibility.

The time required for setting up a new blade is generally a few minutes (operation carried out online by the Customer in his Cloud Customer Space).

The other resources (storage, network, etc.) are provisioned from the Cloud Customer Space, for any classical vDC, and are invoiced according to the tariff sheet in force.

Example of configuration

Blade servers with 56 cores/576 GB of RAM per blade, and overbooking targeted to 1,5

Number of blade 56 cores/576 GB of RAM 3 4 5
Total number of available vCPU 168 224 280
Available vCPU if a blade is missing 112 168 224
Overbooking rate (vCPU/physical core) 1,5 1,5 1,5
Resources pool capacity
vCPU (nominal) 252 337 420
RAM (nominal) 1728 2304 2880
vCPU (one blade missing) 168 224 280
RAM (one blade missing) 1152 1728 2304

Subscription

The minimum cluster size is two servers. Invoicing is carried out monthly on the basis of the number of physical servers reserved, and according to their characteristics (see the tariff sheet).

Cloud Avenue provides physical servers with the following specifications:

Specifications Type 1 Type 2 Type 3
CPU Intel xeon Gold
CPU frequency 2,2 GHz 3 GHz 2,2 GHz
Nb of CPU 2 2 2
Nb of core/CPU 28 24 28
Nb of vCPU / blade 56 48 56
Ram 576 GB 256 GB 256 GB
Usage dedicated vmware cluster dedicated vmware cluster dedicated NSX-T cluster

A blade added during the month is billed pro rata temporis to the number of days it is active in the month.

Subscribing to a dedicated cluster and adding a blade are done from the Cloud Customer Space.


Return to Services catalogue