Comment 4 for bug 1471316

My thinking here is that the user possibly doesn't know that a default subnetpool has been set by the admin, and therefore it shouldn't be up to the user to change their API calls to get the behaviour they expect. It was my understanding that the default pools would be used only when the user has requested a subnet without expressing a cidr preference - therefore not breaking existing applications making use of the neutron api.

My concern is that all legacy applications (including devstack) are going to need to be updated to reflect the need to specify subnetpool_id=None, otherwise they will break or at least not function as expected where a default pool value has been set.