Reviewed: https://review.openstack.org/282021 Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=26e268db7923c4deb4c0de32066874b44d441042 Submitter: Jenkins Branch: master
commit 26e268db7923c4deb4c0de32066874b44d441042 Author: Carl Baldwin <[email protected]> Date: Thu Feb 18 19:27:30 2016 +0000 Add use_default_subnetpool to subnet create requests This follows up [1] by adding an extension to allow requesting the default subnet pool explicitly through the API thus restoring the convenience that was lost by removing the automatic default subnetpool fallback behavior. ApiImpact [1] https://review.openstack.org/#/c/279378/ Change-Id: Ifff57c0485e4727f352b2cc2bd1bdaabd0f1606b Related-Bug: #1545199 Closes-Bug: #1547705 ** Changed in: neutron Status: In Progress => Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1547705 Title: There is no way to use the default subnet pool without first looking it up Status in neutron: Fix Released Status in python-neutronclient: In Progress Bug description: With the recent resolution of [1], which removed the automatic fallback to the default subnet pool, the only way to use the default subnetpool is to manually look it up and specify it on the command land. This made things much less convenient for the end user. While discussing [1], I agreed to provide a new extension to make this convenient again. The extension should be added to the server side to allow any API consumers to make use of it. [1] https://bugs.launchpad.net/neutron/+bug/1545199 To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1547705/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : [email protected] Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
