Comment 5 for bug 1832526

This RFE and the spec / blueprints mentioned in #2, #3 and #4 refer to different problems. The problem solved and implemented by #2, #3 and #4 was enabling a cloud admin to administer through the API the range of segments that are assigned for the creation of tenant networks. Prior to that solution, the assignment of those ranges was done using config options in neutron.conf.

This RFE refers to the edge computing scenarios defined in https://wiki.openstack.org/wiki/Edge_Computing_Group/Edge_Reference_Architectures. In those deployment scenarios, there are sites known as "Small Edge", which don't have the API components of the control plane. They only have the Neutron OVS agent and the Nova compute agent. In other words, the virtual networks instantiated those "Small Edge" sites will be created through an API that exists in a regional or centralized site.

Today, a Neutron network is assumed to be a single L2 domain that spans the entire deployment. As discussed during the PTG in Denver, the edge computing scenarios require us to be able to create networks that span only one segment that exist in a specific "Small Edge" site. In other words, each "Small Edge" site will have its own networks: This will entail:

1) Changes to the API, to be able to create a network associated with a "Small Edge"
2) Changes to the backend mechanism, to be able to instantiate a network only in a specific "Small Edge"