From 0ca6953194e1bc7d859aeedf66d00f6cb875c11d Mon Sep 17 00:00:00 2001 From: Brian Haley Date: Tue, 12 Sep 2023 12:28:55 -0400 Subject: [PATCH] Fix wrong indentation in release note Default-security-group-rules-added release note had some extra indentation, which rendered it with a "bar" in front of the list of items. Remove the two spaces. Also fixed other grammatical issues in the note. Trivialfix Change-Id: I5d4a2e3be9a86c29f75e131d677f288bfe3222d1 --- ...ty-group-rules-added-94a9ac6cdd1c538e.yaml | 30 +++++++++---------- 1 file changed, 15 insertions(+), 15 deletions(-) diff --git a/releasenotes/notes/Default-security-group-rules-added-94a9ac6cdd1c538e.yaml b/releasenotes/notes/Default-security-group-rules-added-94a9ac6cdd1c538e.yaml index c27baa10b8c..5e0f499e29c 100644 --- a/releasenotes/notes/Default-security-group-rules-added-94a9ac6cdd1c538e.yaml +++ b/releasenotes/notes/Default-security-group-rules-added-94a9ac6cdd1c538e.yaml @@ -1,23 +1,23 @@ --- features: - | - New API which allows to define own set of the security group rules used - automatically in every new ``default`` and/or custom security group created - for projects. + A new API which allows a cloud administrator to define their own set of + security group rules added automatically to every new ``default`` and/or + custom security group created for projects. upgrade: - | - During upgrade process set of 4 default security group rules will be created - in the Neutron database. Those rules are the same as default rules added to - every new security group up to now: + During the upgrade process, a set of four default security group rules will + be created in the Neutron database. Those rules are the same default + rules added to every new security group up to now: - * rule to allow all egress IPv4 traffic (for all default and custom - Security groups), - * rule to allow all egress IPv6 traffic (for all default and custom - Security groups), - * rule to allow all ingress IPv4 traffic from the same security group - (for default security group in each project), - * rule to allow all ingress IPv6 traffic from the same security group - (for default security group in each project). + * rule to allow all egress IPv4 traffic (for all default and custom + Security groups), + * rule to allow all egress IPv6 traffic (for all default and custom + Security groups), + * rule to allow all ingress IPv4 traffic from the same security group + (for default security group in each project), + * rule to allow all ingress IPv6 traffic from the same security group + (for default security group in each project). - Those rules can now be modified by cloud administrator using + Those rules can now be modified by a cloud administrator using the ``default-security-group-rules`` API.