c613ede9fa
This change is needed for enabling floating IP's on routed networks. To be able to create a subnet that spans all segments of a routed network, a special subnet service type of 'network:routed' is used to denote a network that can span all segments of a routed network. To create floating IP's on a routed network, the subnet must be created with a service_type of 'network:routed'. After the subnet has been created, floating IP's can be allocated and associated as before. See the design spec https://review.opendev.org/#/c/486450/ for reference. One caveat for this approach is that it requires the underlying infrastructure to be aware of and able to route /32 host routes for the floating IP. This implies that in practice, use of the 'network:routed' service type should be done in conjunction with one or both of the following: 1. Third-party SDN backend that handles this service type in its own way 2. neutron-dynamic-routing and the BGP service plugin for announcing the appropriate next-hops for floating IP's. This is compatible with DVR and non-DVR environments. Depends-On: Ibde33bdacba6bd1e9c41cc69d0054bf55e1e6454 Change-Id: I9ae9d193b885364d5a4d90538880d8e9fbc8df74 Co-Author: Thomas Goirand <zigo@debian.org> Partial-Bug: #1667329 |
||
|---|---|---|
| .. | ||
| db | ||
| extensions | ||
| logapi | ||
| plugins | ||
| port | ||
| qos | ||
| README.rst | ||
| __init__.py | ||
| address_scope.py | ||
| agent.py | ||
| auto_allocate.py | ||
| base.py | ||
| conntrack_helper.py | ||
| flavor.py | ||
| floatingip.py | ||
| ipam.py | ||
| l3_hamode.py | ||
| l3agent.py | ||
| metering.py | ||
| network.py | ||
| network_segment_range.py | ||
| port_forwarding.py | ||
| ports.py | ||
| provisioning_blocks.py | ||
| quota.py | ||
| rbac.py | ||
| rbac_db.py | ||
| router.py | ||
| securitygroup.py | ||
| servicetype.py | ||
| stdattrs.py | ||
| subnet.py | ||
| subnetpool.py | ||
| tag.py | ||
| trunk.py | ||
README.rst
Neutron Objects
Directory
This directory is designed to contain all modules which have objects definitions shipped with core Neutron. The files and directories located inside of this directory should follow the guidelines below.
Structure
The Neutron objects tree should have the following structure:
- The expected directory structure is flat, except for the ML2 plugins. All ML2 plugin objects should fall under the plugins subdirectory (i.e. plugins/ml2/gre_allocation).
- Module names should use singular forms for nouns (network.py, not networks.py).