Public bug reported: After adding address scope in Mitaka, the openstack can create subnetpool with specified address scope, and in the same address scope, we can not create the overlapping subnetpool.
As we also known, the BGP depends on these two features to get the advertised tenant networks. So in order to get better subnet management, we'd better create subnet from the subnetpool and add the address scope. In order to backward compatibilities, the subnetpool can be created without address scope, see below, the address_scope_id is empty. yangyubj@yang-devstack-ubuntu-1604:/opt/stack/logs$ neutron subnetpool-show 07f8a928-afb3-4ba8-ba46-cb70c6d9c073 +-------------------+--------------------------------------+ | Field | Value | +-------------------+--------------------------------------+ | address_scope_id | | | created_at | 2016-06-01T09:32:52 | | default_prefixlen | 24 | | default_quota | | | description | | | id | 07f8a928-afb3-4ba8-ba46-cb70c6d9c073 | | ip_version | 4 | | is_default | True | | max_prefixlen | 32 | | min_prefixlen | 8 | | name | shared-default-subnetpool | | prefixes | 10.0.0.0/8 | | shared | True | | tenant_id | 21734c4383284cf9906b7fe8246bffb1 | | updated_at | 2016-06-01T09:32:52 | +-------------------+--------------------------------------+ And the user can be continuous to create overlapping subnetpool with the empty address scope id. If the address scope id is specified, the customer can not create the overlapping subnetpool. So IMO, for the best practice, we can not allow the user to create overlapping subnetpool when the address scope id is empty. ** Affects: neutron Importance: Undecided Assignee: Yang Yu (yuyangbj) Status: New ** Changed in: neutron Assignee: (unassigned) => Yang Yu (yuyangbj) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1600691 Title: Should not create overlapped subnetpool in one tenant Status in neutron: New Bug description: After adding address scope in Mitaka, the openstack can create subnetpool with specified address scope, and in the same address scope, we can not create the overlapping subnetpool. As we also known, the BGP depends on these two features to get the advertised tenant networks. So in order to get better subnet management, we'd better create subnet from the subnetpool and add the address scope. In order to backward compatibilities, the subnetpool can be created without address scope, see below, the address_scope_id is empty. yangyubj@yang-devstack-ubuntu-1604:/opt/stack/logs$ neutron subnetpool-show 07f8a928-afb3-4ba8-ba46-cb70c6d9c073 +-------------------+--------------------------------------+ | Field | Value | +-------------------+--------------------------------------+ | address_scope_id | | | created_at | 2016-06-01T09:32:52 | | default_prefixlen | 24 | | default_quota | | | description | | | id | 07f8a928-afb3-4ba8-ba46-cb70c6d9c073 | | ip_version | 4 | | is_default | True | | max_prefixlen | 32 | | min_prefixlen | 8 | | name | shared-default-subnetpool | | prefixes | 10.0.0.0/8 | | shared | True | | tenant_id | 21734c4383284cf9906b7fe8246bffb1 | | updated_at | 2016-06-01T09:32:52 | +-------------------+--------------------------------------+ And the user can be continuous to create overlapping subnetpool with the empty address scope id. If the address scope id is specified, the customer can not create the overlapping subnetpool. So IMO, for the best practice, we can not allow the user to create overlapping subnetpool when the address scope id is empty. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1600691/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp