Comment 10 for bug 1885921

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Related fix merged to neutron-lib (master)

Reviewed: https://review.opendev.org/c/openstack/neutron-lib/+/832338
Committed: https://opendev.org/openstack/neutron-lib/commit/1dde6c24b777a86eb1a562a4ee2ca5019ac1e08a
Submitter: "Zuul (22348)"
Branch: master

commit 1dde6c24b777a86eb1a562a4ee2ca5019ac1e08a
Author: Pedro Henrique <email address hidden>
Date: Mon Mar 7 11:56:18 2022 -0300

    Add custom range parameters on port_range validator

    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