Private pool segments

Private pool segments can be used to reserve one or more virtualization hosts — to launch cloud servers with physical-level isolation, if there are special security requirements or to guarantee the availability of computing resources at any time.

In public pool segments, cloud servers run on physical hosts that may be shared by many clients. Each pool segment is linked to one or more physical servers. Within each private segment, you can have full control over cloud platform resources without sharing host hardware with other clients.

Available resources

A private pool segment can be used in any account project alongside public pools. Access to resource usage is limited by project quotas.

In a private pool segment:

all network volume types of the cloud platform are available. To meet non-standard capacity or performance requirements for network volumes, you can set up dedicated network storage;
you can configure network volumes to be backed up with backups;
cloud servers can use the same network resources as in public segments;
cloud servers can be connected with servers in other segments via a private network;
image storages of the pool segments on which they are launched are used.

Configurations

A private pool segment can consist of one or more virtualization hosts. You cannot use multiple different processors within a single segment.

Account limit for private pool segment resources:

vCPU — 1 vCPU per physical processor core (can be changed upon request);
RAM — sum of virtualization host capacities;
local disk — sum of virtualization host capacities.

In a private segment, you can create cloud servers:

with private flavors;
with fixed configurations, if they were specified when ordering the private pool segment.

There are limits on the maximum size of a cloud server—this is determined by the parameters of the virtualization hosts that are part of the pool segment. For example, if a private pool segment is formed from hosts with 36 physical cores and 354 GB of RAM, the maximum server size will be limited to 36 vCPU and 354 GB of RAM.

Virtualization host maintenance in private pool segments is performed by Selectel specialists.

Processors

You can check processor availability in locations in the Private Pool Segments subsection of the Product Availability by Location guide.

	Intel® Xeon® Processor E5-2670 v3 @ 2.30 GHz	Intel® Xeon® Processor E5-2680 v4 @ 2.40 GHz	Intel® Xeon® Processor E5-2699 v4 @ 2.20 GHz	Intel® Xeon® Gold 5218 @ 2.30 GHz	Intel® Xeon® Gold 6140 @ 2.30 GHz	Intel® Xeon® Gold 6240 @ 2.60 GHz (in the ru-7a pool segment)	Intel® Xeon® Gold 6240 @ 2.60 GHz (in the ru-7a, ru-9a pool segments)	Intel® Xeon® Gold 6240R @ 2.40 GHz	Intel® Xeon® Gold 6336Y @ 2.40 GHz	AMD EPYC™ 7742 @ 2.25 GHz	AMD EPYC™ 7763 @ 2.45 GHz
Number of processors	2	2	2	4	2 / 4	2	4	2	2	2	2
Number of cores	24	28	44	64	36 / 72	36	72	48	48	128	128
RAM, GB	229	229	229	731	349 / 371	221 / 349	731	221 / 349	221	450	731
SSD local disk size, TB (for hosts with local storage)	✗	✗	✗	✗	3.6 / 7.2	3.6	3.6 / 7.2	3.6	3.6	✗	7.2

Connect a private pool segment

To connect a private pool segment, create a ticket.

Creating a private pool segment with up to four hosts takes one business day; for five or more hosts, it takes one week or more.

You can transfer resources to a private pool segment from a public one yourself — create a volume from a snapshot or image.

Pricing

Private pool segments are paid for using the cloud platform payment model.

The cost of a private pool segment depends on the selected virtualization host configuration and their quantity — calculations include the number of physical cores, amount of memory, and local disk size.

We will provide the exact cost in the ticket response.