hacking 3.0.x is really old. Let's bump it to the latest version
available.
This also fixes some errors detected but some rules are excluded now.
See the comments in tox.ini for further details.
Change-Id: I2565e5f5e791dfdd9bbc1890b35c413965d83626
As discussed during the Zed PTG (see [1]) , due to changed product
development priorities we expect the BFD related extensions not
to get implemented. This patch reverts all relevant changes.
Revert Exception for BFD: BfdMonitorInUse,
a3b564dabf
Revert BFD validator, d126257982
Revert Fix hostroute validation with BFD,
5ff14c63c8
Revert extension for adding bfd monitors to extraroutes,
eb2c8a3c97
Revert BFD api def, f8c5b72cc8
[1]: https://etherpad.opendev.org/p/neutron-zed-ptg#L111
Related-Bug: #1907089
Change-Id: Ia532e4aa6ba2ed9e5ba4db75a250293890d9019d
To maintain the behavior of port forwarding
validations that denies the port number 0 when
creating a new port forwarding rule for floating
IPs, we will need to extend the
'validate_port_range_or_none' validator to allow
us to define the acceptable port ranges when
validating a value.
This patch is one of a series of patches
to implement floating ip port forwarding with
port ranges.
The specification is defined in:
https://github.com/openstack/neutron-specs/blob/master/specs/wallaby/port-forwarding-port-ranges.rst
Change-Id: I0e11885e15616509942d60fbced3ff8e14cac654
Implements: blueprint floatingips-portforwarding-ranges
Related-Bug: #1885921
The _collect_duplicates uses a set for duplicates. This
does not work when the values in the list are dictionaries.
Instead of using a set, use a list and extend the condition to
only add to the list if seen and not already in dups.
Closes-Bug: #1956785
Change-Id: Iad627bcfb95699febd504d7dc7fc9e8a7d813a9e
Those new validators are used to validate extra_dhcp_opt's opt_name and
opt_value fields to not allow multi-line strings to be set there.
Related-Bug: #1939733
Change-Id: I4dc3a09847205a660dc966d8eabccb4946f9bbc6
When the change to add support for extended ethertypes was introduced,
one scenario for backwards compatibility was not addressed in the
validator: using the canonical string names for ethertypes. This was
previously supported in the original implementation, using 'IPv4' or
'IPv6' for example.
Since the list of canonical ethertype names is available from os-ken we
consume it from there, which adds an additional dependency for
neutron-lib.
Related-Bug: #1838473
Change-Id: I53c6538dfbeea9691d95c6c555f0c56ae13d1a33
Since the restriction on ethertypes is being raised so that ethertypes
other than IPv4 and IPv6 can be specified in security group rules, add a
validator to ensure that ethertypes will be a valid two octet value.
The ethertype handling is configurable so make sure the validator
handles both possible configuration alternatives: the original style
where only IPv4 and IPv6 are valid, and the new style where any valid
two octet number (or it's string equivalent) works.
Related-Bug: #1832758
Needed-By: https://review.opendev.org/670203
Change-Id: I900f370f1de20b5137f138e54c5eec2102f77cce
The routing table could not add information, because
the original method could not identify the invalid CIDR.
This patch modify the judgement method. It will help
the router working normally.
Co-Authored-By: Allain Legacy <Allain.legacy@windriver.com>
Change-Id: I4db2e35303492aeda7e14cf9d525cc9b4a54ac36
Closes-Bug: #1805991
Story: 2004567
Adds the API definitions for the 'sfc' and 'flow_classifier' API
extensions from networking-sfc.
Co-Authored-By: Thomas Morin <thomas.morin@orange.com>
Needed-By: I4958fb7b47050a76618183ab4f938622d95c8a0c
Change-Id: Id5aea04553b78dd17fca85de88cf076b42d24140
Messages fixed in this commit are wrapped at the end of other messages,
where the outer messages themselves have periods at the end. Thus the
extra periods of these messages should be removed to avoid duplication
in user facing messages.
An example for reference:
$ openstack firewall group rule create --source-port BEEF --protocol tcp
Invalid input for source_port. Reason: Invalid port: BEEF..
TrivialFix
Change-Id: I76bfed5a91cb569119e1e83ee3bf3917bb526e79
When supplying a subport for a trunk with segmenation_id 0, Neutron
reports the error message about subport.
This patch lets the segmentation_id 0 pass through.
Change-Id: I3d164c1a1af89d7de20d90b3a6c6dcf6e8a1415b
Closes-bug: 1718385
This patch rehomes the flavor extension API definition into neutron-lib
along with it's associated exceptions and validator. Please see the
release notes for some minor refactoring that's done as part of this
patch.
Change-Id: I0229a80bb168bac8dc0fa17fb2b06f1b140d27b4
* remove spurious comma in range definition for 'local_pref'
* add validator to allow a field to be an integer in a range or none
and use it for the local_pref parameter
* the port association 'routes' attribute can be updated
Needed-By: I263e1ee6cf4e1a91be91a4a78f4a160f64d33cc6
Change-Id: I7995209459d5efa020a5e6c6335f4116df7f9f3f
It used to accept an integer but it has been changed for
some reasons when migrating to neutron-lib.
For compatibility, it's better to keep the original behaviour.
After all, the original behaviour seems reasonable to me.
Closes-Bug: #1696682
Related-Bug: #1696389
Change-Id: I60e1a99780202de14522f592288d3a9af7a75592
Extension specific validators should be isolated from general
validators[1]. The existing validators are moved from
neutron_lib.api.validators to neutron_lib.api.validators.__init__
so that it doesn't affect existing consumers importing them.
[1]: https://review.openstack.org/#/c/459782/
Change-Id: I3434f9d7f504b78aca707e4fc8caad99c7af8dfc
Takashi Kajinami