Private Availability Zones
Private availability zones are availability zones created for use within one account. Private zones can be used to make one or more virtualization hosts redundant to run virtual machines that require isolation at the physical level because of special security requirements or to guarantee the availability of computing resources at any time.
A private zone can be used in any account project together with public availability zones. Access to resources in the zone is limited by project quotas.
A private zone is similar to a public zone. You can transfer resources to the zone using the standard mechanism for creating a disk from a snapshot or an image.
In public availability zones, cloud servers (virtual machines) operate on physical hosts that can be shared by many clients. Each private zone is connected to one or more physical servers. Within each private zone, the client can fully control the resources that are available for virtual machines without sharing the host equipment with other clients.
Private Availability Zone Configurations
A private availability zone can consist of one or more virtualization hosts of the following configurations.
You cannot mix different host configurations within the same private zone.
The account limit for private zone resources is set as follows:
- vCPUs: 1 vCPU per one physical processor core (can be changed upon request);
- storage: total sum of capacities of virtualization hosts;
- local disk: total sum of capacities of virtualization hosts.
Maintenance of virtualization hosts in private availability zones is provided by Selectel specialists.
Available private zone host configuration without local storage
|Processor model||Processor number||CPU core number||Storage, GB||Availability in the region|
|Intel 2670v3||2||24||229||ru-1, ru-2|
|Intel 6140||2||36||354||ru-2, ru-3|
|Intel 6140||4||72||731||ru-2, ru-3|
*For ru-8 region, private zone host configurations are available upon request.
Available private zone host configuration with local storage
|Processor model||Processor number||CPU core number||Storage, GB||Local SSD capacity, TB||Availability in the region|
|Intel 6140||2||36||354||2||ru-1, ru-2, ru-3|
*For ru-8 region, private zone host configuration with local storage is available upon request.
Private Network Storage
AAll three types of cloud platform disks (fast, universal and basic) are available in the private zone. Disks have their own subtype with the name of the availability zone in their names:
fast.ru-<number>-<account_id> and work at the standard performance level that is typical for the parent zone: click here for more information. To implement non-standard requirements for disk capacity or performance, it is possible to organize a dedicated network storage for the private zone.
Network disks of the private availability zone are maintained by the storage cluster of one of region’s public zones. This allows you to create all types of disks in the private zone – fast, universal and basic.
Virtual machines in a private zone can use the same network resources as machines in public availability zones of the same region, as well as interregional routed networks that combine different regions of the Cloud Platform and other company services.
Private zones share a repository of images with other availability zones.
Virtual machines in a private zone can be connected to virtual machines in nearby zones using regular private networks.
A private zone is displayed in the list of availability zones along with public availability zones within the region. Visually, the private zone looks like a regular availability zone with the name
You can only run fixed lines virtual machines in the private zone (standard or customized request). There are restrictions on the maximum instance size, which is determined by the parameters of virtualization hosts that are part of the availability zone. For example, if a private zone is made up of hosts with 36 physical cores and 354 GB of RAM, the maximum instance size will be limited to 36 cores and 354 GB of RAM.
The cost of the private zone depends on the selected configuration of virtualization hosts and their number. The number of virtual cores, as well as the amount of memory and local disk space, are also taken into account.
The exact cost will be provided in response to a created ticket.
Private zone billing is performed on an hourly basis and can be viewed in the Control panel.
How to Order
Create a ticket to connect a private zone.
Creating a private zone of no more than 4 hosts takes up 1 business day.
Note: creating a private zone of more than 4 hosts takes longer (from one week).
Create a ticket to disable a private zone.