| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
Change-Id: I4e4d819e271495fa650a275246df8925ef84fd25
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This patch updates list of the Neutron's stadium's projects lieutenants
and the list of the bugs' contact persons.
In details this patch:
- sets Rodolfo Alonso Hernandez as contact person for db and qos
related issues,
- adds Oleg Bondarev as "loadimpact" bugs,
- removes Matt Riedemann as contact person for "logging" bugs,
- sets PTL/Drivers team as conctact for "troubleshooting" related bugs,
It also sets Lajos Katona as "Testing" lieutenant.
Finally it removes networking-ovn and neutron-fwaas from the list of
stadium projects and removes tag "fwaas" from the list of bug tags.
Neutron-fwaas was deprecated and isn't part of the stadium since long
time and networking-ovn is now one of the Neutron in-tree drivers.
Change-Id: Id4b928e077ed684c67d4b5054f12653d63f70788
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
By adding this library to the doc requirements file, tox will install
it limiting the upper version according to
"requirements/upper-constraints.txt".
"pyroute2" is called in tox doc job as mentioned in [1]. Since version
0.6.0, the library structure changed. To keep backwards compatibility,
all modules are imported from the main namespace. As reported in the
referred bug, the library "mitogen" must be installed first.
In stable releases that use older "pyroute2" versions, this library is
not needed but this patch should enforce the upper library version.
Related-Bug: #1928913
[1]https://github.com/openstack/neutron/blob/2a4074918c248adf84b0afa404d30c18710da4b2/doc/source/conf.py#L33-L40
Change-Id: I0cf458f4532d313e593a943653e8310b93ac1e9c
|
|/
|
|
| |
Change-Id: I1485948b251e451895f8e773cc34be1221cf650d
|
|
|
|
|
|
|
|
|
| |
Since I67504a37b0fe2ae5da3cba2f3122d9d0e18b9481 Nova supports attaching
neutron ports backed by PCI devices. So the limitation can be removed
from the doc.
Closes-Bug: #1925433
Change-Id: I44e573bd55e3631901d782d6d65987a58ca3e4fb
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| | |
It was deprecated in the Wallaby cycle due to lack of maintainers.
This patch removes networking-midonet as an stadium project from the
official Neutron docs.
Change-Id: I5cd3da80d78d98ec4b2a49574efc0ec075e75959
|
|\ \
| |/
|/| |
|
| |
| |
| |
| |
| | |
Depends-On: https://review.opendev.org/c/openstack/neutron-lib/+/785590
Change-Id: Iaf360714f25defecbc5dd28515fba75e8c966b59
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
OVN driver is one of the in-tree drivers since couple of cycles already
so we can update links to the OVN driver's docs in the
general_feature_support_matrix and provider_network_support_matrix
documents now.
Change-Id: If8887ce0786ab1d86d331e1781a36cc34c897c6d
|
|/
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Until the migration to the new native "nftables" API is completed,
Neutron Linux Bridge mechanism driver can work with:
- The legacy binaries ("iptables", "ip6tables", "arptables" and
" ebtables").
- The "nftables" legacy API tools. "ipset" tool is not compatible
with "nftables" and must be disabled.
Closes-Bug: #1915341
Related-Bug: #1508155
Related-Bug: #1922892
Change-Id: I10ef4e9124ba8f243680acde506eebc586c2f9a7
|
|
|
|
|
|
|
| |
These dashboards are checked in CI meeting and should always point to
latest and previous stable releases.
Change-Id: Ied2a0d9adbc33b9a41820667d961c1ce9fe72656
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| | |
Add documentation for Routed Provider Networks.
Co-Authored-By: Lucas Alvares Gomes <lucasagomes@gmail.com>
Closes-Bug: #1865889
Change-Id: Ie9b7ba52b5b9e93480f22d6863038bea23a19123
|
|/
|
|
|
|
|
|
|
| |
The undercloud node user is configurable in TripleO and isn't always set
to heat-admin. This patch introduces an environment variable for cases
where user is different.
Change-Id: If65925ded1b5df2bfdcfba50445ff7d821c725d8
Signed-off-by: Jakub Libosvar <libosvar@redhat.com>
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
FWaaS was retired with [1], so it's time to remove the misleading
references from doc as well.
[1]: https://review.opendev.org/c/openstack/neutron-fwaas/+/735829
Change-Id: Ic098263b7450c09308eeff4ef6dd2f8097c0a449
|
|/
|
|
|
|
|
|
|
|
|
| |
neutron-tempest-plugin single node scenario jobs were switched
to use L3HA routers by default in [1] and this patch reflects that
change in our docs.
[1] https://review.opendev.org/721805
Depends-On: https://review.opendev.org/721805
Change-Id: Ib3c6be059dc4f3e62a9c5d25588d44ed4a3df971
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This is patchset 1 of 2 for OVN driver handling of security-group-logging.
It includes the design documentation for this feature.
Changed a few lines in doc/source/admin/ovn/features.rst, so the extensions
are sorted in alphabetical order.
Related-Bug: 1914757
Partially-implements: https://review.opendev.org/c/openstack/neutron-specs/+/203509
Change-Id: I95d57613cef3b6892d3a0dd5705e2e8f3386a3a2
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Client: https://review.opendev.org/c/openstack/python-openstackclient/+/775045
Tempest tests: https://review.opendev.org/c/openstack/neutron-tempest-plugin/+/773274
Allow sharing of address groups via RBAC mechanism
Change-Id: I9d9e2bd4add5bb6fa4105352bfda739340932571
|
|\ \ |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Before that patch it was possible to send ICMPv6 packets like e.g.
neutron_lib.constants.ICMPV6_TYPE_MLD_QUERY,
neutron_lib.constants.ICMPV6_TYPE_RS,
neutron_lib.constants.ICMPV6_TYPE_NS,
neutron_lib.constants.ICMPV6_TYPE_NA
And that could cause some security issues as instance could advertise
that it owns IPv6 address which really don't belong to it.
Now rules in table=71 which allows that traffic are "per mac/ipaddress"
and are allowed only for fixed ips allocated to port and port's
allowed_address_pairs.
Closes-Bug: #1902917
Change-Id: I4749fdc6a6cabd253b971bf4010ff76f5593c59c
|
| |/
|/|
| |
| |
| |
| |
| |
| | |
ovn-controller man page has moved to [1]
[1] http://www.ovn.org/support/dist-docs/ovn-controller.8.html
Change-Id: I528eb847ee956d1939abe2cb9e32450a4e271999
|
|\ \ |
|
| | |
| | |
| | |
| | |
| | | |
Change-Id: I5a8451370646d8d149c03283a2180e325a2d7b1c
Closes-bug: #1914522
|
|\ \ \
| |_|/
|/| | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The job neutron-tempest-with-neutron-lib-master is mostly to check if
current neutron changes will work fine with some changes done in
neutron-lib.
It isn't really needed to run it on all patches and can be rune on
demand by running experimental queue if that is needed.
This patch also removes job neutron-ovn-tempest-ovs-master from the
experimental queue as we already have there similar multinode job.
As job neutron-ovn-tempest-ovs-master wasn't used anywhere, this patch
also removes its definition.
Finally this patch improves ci_scenario_jobs document and adds there
info about experimental queue and what is there currently.
Change-Id: I0fc4ffd5db2673cefcd01307555d1a3900bb12e8
|
|\ \ \
| |/ /
|/| | |
|
| | |
| | |
| | |
| | | |
Change-Id: I2ffee0c8dcfd9911681ba5dd0e16b6d3505a9271
|
|\ \ \
| |/ /
|/| | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Tell something about the config option ``explicitly_egress_direct``
since there is something not so much clear for users now.
Change-Id: I1c046d8140f93d9a8cd9e0bc43d3494e4f6a1ce7
|
|\ \ \ |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Security group rule quota is per-project, not per-group.
Change-Id: Icc8119fa7d5451ee6efceeaad1371274c2846d67
|
|\ \ \ \ |
|
| | |_|/
| |/| |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
In neutron CI queues we were running tempest-slow-py3 and
tempest-ipv6-only jobs which are defined in tempest repository and runs
all tests, e.g related to Swift or Cinder.
This patch defines new jobs: "neutron-tempest-slow-py3" and
"neutron-tempest-ipv6-only" which inherits from the tempest jobs but
disables Cinder and Swift services.
Additionally "neutron-tempest-ipv6-only" job now runs only
"integrated-networking" tox_envlist.
Change-Id: Icd376c144e1993ca84890c76743fda4196662d9b
|
|\ \ \ \ |
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
As per the community goal of migrating the policy file
the format from JSON to YAML[1], we need to do two things:
1. Change the default value of '[oslo_policy] policy_file''
config option from 'policy.json' to 'policy.yaml' with
upgrade checks.
2. Deprecate the JSON formatted policy file on the project side
via warning in doc and releasenotes.
Also replace policy.json to policy.yaml ref from doc and tests.
[1]https://governance.openstack.org/tc/goals/selected/wallaby/migrate-policy-format-from-json-to-yaml.html
Change-Id: I0dbb8484e749e645627756e88ec79c1b26a6414a
|
| |/ / /
|/| | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
With the new engine facade in place, a context session can execute
one single transaction at once. Nested transactions are no longer
supported.
This patch also changes db related examples in the "retries" document
that they uses engine facade.
Partially-Implements blueprint: enginefacade-switch
Change-Id: I978a24c3b30c2bb0a3ea6aa25ebf91ca5c58b8c9
Co-authored-by: Slawek Kaplonski <skaplons@redhat.com>
|
| | | |
| | | |
| | | |
| | | | |
Change-Id: Iff9f415ff4e472cfb03e69c69bf7f2d9fc439abd
|
|\ \ \ \ |
|
| | |/ /
| |/| |
| | | |
| | | |
| | | |
| | | |
| | | | |
Move out tempest related things from TESTING.rst to tempest.rst.
It also gives some basics on how to debug tempest in zuul and locally.
Change-Id: I46c282c865bfdf5e88e26ea8fc31b26cdd3f6b2e
|
|\ \ \ \ |
|
| |/ / /
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Document the existing QoS extensions provided (for L3 router and
OVN L3) and the QoS rules supported (bandwidth limit).
Change-Id: Ifafb327f5b2e2a4b9e46e07cf896e29f9f24f8a4
|
|\ \ \ \ |
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
As talked about in the CI meeting, some manual steps were not mentioned
and could cause some issues later (like running stable stadium CI
against master neutron). All steps should now be listed.
Also update some release names and URLs in the document
Change-Id: I06a5a1ba0523befbc136920efde3e717ef822856
|
|\ \ \ \ \
| |_|/ / /
|/| | | | |
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
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
|
| |_|/ /
|/| | |
| | | |
| | | | |
Change-Id: I218a7a2584a8669a0da0a7ff328985e12f8ec92f
|