Compliant Cloud
Feature is in production and fully supported
Feature is in deployment, not yet supported
Feature is deprecated, being phased out
Feature is not available
The new Sto-Com region, also known as Compliant Cloud v2, implements certain technologies that significantly differentiate it from other Cleura Cloud regions.
Availability zones
The Sto-Com region has three (3) availability zones (AZs) connected by a stretched Layer 2 network. Resources are allocated randomly between the three whenever an AZ is not explicitly specified. Each AZ has its own block storage, and no live migration between AZs is possible.
Block storage
| Sto1HS | Sto2HS | Sto-Com | |
|---|---|---|---|
| Highly available storage | |||
| High-performance local storage | |||
| Volume encryption |
Volumes in Sto-Com are provided by Ceph. Cloud servers with ephemeral storage have low-latency disks (LLDs) that are local to the corresponding hypervisor.
Domain-based OpenStack endpoints
Instead of having different endpoints on different ports of the same domain name, Sto-Com offers different subdomain names per endpoint.
The following is a list of domain-based endpoints valid for Sto-Com:
| Service Name | Service Type | URL |
|---|---|---|
| barbican | key-manager | https://key-manager.sto-com.cleura.cloud/ |
| cinderv3 | volumev3 | https://volume.sto-com.cleura.cloud/ |
| octavia | load-balancer | https://load-balancer.sto-com.cleura.cloud/ |
| keystone | identity | https://identity.sto-com.cleura.cloud/ |
| radosgw | object-store | https://object-store.sto-com.cleura.cloud/ |
| placement | placement | https://placement.sto-com.cleura.cloud/ |
| heat | orchestration | https://orchestration.sto-com.cleura.cloud/ |
| neutron | network | https://network.sto-com.cleura.cloud/ |
| nova | compute | https://compute.sto-com.cleura.cloud/v2.1/ |
| glance | image | https://image.sto-com.cleura.cloud/ |
Object storage
| Sto1HS | Sto2HS | Sto-Com | |
|---|---|---|---|
| S3 API | |||
| S3 SSE-C | |||
| S3 object lock | |||
| Swift API |
The Object Store in Sto-Com is configured so that data written in a container or a bucket are automatically stored and synchronized between all three availability zones. Users may define policies so that a specific bucket is located in a single AZ.
Contrary to other regions, where images live on Ceph RBD pools, images in Sto-Com reside in an object store. As a result, new VMs in Sto-Com may take longer to initialize.
OVN Octavia provider
Sto-Com comes with two providers for Octavia: the Amphora Layer 7 Load Balancer (LB) and the OVN Layer 4 LB. The Amphora LB is the default.
Networking (Layer 2/3)
| Sto1HS | Sto2HS | Sto-Com | |
|---|---|---|---|
| IPv4 (with NAT) | |||
| IPv6 | |||
| VPN (IPsec with PSK) |
In Sto-Com, Quality of Service in Neutron is configured for tenant networks, router gateways, and floating IPs:
| Port type | Bandwidth limit |
|---|---|
| VM ports (private networks) | 2 Gbps |
| Floating IPs | 1 Gbps |
| Router Gateways | 1 Gbps |
Load Balancers
| Sto1HS | Sto2HS | Sto-Com | |
|---|---|---|---|
| Transport layer (TCP/UDP) | |||
| Application layer (HTTP) | |||
| Application layer (HTTPS, with secrets management for TLS certificates) | |||
| Metrics endpoint |