Tacker should provide tenant id support for vnf creation
Bug #1488243 reported by
Sripriya
This bug affects 3 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| tacker |
Invalid
|
Low
|
Sripriya | ||
Bug Description
Request for Enhancement:
As an user, I need the tenant id option in vnf-create to land my VNF in a specific tenant. If the tenant_id attribute is not provided, the VNF lands in the 'service' tenant based on default configuration in tacker.conf file.
Tacker should offer both the existing dedicated "tacker" service tenant based deployment and the one asked in this RFE to honor the tenant-id passed in the vnf-create, perhaps using tacker.conf knob.
Special care need to be taken when dealing with Multi-VIM scenario.
| Changed in tacker: | |
| assignee: | nobody → Sripriya (sseetha) |
| description: | updated |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix proposed to tacker (master) | #1 |
| Changed in tacker: | |
| status: | New → In Progress |
| Changed in tacker: | |
| importance: | Undecided → Wishlist |
| Changed in tacker: | |
| importance: | Wishlist → Medium |
| tags: | added: mitaka-rfe rfe |
| Changed in tacker: | |
| importance: | Medium → Low |
| description: | updated |
| description: | updated |
| Changed in tacker: | |
| status: | In Progress → Invalid |
To post a comment you must log in.
Fix proposed to branch: master
Review: https:/