a37378e8d5
Problem Description =================== As users create and update theirs floating ip rules, the reason behind those rules might get lost throughout time. Moreover, in an environment with many people writing rules, it is important to track down the reason behind each one of the rules created/added in a floating IP port forwarding configuration. The addition of a description field would allow operators to determine the reason why a rule was created and help the users to know if the existence of a rule is still reasonable. Proposed Change =============== To address the described scenario, we propose to create a new “description” field in the Neutron’s Floating IP port forwarding rules API JSON. This new field will be a nullable String containing the description/reason why this new port forwarding rule is being created. Change-Id: If98a70011b187d2143a660f1f281ab197d21eb4d Implements: blueprint portforwarding-description Closes-Bug: #1850818
5 lines
157 B
YAML
5 lines
157 B
YAML
---
|
|
features:
|
|
- |
|
|
Add a new field ``description`` in floating ip portforwardings that
|
|
can be used to help users to manage/find easily theirs rules. |