Skip to content

Projects and quotas

A project groups what you run and who may use it. It runs in one location, chosen when it is created, and has its own quota there. Every instance, network and volume belongs to exactly one project.

One location per project

A project's location never changes. Its networks, instances, volumes, public IPs, security groups and quota are all in that location, so a project's pages never ask you to choose one.

To run in Karachi and Islamabad, make a project in each, for example web-shop in Karachi and web-shop-dr in Islamabad, and give the same people a role on both. Usage, costs and the audit log cover the whole organization.

Who can use a project

An organization role alone does not let anyone use a project's resources. People and service accounts use a project through a project role: project admin, project member or project reader, or a custom role. The project's IAM → People lists who holds which. See Roles and permissions.

Quota

Quota is how much a project may hold: instances, vCPUs, memory, volumes, storage, networks, public IPs and the rest. It is set in two layers:

  1. NubeStack sets the organization's budget in each location.
  2. Owners and admins share that budget between the projects in the location. A new project starts from a quota preset.
Quota in two layers In each location, Karachi pak-khi-1 and Islamabad pak-isb-1, NubeStack sets the organization's budget: how much Acme may hand out there. Acme's owners and admins share that budget between projects, so each project has its own quota in the location it runs in: web-shop in Karachi; reports and analytics in Islamabad. A new project starts from a quota preset: the preset's figure, or what is left of the budget there, whichever is less. When a budget runs short, owners and admins ask NubeStack for more, one location at a time. Each location enforces its own quota, and quota is not capacity: a location can still be out of room. NubeStack Sets the organization's budget in each location Request more one location at a time owners and admins ask Karachi · pak-khi-1 Acme's budget What Acme may hand out here Shared by owners and admins web-shop Project quota Islamabad · pak-isb-1 Acme's budget What Acme may hand out here Shared by owners and admins reports Project quota analytics Project quota Quota preset A new project starts with the preset's figure, or what is left of the budget there, whichever is less. Each location enforces its own quota. Quota is not capacity: a location can still be out of room.
Two layers, per location: the organization's budget from NubeStack, and each project's share of it.

The location enforces the quota. A request over it is refused, even if the console's check let it through, for example because something was made at the same moment with the location's own tools.

A project's quota: each resource, what is allocated and what is in use
A project's quota: each resource, what is allocated and what is in use

Everyone with a role on the project sees its quota, and what it used this month, under Quota at the bottom of the menu. How owners and admins set it: Quota.

Quota is not capacity

Quota says how much you may use. Whether a location has room right now is separate: a request within quota can still fail when a location has no room for that size. The operation says so; try another size, or try again later.

Names

A project has a name (up to 200 characters) and a short name (lower-case letters, digits and dashes) used in addresses and in the location's own tools. Neither can change after creation.