openstack/neutron
Code Issues Proposed changes
Files
b09b44608b1e5b787c686c6ce52bb37480fb5129
neutron/neutron/objects
History
Kailun Qin 563a536d02 Support Network Segment Range CRUD as extensions 
This patch adds the support for network segment range CRUD. Subsequent
patches will be added to use this network segment range on segment
allocation if this extension is loaded.

Changes include:
- an API extension which exposes the segment range to be administered;
- standard attributes with tagging support for the new resource;
- a new service plugin "network_segment_range" for the feature
  enabling/disabling;
- a new network segment range DB table model along with operation
  logic;
- Oslo Versioned Objects for network segment range data model;
- policy-in-code support for network segment range.

Co-authored-by: Allain Legacy <Allain.legacy@windriver.com>

Partially-implements: blueprint network-segment-range-management
Change-Id: I75814e50b2c9402fe6776229d469745d7a72290b
2019-03-07 08:20:30 +00:00
..
db
remove the neutron.db._model_query module
2019-01-25 08:55:25 -07:00
extensions
Tag mechanism supports resources with standard attribute
2017-07-25 08:14:04 +09:00
logapi
[OVO] Switch to use own registry
2017-11-22 17:44:22 +01:00
plugins
[OVO] Switch to use own registry
2017-11-22 17:44:22 +01:00
port
Add propagate_uplink_status to port
2018-11-29 19:33:16 +00:00
qos
remove neutron.common.exceptions
2019-02-01 14:35:00 -07:00
__init__.py
Use dirname in object recursive import
2017-04-20 04:35:10 -07:00
address_scope.py
[OVO] Switch to use own registry
2017-11-22 17:44:22 +01:00
agent.py
New agent attribute: resources_synced
2019-02-21 13:45:15 +01:00
auto_allocate.py
[OVO] Switch to use own registry
2017-11-22 17:44:22 +01:00
base.py
Fix slow SG api calls when limiting fields
2019-02-21 15:44:27 -07:00
common_types.py
Support Network Segment Range CRUD as extensions
2019-03-07 08:20:30 +00:00
flavor.py
[OVO] Switch to use own registry
2017-11-22 17:44:22 +01:00
floatingip.py
Integration of Floating IP OVO
2017-12-04 19:30:02 +09:00
ipam.py
[OVO] Switch to use own registry
2017-11-22 17:44:22 +01:00
l3_hamode.py
[OVO] Switch to use own registry
2017-11-22 17:44:22 +01:00
l3agent.py
[OVO] Switch to use own registry
2017-11-22 17:44:22 +01:00
metering.py
[OVO] Switch to use own registry
2017-11-22 17:44:22 +01:00
network_segment_range.py
Support Network Segment Range CRUD as extensions
2019-03-07 08:20:30 +00:00
network.py
Use RBACBaseObject OVO in neutron/db/rbac_db_mixin.py
2018-11-08 13:41:36 +00:00
port_forwarding.py
Fix pylint R1714 (consider-using-in) refactor messages
2019-02-21 21:11:34 +00:00
ports.py
Make port binding attempt after agent is revived
2018-10-22 18:43:33 +02:00
provisioning_blocks.py
[OVO] Switch to use own registry
2017-11-22 17:44:22 +01:00
quota.py
Allow objects to opt in new engine facade
2018-02-09 04:07:34 +00:00
rbac_db.py
Bump pylint version to one that supports python3.7
2019-02-21 13:22:26 +00:00
rbac.py
Use RBACBaseObject OVO in neutron/db/rbac_db_mixin.py
2018-11-08 13:41:36 +00:00
README.rst
Objects: Add README for neutron/objects directory tree
2016-10-07 15:12:20 +00:00
router.py
Use Router OVO in external_net_db
2018-02-08 14:42:29 +00:00
securitygroup.py
Fix slow SG api calls when limiting fields
2019-02-21 15:44:27 -07:00
servicetype.py
[OVO] Switch to use own registry
2017-11-22 17:44:22 +01:00
stdattrs.py
Allow objects to opt in new engine facade
2018-02-09 04:07:34 +00:00
subnet.py
remove the neutron.db._model_query module
2019-01-25 08:55:25 -07:00
subnetpool.py
Allow objects to opt in new engine facade
2018-02-09 04:07:34 +00:00
tag.py
remove the neutron.db._model_query module
2019-01-25 08:55:25 -07:00
trunk.py
Allow objects to opt in new engine facade
2018-02-09 04:07:34 +00:00

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).