Support Multi-tenancy in ONAP
Requirement:
| Jira | ||||||
|---|---|---|---|---|---|---|
|
SO:
| Jira | ||||||
|---|---|---|---|---|---|---|
|
...
| Jira | ||||||
|---|---|---|---|---|---|---|
|
CDS:
| Jira | ||||||
|---|---|---|---|---|---|---|
|
Policy:
| Jira | ||||||
|---|---|---|---|---|---|---|
|
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.
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.
...