Regions and availability zones#

3HCloud infrastructure is hosted in physical data centers grouped into regions and availability zones:

  • Region defines the geographical location of the infrastructure.

    Each region has independent power supply, cooling, and network connectivity systems.

    Regions are isolated from each other, so hardware and software failures in one region do not directly affect the infrastructure in another region.

    A region can include one or more availability zones. The choice of region depends on the location of users and systems, latency requirements, the availability of specific resources, and other infrastructure considerations.

  • Availability zone defines a separate, physically isolated part of the infrastructure within a region.

    Availability zones have independent power supply and cooling systems and are interconnected through additional low-latency networks.

    Zone isolation reduces the impact of hardware and software failures. If a service supports resource placement across multiple availability zones, distributing resources between zones can improve infrastructure fault tolerance.

Regions and availability zones represent different levels of infrastructure location:

Region → Availability Zone → Resource

For example, WAW-1 and WAW-2 belong to the same geographical area — Warsaw — but are separate availability zones.

Not all resources have the same placement scope. Depending on the service type, a resource may be: * Tied to a specific availability zone. * Available throughout an entire region. * Subject to its own placement model.

A region is a general characteristic of the infrastructure, but individual services may use regions and availability zones differently.

Placing resources in different availability zones can help improve fault tolerance.

In most cases, resources located in the same availability zone can access each other, while resources located in different zones are not reachable from one another.

For example, virtual servers in the WAW-1 zone cannot be migrated to hypervisors in the WAW-2 zone, use virtual volumes from that zone, or connect to servers in that zone over a local network.

Available regions and zones#

A specific zone may temporarily be unavailable for creating new resources. This does not indicate a failure of the existing infrastructure and does not affect resources that are already running.

If you cannot create a new resource in the selected zone, choose another available zone or try again later.

Currently, 3HCloud provides infrastructure in the following regions:

  • Miami, USA

  • Dallas, USA

  • San Francisco, USA

  • Warsaw, Poland

  • Manila, Philippines

3HCloud infrastructure is available in the following availability zones:

  • SFO-1 - San Francisco, USA

  • MIA-1 - Miami, USA

  • DFW-1 - Dallas, USA

  • WAW-1 - Warsaw, Poland

  • WAW-2 - Warsaw, Poland

  • MNL-1 - Manila, Philippines

Resource quotas#

For the cloud platform, resource quotas are set at the region level.

Zonal resources within the same region share a common quota.

Resource consumption in one zone affects the available quota in other zones within the same region.

If the required quota is available in the region, you can create the resource in any availability zone that supports that resource type.

Resource movement#

Virtual servers and volumes cannot be directly migrated between regions or availability zones.

To move a virtual server or volume to another region:

  1. Create a backup or snapshot of the required volume.

  2. Create a new volume in the target region.

  3. Restore the volume from the backup or snapshot using the OpenStack API.

Virtual volumes can be moved between availability zones using backups. To do this, select the required availability zone when creating a volume from an existing backup.

Warning

IP addresses associated with a region are not retained when a resource is moved to another region.