Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Support Multi-tenancy in ONAPĀ 

Requirement:

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyREQ-340

SO:

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keySO-3029

...

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keySDC-3188

CDS:

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyCCSDK-2537

Policy:

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyPOLICY-2717

Abstract

In order to deal with E2E service orchestration across different network domains, there are ONAP components that need to be logically centralized, such as the Inventory or entry-point of service orchestration or use of common models for services and resources.

...

  • If controllers are distributed, Policy executors need to fetch which controller instance to be leveraged for a given resource from A&AIĀ 
    • Or, we use K8S's namespace/DNS - but this has limitations and would inconsistent with SO's way of dealing with this.

Image Added

SDC


A&AI

An example for A&AI multi-tenancy is the use of owning-entity concept - which defines which group of people owns specific A&AI resources or services.

...