Discrepancy between API and CLI on how to enable PD
Bug #1513894 reported by
Baodong (Robert) Li
This bug affects 3 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
neutron |
Won't Fix
|
Medium
|
Unassigned | ||
python-neutronclient |
Won't Fix
|
Undecided
|
Unassigned | ||
python-openstackclient |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
Checking api/v2/
Changed in neutron: | |
importance: | Undecided → Medium |
status: | New → Triaged |
Changed in neutron: | |
status: | Triaged → Confirmed |
tags: | added: ipv6 |
Changed in neutron: | |
assignee: | nobody → John Davidge (john-davidge) |
Changed in python-openstackclient: | |
assignee: | nobody → Reedip (reedip-banerjee) |
To post a comment you must log in.
Looking at http:// docs.openstack. org/mitaka/ networking- guide/adv- config- ipv6.html I wonder whether this is really an issue. The usual procedure seems to be to set
ipv6_pd_enabled = True
in neutron.conf which will have the side effect of making the "--use_ default_ subnetpool" option to automatically set the subnetpool_id to "prefix_ delegation" .
So what would be the use case where for subnet creation one would need to set the pool_id explicitly instead of using --use_default_ subnetpool?