PAP and provider network APIs don't support using transit domain name and PAP name instead of UUID
Bug #1571067 reported by
Shahbaz Nazir
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
networking-plumgrid |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
- physical attachment point APIs only support UUID for transit_domain_id parameter support for using transit domain name should be added
- provider network APIs only support UUID of physical attachment point for --provider:
To post a comment you must log in.
Reviewed: https:/ /review. openstack. org/303600 /git.openstack. org/cgit/ openstack/ networking- plumgrid/ commit/ ?id=ef69311c5be 2b065a5f4a38fec 5042e99e34caec
Committed: https:/
Submitter: Jenkins
Branch: master
commit ef69311c5be2b06 5a5f4a38fec5042 e99e34caec
Author: Shahbaz Nazir <email address hidden>
Date: Fri Apr 8 12:59:32 2016 -0700
Adding support to use name instead of UUID for PAP and transit domain APIs
Previously physical- attacment- points and transit-domains API
extensions required UUIDs for identifying PAPs and transit domains
This patch adds support which allows use of names instead of UUIDs
for identifying Physical Attachment Points and transit domains
Closes-Bug: #1571067 55212856c277049 f84fe6da07d
Change-Id: Ic4aa5dbb69b053
Signed-off-by: Shahbaz Nazir <email address hidden>