Tenants, subscriptions, projects, and regions

Everything you do in Bulutistan Cloud happens in a scope with four levels: your organization's tenant, a subscription, a project, and the project's region. The top bar of the console always shows the scope that you're working in.

Tenant: Acme Corp
├── Subscription: Default      (created at sign-up, billed in USD, region Istanbul 1)
│   └── Project: core
└── Subscription: Production   (billed in TRY, region Istanbul 1)
    ├── Project: core
    └── Project: web-platform

TenantCopy Anchor Link

The tenant is your organization: the top level, and the boundary that keeps your data apart from every other organization's. It's created when you sign up, and named after the organization name that you enter. The console also calls it the organization.

These belong to the tenant as a whole: its members, its service accounts, and its custom roles.

An email address can belong to only one account on the platform. You can't sign up a second organization with an address that's already registered, and an address that already has an account can't be invited to another organization.

SubscriptionCopy Anchor Link

A subscription is a billing account in your tenant. It sets the currency that you're billed in and the region that its projects run in. Invoices, payments, credits, commitments, and the subscription's quota belong to the subscription, and the usage of all its projects is billed to it.

A tenant can have several subscriptions, up to a limit. When you reach the limit, you can't create more. For the currency, pausing, and billing, see Subscriptions and currency.

ProjectCopy Anchor Link

A project is where your resources live: instances, volumes, networks, buckets, and everything else you create. Each project is a separate project in the underlying OpenStack cloud. Use projects to keep the resources of different teams or environments apart.

A subscription can have several projects, up to a limit. Every subscription has at least one project.

RegionCopy Anchor Link

A project lives in exactly one region, and every resource in it runs there. The top bar shows the region next to the project, for example Istanbul 1.

• Set by the subscription. You choose the region when you create a subscription. A project that you create runs in its subscription's region: the dialog for a new project shows the region, and you can't change it.
• Fixed. A project's region can't be changed. A request that names another region is refused. To work in another region, open a project there.
• Services per region. If a service isn't offered in your project's region, the console hides it. If you open one of its pages from a link, the console explains why it's not available.

For the regions, see Regions.

Roles and scopesCopy Anchor Link

You give people access by granting a role on a subscription, which covers all its projects, or on a single project. See Role assignments.

The built-in roles are Owner, Contributor, Reader, and Billing Operator. See Use built-in and custom roles.

Some things need a role granted on the subscription itself:

• Billing. Invoices, payments, and credits need a role on the subscription, because billing is measured per subscription. With a role on a project only, the cost figures cover that project only.
• Subscriptions and projects. Creating subscriptions and projects, and moving projects, need the Owner role on a subscription. An owner can also allow a member to create projects. See Manage subscriptions and projects.
• Quota. Moving quota between projects needs the Owner role on the subscription. See Quotas.

Manage subscriptions and projectsCopy Anchor Link

You create and delete subscriptions, and create, rename, move, and delete projects, from the scope picker in the top bar. See Manage subscriptions and projects.

Related tasksCopy Anchor Link

• Manage subscriptions and projects
• Subscriptions and currency
• Quotas
• Use built-in and custom roles