This patch moves the BGP service plugin, agent, driver, and
tests out of the neutron repository and into the
neutron-dynamic-routing repository.
Partially-Implements: blueprint bgp-spinout
Partial-Bug: #1560003
Co-Authored-By: vikram.choudhary <vikram.choudhary@huawei.com>
Change-Id: I80ea28a51d7b18e67d6ed4cd2da22520f950300f
This patch adds OSLO config framework required by
neutron-dynamic-routing repository for defining configuration
parameters.
Below changes are done as part of this patch-set:
- Added OSLO config framework.
- PEP8 changes for genconfig check.
Change-Id: Id3db0e9c5943ce913f5b2cca8d05a9ade37b3f68
Implements: blueprint bgp-spinout
Partial-Bug: #1560003
This patch restructures existing documents for better user
experience.
Below changes are done as part of this patch-set:
- Re-structured/Reworded existing documents.
- Identified and added dummy documents for required devrefs.
Implements: blueprint bgp-spinout
Partial-Bug: #1560003
Change-Id: I71d9f6107bca165d72b6f6e710ac6e0e6108fcf9
This patch adds alembic DB migration framework required by
neutron-dynamic-routing repository for defining new data
models to realize BGP dynamic routing functionality in neutron.
Below changes are done as part of this patch-set:
- Added new alembic migration framework.
- PEP8 changes for alembic migration check.
Change-Id: I395ca9541bceda40bbc0c0870e58c18231ba44e9
Implements: blueprint bgp-spinout
Partial-Bug: #1560003
This patch-set prepares the basic code structure with all
the tools required for running static and unit tests.
Note: All the imported code from the seed repo is being removed
temporarily and will be added after the required re-factoring
needed as per the new repo in the subsequent patch-sets.
Co-Authored-By: Ryan Tidwell <ryan.tidwell@hpe.com>
Implements: blueprint bgp-spinout
Partial-Bug: #1560003
Change-Id: I9bff3d916279c4f335b309e7a2c2e943ac6f6cde
Tempest provides decorator for checking if extension
is enabled. Refactored tests to use decorator instead
of manually checking enabled extensions.
Depends-on: Ied13e52bf78afe571f7243e93005bf5c68fe44db
Change-Id: I341d8b85a7cf0c49d66da79ac8e87271e185486e
* Detect neutron.i18n import (neutron._i18n is recommended)
* Check builtins _ usage
* 'builtins = _' in tox.ini is no longer required.
* Introduce hacking rule doctest framework.
Newly added check_builtins_gettext() hacking check takes
token as argument. It is not a good idea to pass a tokenized
line manually. Instead it is reasonable to use docstring based
tests used in hacking repo.
Change-Id: Ib7464658fc4c8a6f1b03af6ab46f0bd3ee0bfb18
Some standalone plugins, such as networking-ovn, are expecting
to store provider network information in neutron database, but
we have no table, like other extensions do, for provider
network extension defined.
This patch moves NetworkSegment table out of the ML2 code tree.
The API methods to operate segments are also moved, but stub
methods are still kept in the ml2 db API.
Co-Author: Miguel Lavalle <malavall@us.ibm.com>
Change-Id: I2c4f78fce591486ded63252af13fc0c60d02a3e8
Partially-Implements: blueprint routed-networks
This patch adds the front end and back end implementation of QoS DSCP.
Associated patches that are dependent on this one:
* python-neutronclient: https://review.openstack.org/#/c/254280
* openstack-manuals: https://review.openstack.org/#/c/273638
* API Guide: https://review.openstack.org/#/c/275253
* Heat:
* Spec: https://review.openstack.org/#/c/272173
* QoSDscpMarkingRule resource: https://review.openstack.org/#/c/277567
* Fullstack tests: https://review.openstack.org/#/c/288392/
APIImpact - The API now supports marking traffic egressing from a VM's
dscp field with a valid dscp value.
Co-Authored-By: Nate Johnston <nate_johnston@cable.comcast.com>
Co-Authored-By: Victor Howard <victor.r.howard@gmail.com>
Co-Authored-By: Margaret Frances <margaret_frances@cable.comcast.com>
Co-Authored-By: James Reeves <james.reeves5546@gmail.com>
Co-Authored-By: John Schwarz <jschwarz@redhat.com>
Needed-By: I25ad60c1b9a66e568276a772b8c496987d9f8299
Needed-By: I881b8f5bc9024c20275bc56062de72a1c70c8321
Needed-By: I48ead4b459183db795337ab729830a1b3c0022da
Needed-By: Ib92b172dce48276b90ec75ee5880ddd69040d7c8
Needed-By: I4eb21495e84feea46880caf3360759263e1e8f95
Needed-By: I0ab6a1a0d1430c5791fea1d5b54106c6cc93b937
Partial-Bug: #1468353
Change-Id: Ic3baefe176df05f049a2e06529c58fd65fe6b419
No config generator hooks should ever be registered with a name that
belongs to another project. In this case, using oslo.middleware.cors
means that *every other project* that loads the middleware gets neutron's
defaults when the generator is run on a system with everything installed
(such as a dev box with devstack). Use the name neutron instead, to
ensure that the defaults are only set when neutron's sample config and
documentation are being generated.
Change-Id: I6a8c7d44b9db9325003ff2fdb667b0ced7739e96
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
Python 3 deprecated the logger.warn method, see:
https://docs.python.org/3/library/logging.html#logging.warning
so we prefer to use warning to avoid DeprecationWarning.
Closes-Bugs: #1529913
Change-Id: Icc01ce5fbd10880440cf75a2e0833394783464a0
Co-Authored-By: Gary Kotton <gkotton@vmware.com>
tempest_fixtures is used exclusively in Tempest and Neutron,
therefor I don't think it makes sense to move it in to tempest.lib.
I'd rather copy it in to the Neutron repo.
Change-Id: Ibb52e2cae3f1af1569a04123c43ebc4d125e326d
Related-bug: #1555356
Introduce calls to collect host routes for floating IP's in a
DVR-aware way. When a floating IP is associated through a
distributed router, the next-hop for the floating IP is announced
as the floating IP agent gateway port on the corresponding host.
Change-Id: I654e4d2496e19c011653eedb87c9b6026f801e9f
Implements: blueprint bgp-dynamic-routing
DocImpact: Neutron BGP should have docs created for the feature
This patch adds RPC calls to the BGP speaker service plugin. This enables
the service plugin to notify the appropriate BGP dynamic routing agents
(bgp_dragent) when tenants add router gateway ports, router interfaces,
associate/disassociate floating IP's, and when and admin binds/unbinds
a gateway network to a BGP speaker. Compatible with centralized routers,
distributed routers not supported.
Partially-Implements: blueprint bgp-dynamic-routing
Co-Authored-By: vikram.choudhary <vikram.choudhary@huawei.com>
Change-Id: Ide76f9fdfba228000ddfa41a1168e77d21e92d9f
Change Ic2d4cea4f11222fc7b45eb378cfc32974c1be9b6
removed the service_client module and replaced it
with rest_client. This updates our code to reflect
that.
Change-Id: I5f6b0de632703eac6b6f05ae48c44d511f1fda5e
Closes-Bug: #1554362
In order to give users and operators more flexibility in
annotating the purpose of various Neutron resources, this patch
adds a description field limited to 255 chars to all of the
Neutron resources that reference the standard attribute table.
The resource that reference the table are the following:
security_group_rules, security_groups, ports, subnets,
networks, routers, floatingips, subnetpools
This patch adds a description table related to standard attributes
and migrates over the existing security group description to the new
table as well.
Co-Authored-By: James Dempsey <jamesd@catalyst.net.nz>
APIImpact
DocImpact: Adds a description field to all resources outline in
commit message.
Closes-Bug: #1483480
Change-Id: I6e1ef53d7aae7d04a5485810cc1db0a8eb125953
Currently, neutron core resources (like net, subnet, port and subnetpool)
do not save time-stamps upon their creation and updation. This
information can be critical for debugging purposes.
This patch introduces a new extension called "timestamp" extending existing
the neutron core resources to allow their creation and modification times
to be record. Now this patch add this resource schema and the functions which
listen db events to add timestamp fields.
APIImpact
DocImpact: Neutron core resources now contain 'timestamp' fields like
'created_at' and 'updated_at'
Change-Id: I24114b464403435d9c1e1e123d2bc2f37c8fc6ea
Partially-Implements: blueprint add-port-timestamp
This patch contains code for looking in the Neutron DB and identifying
next-hops for tenant networks and floating IP's. These queries use the
centralized router as the next-hop and ignore host routes attached to
a distributed router.
Partially-Implements: blueprint bgp-dynamic-routing
Co-Authored-By: vikram.choudhary <vikram.choudhary@huawei.com>
Change-Id: If08d6595d9bc657a7ecfb487e8df40860837d200
Introduce a generic mechanism to allow the user to set tags
on Neutron resources. This patch adds the function for "network"
resource with tags.
APIImpact
DocImpact: allow users to set tags on network resources
Partial-Implements: blueprint add-tags-to-core-resources
Related-Bug: #1489291
Change-Id: I4d9e80d2c46d07fc22de8015eac4bd3dacf4c03a
The default values needed for neutron's implementation of cors
middleware have been moved from paste.ini into the configuration
hooks provided by oslo.config. Furthermore, these values have been
added to neutron's default configuration parsing. This ensures
that if a value remains unset in neutron.conf, it will be set to use
sane defaults, and that an operator modifying the configuration
file will be presented with a default set of necessary sane headers.
Change-Id: I327d1d7ce50dd4a20d781e6251a5af81c57e6ca1
Closes-Bug: 1551836
By default oslo CFG sets the default value as None. There is no
need to specifically do this.
The patch also moves the RYU_BGP_SPEAKER_DRIVER to the devstack
settings file.
TrivialFix
Change-Id: Ic33871a0a42fa9a5e5af3158532ecdad9817e5ab
steve.ruan