Skip to main content
Keystone

Tenancy and multi-tenancy in Keystone

Contributors netapp-manini

NetApp Keystone uses the concepts of Tenant and Subtenant as hierarchical entities that own logical storage resources. The concept of multi-tenancy is also supported, where multiple tenants are tied to a partner or service provider. The entities partner and service provider are used interchangeably here.

Note In the context of Keystone, a single tenancy is a NetApp-operated model, while a multi-tenancy is a partner-operated model.
Tenants

A tenant is the primary billing entity defined in Keystone. Each customer that is onboarded into Keystone and holds a subscription to the services, exists as a Keystone tenant. The customer provides NetApp with a customer name and/or identifier for the purposes of onboarding tenants and tracking subscription dates and commitment terms.

In a multi-tenancy, a partner is a tenant/customer of NetApp in a Keystone environment. The partner, in turn, can bear multiple tenants or customers, who are linked to end customers/subtenants. In this model, tenants/subtenants are the customers of the service providers, and have no billing relationship with NetApp.

Subtenants

Keystone subtenants exist entirely within a parent tenant with a many-to-one relationship. Subtenants provide logical resource separation within a tenancy and are used as a basis for show-back reporting. All storage resources (that is file services, block storage, and object storage) belong to a subtenant.

tenancy arch

Subscription model in a NetApp-operated (single tenancy) environment

  • A subscription is created by NetApp admin or GSSC for a tenant and zone.

  • The subscription names are derived from the billing entity for which the tenant is subscribed.

  • In the subscription, the start-date and contract term are configured.

  • There can be only one active subscription for each tenant-zone

  • One subscription can have multiple rate plans and each rate plan corresponds to a service level.

  • Each rate plan has a committed capacity per service level.

  • Service levels can include:

    • Extreme

    • Extreme-Tiering

    • Performance

    • Performance-Tiering

    • Value

    • Data protection for each of the service levels

    • Advanced Data Protection for Extreme, Performance, Value

    • Storage objects

Subscription model in a multi-tenant environment

  • Service Providers are Keystone customers and have subscriptions as tenants. The subscriptions are based on:

    • Commitment per service level and zone

    • Charged on allocated capacity with 100TiB minimum

    • Burst charges apply for 100-120% of committed capacity

  • NetApp charges the providers monthly, as a part of their usual tenancy terms.

  • For a service level to be available to tenants, the service provider or partner should first have a Keystone in place for the service level.

  • The service provider creates tenant subscriptions per service level, zone, and flexible minimums.

  • Service providers can sell more capacity to their tenants than they have purchased from NetApp (oversubscription). Therefore, the capacity used by tenants is not limited by the capacity the service provider has subscribed to.

  • Tenants can use storage capacity over their subscribed amount, that is listed as 'burst' on usage reports.

  • Tenant usage reports are available to partners for viewing on a daily or monthly basis.

  • Tenants can create subscriptions for longer duration as compared to the corresponding Keystone subscription, but a warning message is displayed to the end customer during that activity.

  • Keystone subscription for a partner is configured by NetApp admins or GSSC. Management of Keystone subscription and tenant subscriptions is performed by a user with Partner admin role.

  • Users with the tenant admin roles can only view the tenant subscription (not partner's Keystone subscription). They can update the given subscription to change capacity and service level. They can raise service requests for additional subscriptions.

  • The partner admin can create another subscription either when the existing subscription is expired, or for a future date when the existing subscription is no longer valid. The start date for a new subscription must be greater than or equal to current end date.