Skip to content

NubeStack Cloud documentation

Learn to run instances, private networks, volumes and HTTPS load balancers in Karachi and Islamabad, from the console or the API.

Popular Instances Load balancers API keys API reference

New to NubeStack Cloud?

From an invitation to an instance you can log in to over SSH, in five short steps.

  1. Sign up and sign in
  2. Find your way around the console
  3. Understand your organization
  4. Create a project
  5. Launch your first instance

Start the guide

Services

All services

  • Compute

    Instances, SSH keys, images, server groups, launch templates and instance groups.

  • Networking

    Private networks, routing, Internet gateways, security groups, public IPs and load balancers.

  • Storage

    Volumes that outlive instances, snapshots, and schedules that take them for you.

  • Security

    TLS certificates for HTTPS listeners, several per listener by host name, and your second factor.

  • Organization

    People, roles, service accounts, billing, the audit log, quota and settings.

  • Every service

    All of them on one page, grouped as in the console's menu.

Work the way you prefer

Native access

The console, the API and each location's own OpenStack tools see the same projects, with the same quota and the same access.

  • Console

    Every service in your browser, plus people, roles, billing and settings.

  • API

    JSON over HTTPS under /v1: everything inside a project the console does.

  • Horizon and OpenStack CLI

    Each location's own tools, with your NubeStack sign-in. They keep working when the console does not.

  • CLI and Terraform

    The nexus CLI and Terraform provider, signed in as you or with an API key.

How it fits together

Read the concepts

Your organization holds projects. Each project runs in one location, with its own networks, instances, volumes, public IPs and quota there.

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.
The project web-shop runs in Karachi and analytics in Islamabad. Each location is a separate cloud: resources in one never move to, or depend on, the other.

Common tasks

Need a hand?

Something not working? Start with the common problems, then ask us.

Troubleshooting Glossary Support

Usage and costs are provisional

The usage, statement and cost pages show measured quantities and estimates that are still being checked against each location. They are not a bill. See Usage and costs.