This was a compromise we made toward the end of Kilo. The subnetpools resource was implemented as a core resource, but for purposes of Horizon interaction and a lack of another method for evolving the Neutron API we deliberately added a shim extension. I believe this was done with a couple other “extensions” like VLAN transparent networks. I don’t think we want to remove the shim extension.
-Ryan From: gong_ys2004 [mailto:gong_ys2...@aliyun.com] Sent: Monday, August 31, 2015 9:45 PM To: openstack-dev Subject: [openstack-dev] [neutron] subnetallocation is in core resource, while there is a extension for it? Hi, neutron guys, look at https://github.com/openstack/neutron/blob/master/neutron/extensions/subnetallocation.py, which defines an extension Subnetallocation but defines no extension resource. Actually, it is implemented in core resource. So I think we should remove this extension. I filed a bug for it: https://bugs.launchpad.net/neutron/+bug/1490815 Regards, yong sheng gong
__________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
