summaryrefslogtreecommitdiff
path: root/setup.cfg
Commit message (Collapse)AuthorAgeFilesLines
...
* Merge "Remove neutron-rootwrap-xen-dom0 script"Zuul2020-01-201-2/+0
|\
| * Remove neutron-rootwrap-xen-dom0 scriptBrian Haley2020-01-081-2/+0
| | | | | | | | | | | | | | It was marked for deprecation in the Pike release, enough time has passed so remove it. Change-Id: Ic3eda36e7e79726fb2f22aa015539c7d47ab7430
* | Merge "Complete dropping py27 support goal"Zuul2020-01-161-0/+1
|\ \
| * | Complete dropping py27 support goalNate Johnston2020-01-151-0/+1
| |/ | | | | | | | | | | | | This takes care of the last details for dropping py27 support by adding a proper min version of python in setup.cfg. Change-Id: I911469d46fccf13bc7ead7a103a7d6e4e0ede7c3
* | [OVN] Add OVN metadata entry pointsLucas Alvares Gomes2020-01-091-2/+2
| | | | | | | | | | | | | | | | | | This patch is migrating the entry points for the OVN metadata agent. Change-Id: I4062ade1231e29344a38cb69f32c3a0f198a7d03 Co-Authored-By: Daniel Alvarez <dalvarez@redhat.com> Related-Blueprint: neutron-ovn-merge Signed-off-by: Lucas Alvares Gomes <lucasagomes@gmail.com>
* | [OVN] Migrate the OVN mech driverRodolfo Alonso Hernandez2020-01-081-0/+1
|/ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This patch moves the OVN mech driver. Previous paths in networking-ovn tree: ./networking_ovn/ovn_db_sync.py -> ./neutron/plugins/ml2/drivers/ovn/mech_driver/ovsdb/ovn_db_sync.py ./networking_ovn/ml2/mech_driver -> ./neutron/plugins/ml2/drivers/ovn/mech_driver/mech_driver.py ./networking_ovn/common/maintenance.py -> ./neutron/plugins/ml2/drivers/ovn/mech_driver/ovsdb/maintenance.py Co-Authored-By: Amitabha Biswas <abiswas@us.ibm.com> Co-Authored-By: Aaron Rosen <aaronorosen@gmail.com> Co-Authored-By: Andrew Austin <aaustin@redhat.com> Co-Authored-By: Armando Migliaccio <armamig@gmail.com> Co-Authored-By: Arslan Qadeer <arslanq@xgrid.co> Co-Authored-By: Boden R <bodenvmw@gmail.com> Co-Authored-By: Brian Haley <bhaley@redhat.com> Co-Authored-By: Daniel Alvarez <dalvarez@redhat.com> Co-Authored-By: Dong Jun <dongj@dtdream.com> Co-Authored-By: Gal Sagie <gal.sagie@huawei.com> Co-Authored-By: Gary Kotton <gkotton@vmware.com> Co-Authored-By: Guoshuai Li <ligs@dtdream.com> Co-Authored-By: Han Zhou <zhouhan@gmail.com> Co-Authored-By: Hong Hui Xiao <xiaohhui@cn.ibm.com> Co-Authored-By: Ihar Hrachyshka <ihrachys@redhat.com> Co-Authored-By: Jakub Libosvar <libosvar@redhat.com> Co-Authored-By: John Kasperski <jckasper@us.ibm.com> Co-Authored-By: Kyle Mestery <mestery@mestery.com> Co-Authored-By: Lucas Alvares Gomes <lucasagomes@gmail.com> Co-Authored-By: Maciej Józefczyk <mjozefcz@redhat.com> Co-Authored-By: Miguel Angel Ajo <majopela@redhat.com> Co-Authored-By: Nirapada Ghosh <nghosh@us.ibm.com> Co-Authored-By: Numan Siddique <nusiddiq@redhat.com> Co-Authored-By: Richard Theis <rtheis@us.ibm.com> Co-Authored-By: Rodolfo Alonso Hernandez <ralonsoh@redhat.com> Co-Authored-By: Sean Mooney <work@seanmooney.info> Co-Authored-By: Terry Wilson <twilson@redhat.com> Co-Authored-By: venkata anil <anilvenkata@redhat.com> Co-Authored-By: xurong00037997 <xu.rong@zte.com.cn> Co-Authored-By: zhufl <zhu.fanglei@zte.com.cn> Related-Blueprint: neutron-ovn-merge Change-Id: I3ed2ff4008a3fed8534ee1eb42f0be2b6b779e83
* Merge "Allow to select subnets to publish DNS records"Zuul2019-12-201-0/+1
|\
| * Allow to select subnets to publish DNS recordsJens Harbott2019-12-141-0/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | As described in [0] a new attribute ``dns_publish_fixed_ip`` is added to subnets, allowing to specify directly whether DNS records should be published for this subnet. This overrides the previous behaviour that makes this decision based on various properties of the network that the subnet is contained in, see [1]. [0] https://launchpad.net/bugs/1784879 [1] https://docs.openstack.org/neutron/latest/admin/config-dns-int-ext-serv.html Change-Id: I14605ead2694d9e9422b3d7b519aed2e3c340e2a Partial-Bug: 1784879
* | [OVN] Import OVN Client, L3 and QoS related codeMaciej Józefczyk2019-12-141-0/+1
|/ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This patch moves the OVN Client, L3 and QoS related code: Previous paths in networking-ovn tree: ./networking_ovn/ml2/qos_driver.py -> neutron/services/qos/drivers/ovn/qos_driver.py ./networking_ovn/common/ovn_client.py -> neutron/plugins/ml2/drivers/ovn/mech_driver/ovsdb/ovn_client.py ./networking_ovn/l3/l3_ovn_scheduler.py -> neutron/scheduler/l3_ovn_scheduler.py ./networking_ovn/l3/l3_ovn.py -> neutron/services/ovn_l3/plugin.py Co-Authored-By: Amitabha Biswas <abiswas@us.ibm.com> Co-Authored-By: Andrew Austin <aaustin@redhat.com> Co-Authored-By: Anh Tran <anhtt@vn.fujitsu.com> Co-Authored-By: Armando Migliaccio <armamig@gmail.com> Co-Authored-By: Arslan Qadeer <arslanq@xgrid.co> Co-Authored-By: Boden R <bodenvmw@gmail.com> Co-Authored-By: Brian Haley <bhaley@redhat.com> Co-Authored-By: Cao Xuan Hoang <hoangcx@vn.fujitsu.com> Co-Authored-By: Chandra S Vejendla <csvejend@us.ibm.com> Co-Authored-By: Changxun Zhou <zhoucx@dtdream.com> Co-Authored-By: Daniel Alvarez <dalvarez@redhat.com> Co-Authored-By: Dong Jun <dongj@dtdream.com> Co-Authored-By: Doug Hellmann <doug@doughellmann.com> Co-Authored-By: Gary Kotton <gkotton@vmware.com> Co-Authored-By: Guoshuai Li <ligs@dtdream.com> Co-Authored-By: Han Zhou <zhouhan@gmail.com> Co-Authored-By: Ihar Hrachyshka <ihrachys@redhat.com> Co-Authored-By: Jakub Libosvar <libosvar@redhat.com> Co-Authored-By: John Kasperski <jckasper@us.ibm.com> Co-Authored-By: Kamil Sambor <ksambor@redhat.com> Co-Authored-By: Kevin Benton <kevin@benton.pub> Co-Authored-By: Kyle Mestery <mestery@mestery.com> Co-Authored-By: LIU Yulong <liuyulong@le.com> Co-Authored-By: Lucas Alvares Gomes <lucasagomes@gmail.com> Co-Authored-By: Maciej Józefczyk <mjozefcz@redhat.com> Co-Authored-By: Miguel Angel Ajo <majopela@redhat.com> Co-Authored-By: Na <nazhu@cn.ibm.com> Co-Authored-By: Numan Siddique <nusiddiq@redhat.com> Co-Authored-By: Richard Theis <rtheis@us.ibm.com> Co-Authored-By: Russell Bryant <rbryant@redhat.com> Co-Authored-By: Sławek Kapłoński <slawek@kaplonski.pl> Co-Authored-By: Terry Wilson <twilson@redhat.com> Co-Authored-By: Yunxiang Tao <taoyunxiang@cmss.chinamobile.com> Co-Authored-By: lzklibj <lzklibj@cn.ibm.com> Co-Authored-By: melissaml <ma.lei@99cloud.net> Co-Authored-By: reedip <rbanerje@redhat.com> Co-Authored-By: venkata anil <anilvenkata@redhat.com> Co-Authored-By: xurong00037997 <xu.rong@zte.com.cn> Co-Authored-By: zhufl <zhu.fanglei@zte.com.cn> Change-Id: I52bc2785d815b3f04efbda3b78a28861ca9e8fe1 Related-Blueprint: neutron-ovn-merge
* [OVN] Move OVN metadata agentLucas Alvares Gomes2019-12-091-0/+2
| | | | | | | | | | | | This patch imports the OVN metadata agent code from networking-ovn. Previous paths in networking-ovn tree: ./networking_ovn/agent/metadata -> ./neutron/agent/ovn/metadata ./networking_ovn/conf/agent/metadata -> ./neutron/conf/agent/ovn/metadata.py Change-Id: If0c46909ec0d83df1be98300badeb36753b1002b Related-Blueprint: neutron-ovn-merge Signed-off-by: Lucas Alvares Gomes <lucasagomes@gmail.com>
* [OVN] Move OVN commons to neutron treeMaciej Józefczyk2019-12-041-0/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Move OVN related commons to neutron tree. Previous paths in networking-ovn tree: ./networking_ovn/common/constants.py -> ./neutron/common/ovn/constants.py ./networking_ovn/common/exceptions.py -> ./neutron/common/ovn/exceptions.py ./networking_ovn/common/utils.py -> ./neutron/common/ovn/utils.py ./networking_ovn/common/hash_ring_manager.py -> neutron/common/ovn/hash_ring_manager.py ./networking_ovn/common/config.py -> ./neutron/conf/plugins/ml2/drivers/ovn/ovn_conf.py Co-Authored-By: Gal Sagie <gal.sagie@huawei.com> Co-Authored-By: Boden R <bodenvmw@gmail.com> Co-Authored-By: Daniel Alvarez <dalvarez@redhat.com> Co-Authored-By: Amitabha Biswas <abiswas@us.ibm.com> Co-Authored-By: Chandra S Vejendla <csvejend@us.ibm.com> Co-Authored-By: Babu Shanmugam <bschanmu@redhat.com> Co-Authored-By: Lucas Alvares Gomes <lucasagomes@gmail.com> Co-Authored-By: Terry Wilson <twilson@redhat.com> Co-Authored-By: Ramu Ramamurthy <ramu.ramamurthy@us.ibm.com> Co-Authored-By: Maciej Józefczyk <mjozefcz@redhat.com> Co-Authored-By: Gary Kotton <gkotton@vmware.com> Co-Authored-By: Andrew Austin <aaustin@redhat.com> Co-Authored-By: Miguel Angel Ajo <majopela@redhat.com> Co-Authored-By: Brian Haley <bhaley@redhat.com> Co-Authored-By: Dong Jun <dongj@dtdream.com> Co-Authored-By: xurong00037997 <xu.rong@zte.com.cn> Co-Authored-By: Rodolfo Alonso Hernandez <ralonsoh@redhat.com> Change-Id: Ib46bfdd14a150a324dbf28c6a50c839c5c824e35 Related-Blueprint: neutron-ovn-merge
* Stop testing python 2Brian Haley2019-10-251-5/+0
| | | | | | | | | Since it's no longer supported past Train, lets stop running the tests. Updated docs and made some pep8 code tweaks as well. Change-Id: I1c171ab906a3b4c66558163ad26947ebf710a276
* Merge "Agent - Conntrack Helper"Zuul2019-09-151-0/+1
|\
| * Agent - Conntrack HelperHarald Jensås2019-08-291-0/+1
| | | | | | | | | | | | | | Implements the L3 agent conntrack helper extension. Closes: #1823633 Change-Id: I21cc5683839bbb3fb8a649908080919c1557811d
* | Check mech driver connectivity during port bindingRodolfo Alonso Hernandez2019-09-111-0/+1
|/ | | | | | | | | | | | | | | | | | In [1] the concept of "connectivity" was introduced for the ML2 drivers. This parameter defines the mech driver connectivity type (layer 2, layer 3 only or legacy - not defined). The spec defined in the blueprint allows to spawn a VM with ports without IP addresses. As commented in the Nova spec [2], those ports can be bound only to "l2" drivers. [1] https://review.opendev.org/#/c/645645/ [2] https://review.opendev.org/#/c/641670/ bp boot-vm-with-unaddressed-port Related-Bug: #1821058 Change-Id: I438cbab43b45b5f7afc820b77fcf5a0e823d0eff
* Conntrack Helper - PluginHarald Jensås2019-08-291-0/+1
| | | | | | | | | | | | | | | Implements Conntrack Helper service plugin for conntrack helper resources. Supports create, update and delete conntrack helper for l3 routers. A new configuration option: [l3-conntrack-helpers]/allowed_conntrack_helpers introduced to allow the operator to configure CT helpers, and the helper protocol constraints. Related-Bug: #1823633 Depends-On: https://review.opendev.org/663446 Change-Id: I58193955261f50b18b1946261fe662da6b20f0f5
* fix NetworkSegmentRange OVO entry pointBoden R2019-06-061-1/+1
| | | | | | | | The NetworkSegmentRange entry point in the setup.cfg references an invalid package path to the corresponding OVO class. This patch fixes the package name to reflect the proper path. Change-Id: I228a159a9d3eca7021e3ba08d9ad40f9ff8329df
* Notify ironic on port status changesHarald Jensås2019-05-271-0/+1
| | | | | | | | | | | | | | | | This patch adds an ironic notifier that sends notifications to ironic endpoint /v1/events. The events are triggered by port updates and deletions. Only ports with vnic_type baremetal are honored. Story: 1304673 Task: 22263 Closes-Bug: #1828367 Implements: blueprint event-notifier-ironic Authored-By: Vasyl Saienko <vsaienko@mirantis.com> Co-Authored-By: Harald Jensås <hjensas@redhat.com> Co-Authored-By: Julia Kreger <juliaashleykreger@gmail.com> Change-Id: I0bb3187a88a7f20adb8c60e24945db159afb83f1
* Merge "Conntrack Helper - OVO and db script"Zuul2019-05-211-0/+1
|\
| * Conntrack Helper - OVO and db scriptHarald Jensås2019-05-201-0/+1
| | | | | | | | | | | | | | | | | | | | Implements the conntrack helper OVO and db layer code. - New object 'ConntrackHelper' - New db model - migration db script Related-Bug: #1823633 Change-Id: I0d9c039b260845b6544eccf63f5a2ffaa929120b
* | Use openstack-python3-train-jobs templateZhongShengping2019-05-201-0/+1
|/ | | | | | | | | | | | | | | | | | | | This goal is to implement the process set out in the 2018-10-24 Python Update Process TC resolution[1], for the Train cycle to ensure unit testing is in place for all of the Tested Runtimes for Train[2]. In practice, this generally means adding unit tests for Python 3.7 and dropping unit tests for Python 3.5. For Neutron, which already runs py36 and py37 unit tests it generally means switch to use the Zuul template openstack-python3-train-jobs for Train. Using this template will ensure that all projects that support Python3 will be tested against the agreed runtime versions, and make it easier to update them in future. [1]https://governance.openstack.org/tc/resolutions/20181024-python-update-process.html [2]https://governance.openstack.org/tc/reference/runtimes/train.html Change-Id: I41d232a10a40d97347566e189457d8044e3639db Depends-On: https://review.opendev.org/#/c/641878/
* Check in "_update_segmentation_id" that the mech_driver has an agentRodolfo Alonso Hernandez2019-04-241-0/+1
| | | | | | | | | | | | In [1] it is assumed that all mechanism drivers have an agent, but the mech driver API [2] doesn't enforce it. VIF types will be retrieved only from those mechanism drivers with an associated agent. [1]https://review.openstack.org/#/c/633165/20/neutron/plugins/ml2/plugin.py@814 [2]https://github.com/openstack/neutron-lib/blob/stable/stein/neutron_lib/plugins/ml2/api.py#L37 Change-Id: I5c334f31259871ed5251d5d4a2ba8cae36bd2355 Closes-Bug: #1824346
* Dropping the py35 testingGhanshyam Mann2019-04-151-1/+1
| | | | | | | | | | | | | | | | | All the integration testing has been moved to Bionic now[1] and py3.5 is not tested runtime for Train or stable/stein[2]. As per below ML thread, we are good to drop the py35 testing now: http://lists.openstack.org/pipermail/openstack-discuss/2019-April/005097.html [1] http://lists.openstack.org/pipermail/openstack-discuss/2019-April/004647.html [2] https://governance.openstack.org/tc/reference/runtimes/stein.html https://governance.openstack.org/tc/reference/runtimes/train.html Change-Id: I6cb8b66ce4b3e456a0e9ae534fd8168b49ac414f
* Drive binding by placement allocationBence Romsics2019-03-091-0/+1
| | | | | | | | | | | | | | | | | | | | | | Drive the choice of mechanism driver during binding as inferred from the resource provider allocated by nova and as told to neutron via the port's binding:profile. As discussed on a neutron qos irc meeting some time ago this patch introduces a new assumption on bind_port() implementations. That is an implementation of bind_port() in any mech driver supporting Guaranteed Minimum Bandwidth bind_port() must not have a non-idempotent side effect. Because the last binding level will be redone for a 2nd time with a narrowed down list of mechanism drivers. And if the 2nd call does not give the same result as the first all kind of weird things can happen. Change-Id: I2b7573ec6795170ce45a13d5d0ad7844fb85182d Depends-On: https://review.openstack.org/574781 Depends-On: https://review.openstack.org/635160 Partial-Bug: #1578989 See-Also: https://review.openstack.org/502306 (nova spec) See-Also: https://review.openstack.org/508149 (neutron spec)
* Support Network Segment Range CRUD as extensionsKailun Qin2019-03-071-0/+2
| | | | | | | | | | | | | | | | | | | | | 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
* Placement reporting service pluginBence Romsics2019-03-011-0/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This service plugin synchronizes ML2 mechanism driver agents' resource information to Placement. To use this service an agent must add 'resource_provider_bandwidths' to the 'configurations' field of its RPC heartbeat. It also may add 'resource_provider_inventory_defaults' to fine tune Placement inventory parameters. Again to use this service a mechanism driver must implement get_standrd_device_mappings() and allocate a UUID as mechanism driver property 'resource_provider_uuid5_namespace'. The synchronization is triggered by: * any new agent object in the DB * restart of an agent (via 'start_flag' in the RPC heartbeat) * if an agent's 'resources_synced' attribute is not True (None/False) The latter should autoheal transient errors of the synchronization process. That is if a sync attemp fails then we store resources_synced=False which triggers a sync retry at each new heartbeat message until a sync attempt finally succeeds and we can set resources_synced=True. Since this code functionally depends on ML2 we can also consider making it part of ML2, but at the moment it is a service plugin for better decoupling. Even if you load the service plugin the logic gracefully degrades for heartbeat messages not containing resource provider info. If needed the sync can be forced in multiple ways. First, if you restart an agent then the RPs belonging to that agent will be re-synced. You may also delete the agent by 'openstack network agent delete' and let the next heartbeat message re-create the agent object. On re-creation the RPs belonging to that agent will be re-synced. On the other hand a neutron-server restart does not trigger a re-sync in any way. Depending on the trade-off between the admin's needs to force re-syncs and the performance of (not absolutely necessary) Placement updates re-sync conditions may be further fine tuned. Example config for neutron-server: neutron.conf: [DEFAULT] service_plugins = placement Change-Id: Ia1ff6f7559ab77913ddb9c3b134420a401b8eb43 Co-Authored-By: Lajos Katona <lajos.katona@ericsson.com> Depends-On: https://review.openstack.org/586567 Partial-Bug: #1578989 See-Also: https://review.openstack.org/502306 (nova spec) See-Also: https://review.openstack.org/508149 (neutron spec)
* Merge "Upgrade check command - add support for 3rd party checks"Zuul2018-12-191-1/+2
|\
| * Upgrade check command - add support for 3rd party checksSlawek Kaplonski2018-12-181-1/+2
| | | | | | | | | | | | | | | | | | | | | | CLI command "neutron-status upgrade check" now can load checks from 3rd party and stadium projects using entry_points. Such additional checks should be available under "neutron.status.upgrade.checks" namespace in entry_points. Change-Id: I416abbcdd7b397ec6acd2827129d7a56095ea63d Story: 2003657
* | Merge "Update mailinglist from dev to discuss"Zuul2018-12-171-1/+1
|\ \
| * | Update mailinglist from dev to discussZhongShengping2018-12-121-1/+1
| | | | | | | | | | | | | | | | | | | | | openstack-dev was decomissioned this night in https://review.openstack.org/621258 Update openstack-dev to openstack-discuss Change-Id: I739ec6a4984df396b11b29f2d55f0d24fecab6eb
* | | Convert policy.json into policy-in-codeAkihiro Motoki2018-12-131-1/+6
|/ / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This commit introduces a framework for policy-in-code support in the neutron stadium and converts the existing policy.json in the neutron repository into the policy-in-code style. NOTES: 1) This commit tries not to change the existing policy behavior provided by the neutron repository even if there are some stale policies or policies to be defined in a neutron-related project. They should be clean up later in Stein release. 2) 'default' policy should be dropped from the default policies as all default policies should be defined in the code (as many projects which already completed policy-in-code do). However, dropping 'default' policy potentially affects policy behavior in neutron-related projects, so it needs to be visit carefully. Considering this, this commit decides to keep the 'default' policy. Partially Implements: blueprint neutron-policy-in-code Change-Id: I6a61079da4d4f5080ee32d640144e6bdb14735fa
* | [L3][QoS] Agent side router gateway IP rate limitLIU Yulong2018-12-011-0/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This patch implements the L3 agent side router gateway IP rate limit. For routers in centralized snat node (network node), the tc rules will be set on the corresponding device in router namespace: 1. Legacy and HA router, qrouter-namespace and qg-device 2. Dvr (edge) router, snat namespace and qg-device If gateway IP rate limit was set, then under the same router, all the VMs without floating IP will share the bandwidth. Partially-Implements blueprint: router-gateway-ip-qos Closes-Bug: #1757044 Change-Id: Ie92ff0d4df0e85ce71c7d50f34ea6ff973812af8
* | [L3][QoS] Neutron server side router gateway IP QoSLIU Yulong2018-12-011-0/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This patch enables to bind a QoS policy to the router gateway, then in L3 agent side SNAT traffic for the VMs without floating IPs can be limited under the policy bandwidth rules. This is suit for all kinds of L3 routers: DVR, DVR with SNAT HA, L3 HA and Legacy. API update router gateway json: { router": { "external_gateway_info": { ... "qos_policy_id": "policy-uuid" } } } Depends-On: https://review.openstack.org/#/c/567497/ Partially-Implements blueprint: router-gateway-ip-qos Closes-Bug: #1757044 Related-Bug: #1596611 Change-Id: I26e22bce7edd1f93b2ac0048b61b14f858938537
* | Add propagate_uplink_status to portHongbin Lu2018-11-291-0/+1
|/ | | | | | | | | | | | | | | | | | | | | | Introduce an attribute 'propagate_uplink_status' to port. This attribute can be implemented for VF port to indicate if the VF link state should follow the state of the PF. Note: ML2 extension driver loaded on request via configuration: [ml2] extension_drivers = uplink_status_propagation Other related patches: * neutron-lib: https://review.openstack.org/#/c/571821/ * tempest test: https://review.openstack.org/#/c/586719/ * OSC: https://review.openstack.org/#/c/586684/ * neutronclient: https://review.openstack.org/#/c/586712/ APIImpact Add 'propagate_uplink_status' attribute to 'port' resource Change-Id: Ie8260c332e24c1880f9f82e6b6dacca8415be842 Close-Bug: #1722720
* Merge "Add neutron-status upgrade check command framework"Zuul2018-10-301-0/+1
|\
| * Add neutron-status upgrade check command frameworkSlawek Kaplonski2018-10-251-0/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | This adds basic framework for neutron-status upgrade check commands. For now it has only "check_nothing" check implemented. Real checks can be added to this tool in the future. Depends-On: https://review.openstack.org/#/c/610061/ Change-Id: Ib08119e1bb8de80856edb6a39769d4bc9d98c587 Story: 2003657 Task: 26144
* | Introduce L3 agent extension for SNAT loggingNguyen Phuong An2018-10-171-0/+1
|/ | | | | | | | | This patch introduces SNAT logging extension for Neutron Packet Logging framework. Co-Authored-By: Kim Bao Long <longkb@vn.fujitsu.com> Partial-Bug: #1752290 Change-Id: I882b8e75525f51ef8b5b032fc89843ae904844e7
* Add PortForwarding to neutron.objects entrypoint.Wenran Xiao2018-09-261-0/+1
| | | | | Closes-bug: #1794406 Change-Id: Ifad26642d730456136dfa9177d1c9515fe5ec421
* Fix iptables metering driver entrypointHongbin Lu2018-08-091-1/+1
| | | | | Closes-Bug: #1786347 Change-Id: If1c276338cec0c199d8cc8d8f6385025a3bb5d25
* [agent side] L3 agent side Floating IP port forwardingZhaoBo2018-07-271-0/+1
| | | | | | | | | | | | | | | | | | | | | This patch contains the l3 agent extension and agent part code. This patch introduce a new l3 agent extension named "port_forwarding", to process the binding of the port forwarding resources, manage its own floatingip configuration on router interface and floatingip status. Currrently, we support all Neutron Router reference implementations. This extension uses the period router sync task and PortForwarding OVO rpc. * The main idea about this new extension is using the generic router sync rpc to maintain the host port forwarding resources, * For a single port forwarding create/update/delete, process it one by one in smaller scope for forbidding refresh the iptables with a larger scope frequently. Partially-Implements: blueprint port-forwarding Partial-Bug: #1491317 Change-Id: Ic56e67d428f6177099c285a9d1bccabc1e710f2b
* [server side] Floating IP port forwarding pluginZhaoBo2018-07-261-0/+1
| | | | | | | | | | | | | | | | | | | | | | | This patch implements the plugin. This patch introduces an new service plugin for port forwarding resources, named 'pf_plugin', and supports create/update/delete port forwarding operation towards a free Floating IP. This patch including some works below: * Introduces portforwarding extension and the base class of plugin * Introduces portforwarding plugin, support CRUD port forwarding resources * Add the policy of portforwarding The race issue fix in: https://review.openstack.org/#/c/574673/ Fip extend port forwarding field addition in: https://review.openstack.org/#/c/575326/ Partially-Implements: blueprint port-forwarding Change-Id: Ibc446f8234bff80d5b16c988f900d3940245ba89 Partial-Bug: #1491317
* expose objects as entry points in setup.cfgBoden R2018-05-241-0/+75
| | | | | | | | | | | | | We've already added support for pluggable (via entry points) object loading in neutron-lib with [1] This patch exposes the neutron.objects in setup.cfg using entry points so that consumers can start to use them via the API in [1] rather than directly import them from neutron. [1] https://review.openstack.org/#/c/553838/ Change-Id: I25ddd77c55f48997ff6131f232addb4c2e629804
* Refactor for L3 router QoS extensionsLIU Yulong2018-05-171-1/+1
| | | | | | | | | | | Move the l3 qos extensions to a separated folder, then we can move a following up router gateway IP QoS extension to it. And also extract some common code to a base class. Related-Bug: #1757044 Change-Id: I63cc9506caa80f889ad817444281a0ac31bc9418
* Remove deprecated IVS interface driverBrian Haley2018-04-261-1/+0
| | | | | | | This was marked deprecated in Queens for removal in Rocky, https://review.openstack.org/#/c/505401/ Change-Id: I77fa59ae1819e87ab8ccc1fa5f0db86de3b90e2e
* Follow the new PTI for document buildNguyen Hai2018-03-241-5/+0
| | | | | | | | | | | For compliance with the Project Testing Interface as described in: https://governance.openstack.org/tc/reference/project-testing-interface.html http://lists.openstack.org/pipermail/openstack-dev/2017-December/125710.html Remove the '[build_sphinx]' as described in: http://lists.openstack.org/pipermail/openstack-dev/2018-March/128594.html Change-Id: Id3d7065028b4c0831e6b5c2363b19626734817a3
* Merge "Include all rootwrap filters when building wheels"Zuul2018-03-081-11/+1
|\
| * Include all rootwrap filters when building wheelsJesse Pretorius2017-09-221-11/+1
| | | | | | | | | | | | | | | | | | | | | | | | The current method of specifying each rootwrap filter in the file list is prone to errors when adding or removing filters. Instead of relying on a manually maintained list this patch just includes all the files of the correct naming convention from the applicable folder. This is simpler and easier to maintain. Closes-Bug: #1718356 Change-Id: I7f8c55f63d1c5a85a6a92062e918426f7d2d3c35
* | [log] ovs fw logging implementationNguyen Phuong An2018-01-091-0/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | This patch implements ovs firewall logging driver for security group base discussed on the spec [1] and [2] [1] https://specs.openstack.org/openstack/neutron-specs/specs/pike/logging-API-for-security-group-rules.html [2] https://docs.google.com/presentation/d/1fteBesETsmA7CWV6wf1i2QKa7k8EHPpRjytj8Rzeb-A/edit#slide=id.p Change-Id: Ib8668dd25ee7c5000a6dafcc7db3dbc33ad190be Co-Authored-By: IWAMOTO Toshihiro <iwamoto@valinux.co.jp> Co-Authored-By: Yushiro FURUKAWA <y.furukawa_2@jp.fujitsu.com> Partially-implements: blueprint security-group-logging Related-Bug: #1468366
* | [L3][QoS] L3 agent side Floating IP rate limitLIU Yulong2017-12-201-0/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This patch implements the L3 agent side floating IP rate limit. For all routers, if floating IP has qos rules, the corresponding TC filters will be added to: 1. for legacy/HA router, the device is qg-device of qrouter-namespace, aka router gateway in network node. 2. for dvr (HA) router in compute node, the device is rfp-device, the namespace is qrouter-namespace. 3. for dvr (HA) router in network node, the device is qg-device in snat-namespace. Partially-Implements blueprint: floating-ip-rate-limit Change-Id: Ie8a5fe4ebaeccfb3998732dd972663c54542b5bf
* | [log]: Change entry point name of logging pluginNguyen Phuong An2017-12-191-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | The name ('logapi') seems redundant 'api' and it looks inconsistent with entry point name of logging agent extension ('log') and LoggingPlugin class[1]. So this patch change 'logapi' to 'log' to make it look consistent. [1] https://github.com/openstack/neutron/blob/master/neutron/services/logapi/logging_plugin.py#L27 Change-Id: I57d0b86823670a1dc5d116d98059993c802ef86c Partially-implements: blueprint security-group-logging Related-Bug: #1468366
View Lorry Controller Status