VPNaaS: Modify neutron API users to detect multiple local subnet feature
Bug #1515670 reported by
Paul Michali
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
neutron |
Fix Released
|
High
|
Akihiro Motoki |
Bug Description
In review of 231133, Akihiro mentioned follow up work for the neutron API consumers, so that Horizon can detect whether or not the new multiple local subnet feature, with endpoint groups, is available.
At the moment, multiple local subnet feature has been implemented in VPNaaS API, but API consumers need to try VPNaaS API to detect multiple local subnet feature is available or not. It is better to detect the feature without trying to call VPNaaS API.
The suggested approach is to add an extension which represents this feature.
Placeholder for that work.
Changed in neutron: | |
assignee: | nobody → Akihiro Motoki (amotoki) |
importance: | Undecided → High |
no longer affects: | neutron |
Changed in python-neutronclient: | |
importance: | Undecided → High |
assignee: | nobody → Akihiro Motoki (amotoki) |
Changed in neutron: | |
status: | New → Confirmed |
Changed in neutron: | |
milestone: | none → mitaka-2 |
Changed in neutron: | |
milestone: | mitaka-2 → mitaka-1 |
Changed in neutron: | |
milestone: | mitaka-1 → mitaka-2 |
Changed in neutron: | |
milestone: | mitaka-2 → mitaka-3 |
To post a comment you must log in.
I cant seem to figure out how to assign this to Akihiro. Maybe I don't have permissions.