openstack/tacker
Code Issues Proposed changes

Update release notes of multi tenant policy in LCM

Browse Source 
This patch adds a known limitation that non-admin users cannot
instantiate VNFs. Secondly, it should be noted in the feature
description that the current implementation does not fix this issue.

Implement: blueprint multi-tenant-policy
Change-Id: I54570e989a6cf8bb5d19a023b3c50561ed7657db
This commit is contained in:
Manpreet Kaur
2022-03-09 00:12:16 +05:30
parent f1fbcbb9b9
commit f62b87a574
1 changed files with 5 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
releasenotes/notes/support-multi-tenant-in-lcm-87c5d017c37c916f.yaml
View File

@@ -6,4 +6,8 @@ features:
Virtualized Network Function Packages (VNF packages), and Virtualized Virtualized Network Function Packages (VNF packages), and Virtualized
Network Function Lifecycle Management Interface (VNF LCM) related to Network Function Lifecycle Management Interface (VNF LCM) related to
ETSI NFV-SOL based VNF management concerning tenants. Only allows VNF ETSI NFV-SOL based VNF management concerning tenants. Only allows VNF
instantiation by VIM of the same tenant. instantiation by VIM of the same tenant. This feature does not address
the known issue of allowing non admin users to instantiate VNFs, it may
be addressed in a future release.
issues:
- A non admin user can not instantiate VNFs.