d4022f62a0
As proposed in the RFE and then approved in the spec. The parameter 'remote_ip_prefix' in metering label rules has been deprecated. Its name expresses the opposite of what does when used, and the lack of documentation confuses people. Moreover, an alternative method has been proposed and approved to enable operators to create metering rules using both source and destination IP addresses. The parameter will be removed in future releases. Partially-Implements: https://bugs.launchpad.net/neutron/+bug/1889431 RFE: https://bugs.launchpad.net/neutron/+bug/1889431 Depends-On: https://review.opendev.org/#/c/746203/ Depends-On: https://review.opendev.org/#/c/744702/ Depends-On: https://review.opendev.org/#/c/743828/ Depends-On: https://review.opendev.org/#/c/746142/ Depends-On: https://review.opendev.org/#/c/746347/ Change-Id: Iba2b0d09fdd631f8bd2c3c951fd69b243deed652
8 lines
319 B
YAML
8 lines
319 B
YAML
---
|
|
deprecations:
|
|
- |
|
|
Deprecate the use of 'remote_ip_prefix' in metering label rules, and it
|
|
will be removed in future releases. One should use instead the
|
|
'source_ip_prefix' and/or 'destination_ip_prefix' parameters. For more
|
|
details, you can check the spec: https://review.opendev.org/#/c/744702/.
|