Skip to content

Locations

A location is one of NubeStack's clouds. NubeStack Cloud has two:

Location Code Shown in the console as
Karachi pak-khi-1 Karachi
Islamabad pak-isb-1 Islamabad

The code is what you see in the API, in the location's own tools and in clouds.yaml. The API identifies a location by an ID starting loc_, from GET /v1/orgs/{org_id}/locations.

A project runs in one location

You choose a project's location when you create it, and it never changes. Everything in the project, its instances, networks, volumes, public IPs and quota, is in that location. The scope selector at the top of the console lists your projects under their locations.

To run in both locations, for example to keep a copy of a service in Islamabad, create a second project there and give the same people access to both. Usage, costs and the audit log cover the whole organization either way.

Each location is independent

Each location is a separate OpenStack cloud, with its own capacity, networks, storage, images and sign-in. Design for that:

  • Things stay where you make them. Nothing is copied or moved between locations.
  • Networks do not cross locations. A network in Karachi cannot reach a network in Islamabad privately. Instances in two locations talk over the Internet, through public IPs.
  • Images and snapshots stay too. To run the same setup in the other location, set up an instance in a project there and save it as an image again.
  • Trouble stays local. One location in maintenance, full or unreachable never stops the other. One location's problem never empties a page.
How an organization's resources fit together The organization Acme has two projects, each in one location. The project web-shop runs in Karachi: a public IP points at a load balancer that sends traffic to the instances web-1 and web-2 on the private network app, and the instance db-1 on the same network has a volume, db-data, attached. The project analytics runs in Islamabad, with its own network default and the instance batch-1. Nothing is shared between the two locations. Internet Organization · Acme Project · web-shop Project · analytics Karachi · pak-khi-1 Islamabad · pak-isb-1 Public IP 203.0.113.40 Load balancer web-lb · HTTPS 443 Network · app · 10.0.0.0/24 web-1 Instance · 10.0.0.11 web-2 Instance · 10.0.0.12 db-1 Instance · 10.0.0.30 db-data volume Security groups filter what reaches each instance. Network · default 10.0.0.0/24 batch-1 Instance · stopped Another project, with its own networks, volumes and quota.
Two projects, two locations: web-shop in Karachi and analytics in Islamabad, each with its own networks, instances, volumes and quota. Nothing is shared between them.

To survive a location's failure, run a copy of your service in a project in the other location, with its own data, and send traffic to both. NubeStack Cloud does not fail over for you.

What a location offers

Each location has its own catalog: the sizes of instances, the operating-system images, the volume types and, where offered, the load-balancer types. Create pages show what the project's location offers. The two locations can differ: a load balancer type, for example, may be offered in one location and not the other.

Through the API: GET /v1/orgs/{org_id}/catalog?location=loc_….

Maintenance

NubeStack sometimes takes a location into maintenance. While it lasts, what you have keeps running and you can still read it, but new work there may wait or be refused with location_maintenance, which you can retry later. A strip at the top of the console says so. Owners and admins receive e-mail notices when maintenance starts, is extended and ends, unless they turn them off (E-mail notices).

A location can also stop taking new projects while it keeps running what is there. Its New project here row then leaves the scope selector.