As a ONAP developer, I would like to add multi-tenancy capabilities in policy components. So that multiple tenants can share the same installation of policy framework and still have the data separated on per tenant basis. And possibly have PDP engines on per tenant basis as well to avoid cross dependencies.

Some pre-work regarding the same has been done earlier here - https://wiki.onap.org/display/DW/Multi-tenancy+support+in+Policy+Framework

Following are the high level work items planned for it:

• Study and spikes to understand the current behaviour and desired behaviour for multi-tenancy.
• Design & architecture of the solution.
• Possibly work on bringing the AAA (Authentication, Authorization & Audit) aspects in policy components.
• Separate database instance between policy design & administration vs policy execution.
• Add capabilities in helm charts of policy components to deploy in multi-tenant mode.