Description of Use Case / Requirement:
Some components are currently missing functionalities to allow ONAP to be used as a true multi-tenant platform where:

Some resources can be shared between tenants, while other ones can be restricted to specific tenants / groups

Tenants are isolated from one another and cannot impact each other, both at design-time and at runtime

Several instances of some runtime components can run simultaneously and be managed by different user groups

Overview: https://wiki.onap.org/display/DW/Multi-tenancy+in+ONAP

Owners (one of these should be the Assignee - use @ notation):

Link to HLD/LLD (if any):

The initial details of this are in this could be found under here:
https://wiki.lfnetworking.org/display/LN/2020+April+Technical+Event+Schedule?preview=/34605773/34606235/Guilin%20Proposed%20Requirements%20-%20Multi-tenancy%20v2.2.pdf

Dependency Relationships with Other Projects:
As defined in the sheet
https://wiki.onap.org/display/DW/Guilin+Impact+View+per+Component?src=jira

Project Impact (Test Only (TO), Code (C)):
As defined in the sheet
https://wiki.onap.org/display/DW/Guilin+Impact+View+per+Component?src=jira

Support Status for each Affected Project (Supported (S); Partially Supported (P); Not Supported (N)):
Note: for any affected projects labeled 'P' or 'N', please document the resulting gaps.

SDC : Bell, Amdocs (S)
SO: Bell, Huawei (S)
AAI: Bell, Amdocs, Huawei (S)
Policy : Bell (P)
preview=/34605773/34606235/Guilin%20Proposed%20Requirements%20-%20Multi-tenancy%20v2.2.pdf
CDS & SDNC : Bell (S)

Integration Leads (use @ notation):

Company Engagement:
Bell, Huawei, Amdocs

Project wise :