Recently we closed some of the gaps between ML2/OVS and ML2/OVN,
like for example:
* Support for the QoS DSCP,
* Support for the Layer 3 IPs QoS,
* Fix bugs [1] and [2] related to the OVN DNS resolution.
This patch updates documented gaps by removing those points from the
gaps list.
It also adds some links to the WIP patches for other of the gaps on that
list.
[1] https://bugs.launchpad.net/neutron/+bug/1951816
[2] https://bugs.launchpad.net/neutron/+bug/1950686
Change-Id: I0e670ef0a87300182ba83f350a84d28bf8d31eb9
This reverts commit bce27811dfea634118fdb609289ac70c8d4a6854.
Reason for revert: neutron-fwaas has maintainers so the documentation should be available.
Due to changes since the original deletion commit the following changes
were added:
* Add note that OVN is not yet supported
* Remove note that Horizon support is not available
Change-Id: I1a739ee045b49e9b44283c28f95b1accc8a1e37f
Added "Open Flow processing considerations" in the OVS firewall
driver page. This section describes the [OVS] configuration option
"openflow_processed_per_port". A script to meassure the Open Flow
rule processing time is provided.
Related-Bug: #1934917
Change-Id: Id4936b6d36abb6edc250aaf1cbc7e9af3fd0fae5
The existing example had an implicit overlap between the host network
and some tenant network, use a different network for the host.
Peering network resized to /24 because usually we would have several
network nodes on it instead of creating each their own transfer/peering
network.
Diagrams adjusted accordingly with omnigraffle.
PNGs reexported with 160% size to approximate the previous ones.
Router IPs in Diagrams adjusted to reflect documentation.
Peering Network IPs added to Peering Session Box.
Change-Id: I8778df02330196a8999afd3bbf9a3b87f0e14f7b
While the focus of the routed provider networks documentation
is on the Neutron side of things, this document provides a useful
location to point at relevant Nova configuration.
This reference relates to the Nova scheduler and ensuring that
instance move operations don't result in instances being scheduled
to hosts which do not have access to the required network(s).
Change-Id: Idd7382bd38d70383107d2997205ff880bede8d96
It has been suggested in the Neutron CI meeting to include a section in
the documentation advicing against blind rechecks. It turns out that
such section already exists. What this change does is to move the
section to the first level of the contributors guide, to make it more
visible. This change also improves some wording and adds some examples
of proper recheck comments.
Change-Id: Ib0a00d13a28f98b0a0f26c7233365d04453db4e0
Based on discussions during the Zed PTG (see [1]) mark Prefix Delegation
as experimental.
Add warning to cfg option ipv6_pd_enabled and to IPv6 documentation's
PD section that the feature has low test coverage, and dibbler is
concluded (the tool used for notifing Neutron that a prefix was changed)
see: [2].
[1]: https://etherpad.opendev.org/p/neutron-zed-ptg#L208
[2]: https://github.com/tomaszmrugalski/dibbler#project-status
Related-Bug: #1916428
Change-Id: Ia712eb6f5b6f947aeab89ba7c018771eb4104e37
Noticed a typo while reading the docs, fixed other grammatical
issues while I was here.
Trivial-fix
Change-Id: I9d62281e095688bcbcb1fbab3d1cd5101ae7ad37
The validation is intended mostly for tests and don't make much sense
when running the migration in production because likely there are
already running workloads. This patch changes the default to False so
migration validation must be explicitly asked for.
Change-Id: I5470f61a5e0b55bf682526208c3f57dc0ca6ffd5
Signed-off-by: Jakub Libosvar <libosvar@redhat.com>
tripleo-ansible-inventory stopped working in Wallaby. However, TripleO
now stores the needed ansible-inventory on the undercloud filesystem.
This patch switches from dynamic generation of the Ansible inventory to
use of the already existing inventory file. Fortunately, the format of
the file remained the same as the generated one, so no other changes in
parsing are required.
Closes-Bug: #1966099
Change-Id: I3bdf878617fbe962d56ebb66d59ae7edeb9b7c38
Signed-off-by: Jakub Libosvar <libosvar@redhat.com>
Added support for filtering the QoS rule type list command.
Two new filter flags are added:
- all_supported: if True, the listing call will print all QoS rule
types supported by at least one loaded mechanism driver.
- all_rules: if True, the listing call will print all QoS rule types
supported by the Neutron server.
Both filter flags are exclusive and not required.
Depends-On: https://review.opendev.org/c/openstack/neutron-lib/+/827533
Closes-Bug: #1959749
Change-Id: I41eaab177e121316c3daec34b309c266e2f81979
Table 59 will be used for pps limitation, the pipeline change is:
all original flows with ``goto table 60`` will be changed to
``goto table 59``, while table 59 has a default rule is goto
table 60. Then we can add pps flows to table 59 for all ports.
Basic limit pipeline is:
Ingress: packets get into br-int table 0, before send to table 60,
in table 59, check the destanation MAC and local_vlan ID, if the
dest is resident in this host, do the meter pps action and send
to table 60.
Egress: match src MAC and in_port, before send to table 60,
in table 59, do the meter pps action and send to table 60.
Why table 59? Because for ovs-agent flow structure, all packets
will be send to table 60 to do next actions such as security group.
Between table 0 and table 60, there are tables for ARP poison/spoofing
prevention rules and MAC spoof filtering. We want similar security
checks to take effect first, so it can drop packets before filling
our limit queues (pps limitation based on data forwarding queue).
And we do not want packets go through the long march of security group
flows, in case of performance side effect when there are large amount
of packets try to send, so limit it before goto security group flows.
Partially-Implements: bp/packet-rate-limit
Related-Bug: #1938966
Related-Bug: #1912460
Change-Id: I943f610c3b6bcf05e2e752ca3b57981f523f88a8
Read the chassis bandwidth configuration (stored in the "Chassis"
registers) only once, in the maintenance worker. The SB synchronizer
will call the OVN client Placement extension
"read_initial_chassis_config" method.
This new approach changes how the Placement information is stored. The
Placement extension does not store anymore a local cache of the
resource providers. Instead of this, in future patches, when this
information is required, the Placement extension will retrieve this
information from the SB DB, reading the content from the "Chassis"
registers and parsing the values.
Partial-Bug: #1578989
Change-Id: I160b1dda85596277125c532ea4ce4df8e4d25b63
Dashboard urls syntax changed after the latest Gerrit upgrades. This
change fixes the urls to the correct latest syntax in the
documentation.
Change-Id: I8883eac81c6db4d6bcd96d08c072d8378b07e6e6
