Elastic Pools Across Parent and Child Tenancies

Oracle Cloud Infrastructure (OCI) Organization Management provides two types of tenancies:

• Parent: A tenancy that's associated with the primary funded subscription.
• Child: Tenancies that join an organization, whereby a parent tenancy manages the child's cost and governance. Child tenancies can either be created as entirely new tenancies, or, existing tenancies can be invited to join the same organization and to change your default subscription.

You can combine the OCI organization management with the benefits of elastic pools. An elastic pool can operate across tenancies, where the elastic pool leader is in the parent tenancy and the elastic pool member is in a child tenancy.

• When you create an elastic pool in a child tenancy, the elastic pool is only visible to the child tenancy. This means when you create an elastic pool in a child tenancy, the elastic pool cannot add members from the parent tenancy or from another child tenancy.

• There is no difference for elastic pool billing or capacity management when an elastic pool includes instances from one or more child tenancies. The pool members in the child tenancy are not billed individually (the pool leader is billed based on the pool shape).

• If a child tenancy is removed, that is the parent and child relationship is broken, all the pool members from the child tenancy become regular instances and do not belong to an elastic pool.

Prerequisites

To use an elastic pool across tenancies you must define OCI Identity and Access Management policies that allow an Autonomous AI Database instance in a child tenancy to join an elastic pool in the parent tenancy.

Consider the following cases:

• You want to allow a user in the parent tenancy to create an instance as a pool member in the child tenancy, or add an existing instance from the child tenancy as a pool member to an elastic pool in the parent tenancy. To do this, a user in the parent tenancy should have the following OCI Identity and Access Management policies:

  Policies needed in the parent tenancy:

  
  define tenancy ChildTenancy as ocid1.tenancy.oc1....
  endorse group ParentTenancyUserGroup to manage autonomous-databases in tenancy ChildTenancy
  allow group ParentTenancyUserGroup to manage autonomous-databases in tenancy

  Policies needed in the child tenancy:

  define tenancy ParentTenancy as ocid1.tenancy.oc1...
  define group ParentTenancyUserGroup as ocid1.group.oc1...
  admit group ParentTenancyUserGroup of tenancy ParentTenancy to manage autonomous-databases in tenancy

• You want to allow a user in the child tenancy to create an instance as a member of an elastic pool in the parent tenancy, or add an existing instance from the child tenancy as a pool member to an elastic pool in the parent tenancy. To do this, a user in the child tenancy should have the following OCI Identity and Access Management policies:

  Policies needed in the parent tenancy:

  define tenancy ChildTenancy as ocid1.tenancy.oc1....
  define group ChildTenancyUserGroup as ocid1.group.oc1...
  admit group ChildTenancyUserGroup of tenancy ChildTenancy to manage autonomous-databases in tenancy

  Policies needed in the child tenancy:

  define tenancy ParentTenancy as ocid1.tenancy.oc1...
  define group ParentTenancyUserGroup as ocid1.group.oc1...
  endorse group ChildTenancyUserGroup to manage autonomous-databases in tenancy ParentTenancy
  allow group ChildTenancyUserGroup to manage autonomous-databases in tenancy