Add profile-tenant binding support to n1kv
Bug #1496663 reported by
Saksham Varma
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| networking-cisco |
Fix Committed
|
Undecided
|
Saksham Varma | ||
Bug Description
Add the ability to restrict a tenant's access to network and policy profiles. If the profiles are in a restricted mode, tenants other than admin should be able to use either the default profiles or the ones that the admin tenant permits for their use.
| Changed in networking-cisco: | |
| assignee: | nobody → Saksham Varma (sakvarma) |
| status: | New → In Progress |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix merged to networking-cisco (master) | #1 |
| Changed in networking-cisco: | |
| status: | In Progress → Fix Committed |
| Changed in networking-cisco: | |
| milestone: | none → 2.0.0 |
To post a comment you must log in.
Reviewed: https:/
Committed: https:/
Submitter: Jenkins
Branch: master
commit 24310bad0de9eea
Author: Saksham Varma <email address hidden>
Date: Mon Sep 14 12:11:01 2015 -0700
Add profile-tenant binding support to n1kv
This adds the ability to restrict a tenant's access to
network and policy profiles. If the profiles are in a
restricted mode, tenants other than admin can use either
the default profiles or the ones that the admin tenant
permits for their use.
This also adds resource extensions for network profile
and policy profile bindings, that are consumed by the
openstack-
Closes-Bug: 1496663
Change-Id: I6877b25ac60784