Neutron client CLI association is redundant
Bug #1496905 reported by
Édouard Thuleau
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
networking-bgpvpn |
Fix Released
|
Medium
|
Thomas Morin |
Bug Description
We should have a unique CLI command to associate a resource to a bgpvpn that will simplify the CLI for next resources which can be associated (ie. router, port).
neutron bgpvpn-associate <bgpvpn-uuid> [--network <net-uuid> | --router <router-uuid> | --port <port-uuid>]
description: | updated |
Changed in bgpvpn: | |
status: | New → Confirmed |
importance: | Undecided → Medium |
Changed in bgpvpn: | |
milestone: | none → liberty |
assignee: | nobody → Thomas Morin (tmmorin-orange) |
Changed in bgpvpn: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
Reviewed: https:/ /review. openstack. org/225118 /git.openstack. org/cgit/ openstack/ networking- bgpvpn/ commit/ ?id=1930dfac77d ecc8723742908dc cbada1e4f25674
Committed: https:/
Submitter: Jenkins
Branch: master
commit 1930dfac77decc8 723742908dccbad a1e4f25674
Author: Thomas Morin <email address hidden>
Date: Fri Sep 18 14:09:42 2015 +0200
Neutronclient: one command for all associations
With this change, the association cli becomes:
neutron bgpvpn-associate <bgpvpn-uui> --network <net-uuid>
(this change also adds 'networks' in the list of
fields shown by the bgpvpn-list command, which is
very useful)
Change-Id: If5ff5a43815b29 a983199047e8521 1bc0f4e3136
Closes-Bug: 1496905