Concepts
Locations
Regions and their availability zones, what Stockholm and Lille offer, and how to spread servers for high availability.
Ankra Cloud is organised in regions (a metro, for example eu-north in Sweden) and availability zones
inside them (for example se-sto1). Every server, volume, network and load balancer lives in one zone; private
networks and backup copies can span the zones of a region.
GET /v1/regions lists the regions with their zones and GET /v1/zones lists the zones, both in the order the
portal shows them (each zone's position, a region by its first zone). GET /v1/zones/{zone}/capabilities says what
a zone offers right now.
Current locations#
| Region | Zone | Location |
|---|---|---|
Sweden, eu-north |
se-sto1 |
Stockholm 1 |
France, eu-west |
fr-lil1 |
Lille 1 |
Both zones run servers, block storage and private networks, and every server gets public IPv6 from its zone's range.
The rest differs per zone and changes as a zone gains hosts: which storage tiers it has, whether it has public IPv4
addresses left for the IPv4 add-on, which managed services run there, and whether it has live migration and automatic
restart. Do not assume that what one zone offers the other does too. GET /v1/zones/{zone}/capabilities is the
answer for a zone on the day (features, storage_backends, and under reasons why a missing feature is missing),
and the deploy page reads the same capabilities, so it only offers what the zone you picked can do.
A request for something a zone lacks is refused with 409 Conflict naming the feature, before anything is created
or billed, or it is delivered in the reduced form the zone can give and says so: a load balancer with
high_availability: false, for example.
High availability: zones in a region#
Each availability zone is an independent failure domain: its own power, network, gateways, storage and hypervisor
hosts. Inside one zone, high availability comes from its hosts: a zone marked HA in the portal runs servers on
several hypervisor hosts with live migration (a server moves off a host without stopping) and automatic restart
on host failure. The deploy page and the overview show it per zone, from the zone's capabilities
(features.live_migration, features.ha_restart). A zone that is not marked HA does not restart a
server elsewhere when its host fails: plan for that with backups and with copies of the service in another zone.
A zone can still fail as a whole. Where a region has two or more zones, a private network can span them, a server
group with spread: zone places its members in different zones, and backups are copied to another zone of the region
by default. Each region has one zone today, so to keep a service running through a zone outage, run a copy of it in
Stockholm and one in Lille, each on its own private network, and keep their data in step yourself (database
replication, or backups restored into the other zone).
On the deploy page you pick the region first and then the availability zone inside it.
Stockholm: servers and the cloud's IPv6 edge#
Stockholm 1 (se-sto1) is a server location like Lille 1, and it is also where the cloud's own address space meets
the IPv6 internet:
- IPv6 transit. The cloud's public IPv6 prefix
2a13:7c82:103a::/48is routed to Stockholm. Servers inse-sto1take their public IPv6 from the zone's block of it,2a13:7c82:103a:300::/56. - IPv4 egress for IPv6-only servers (NAT64). A server without the IPv4 add-on still reaches the IPv4 internet:
traffic to
64:ff9b::/96is translated to IPv4 and leaves from a shared address, outbound only. See IPv6-first networking for how DNS64 and NAT64 work and what to do in a zone without a zone NAT64.
None of this needs a setting on your side.
The Stockholm 1 data centre#
Stockholm 1 (se-sto1) runs in Obenet Riverlake, a carrier-neutral colocation data centre in Älvsjö, Stockholm,
operated by Obenet AB. Ankra AB operates the servers there and everything that runs on them; Obenet provides the
building, power, cooling and physical security.
| Area | What the facility provides |
|---|---|
| Information security | Obenet is implementing an ISO 27001 information security management system across its Riverlake and Kista Gate data centres. The facility is not ISO 27001 certified yet. |
| Data residency and privacy | The facility is in Sweden and operates under EU data residency rules, Swedish data protection law and the GDPR. Obenet's own services follow a policy of no traffic logging and no sale of data. |
| Physical security | Camera surveillance 24/7/365, personal access cards for entry at any hour, and a perimeter intrusion alarm connected to an external alarm centre. |
| Fire protection | IG-100 inert gas suppression in the server halls. |
| Energy and cooling | Power from a hydroelectric grid, and free air cooling. |
These are the facility's controls. The controls on Ankra Cloud itself (isolation between servers, encryption of the secrets Ankra holds, staff access to accounts and the audit log) are described in Security.