diff options
| author | Brian Haley <bhaley@redhat.com> | 2017-11-30 17:53:29 -0500 |
|---|---|---|
| committer | Brian Haley <bhaley@redhat.com> | 2019-07-15 22:35:49 -0400 |
| commit | 969e6abd20570ae64b3d1fd049da1521fa148b5c (patch) | |
| tree | f1d563ff95ac7a71be07b2c32e81db7f7c927aa1 /releasenotes | |
| parent | b41d7518c381a453a66f3c09d38752f85b57b7e0 (diff) | |
| download | python-openstackclient-969e6abd20570ae64b3d1fd049da1521fa148b5c.tar.gz | |
Support IPv6 addresses better
When adding a security group rule, if no IP address is given
we will use '0.0.0.0/0', but if the ethertype is IPv6 we will
leave it as None. Change this to be '::/0' to match what we
do for IPv4 - use the "any" address. The neutron server
treats them both the same when checking for duplicates.
Because there are most likely entries in the DB using None
for the IP, print them as '0.0.0.0/0' or '::/0' so it is more
obvious what address they are actually referring to.
Also change to display the Ethertype column by default
instead of with --long, since easily knowing IPv4 or IPv6
is useful.
Change-Id: Ic396fc23caa66b6b0034c5d30b27c6ed499de5a6
Closes-bug: #1735575
Diffstat (limited to 'releasenotes')
| -rw-r--r-- | releasenotes/notes/better-ipv6-address-suppport-security-group-rules-95272847349982e5.yaml | 15 |
1 files changed, 15 insertions, 0 deletions
diff --git a/releasenotes/notes/better-ipv6-address-suppport-security-group-rules-95272847349982e5.yaml b/releasenotes/notes/better-ipv6-address-suppport-security-group-rules-95272847349982e5.yaml new file mode 100644 index 00000000..6cac67cf --- /dev/null +++ b/releasenotes/notes/better-ipv6-address-suppport-security-group-rules-95272847349982e5.yaml @@ -0,0 +1,15 @@ +--- +features: + - | + Security group rules can now be filtered by Ethertype in + ``security group rule list`` using ``--ethertype`` with either + ``ipv4`` or ``ipv6`` as an argument. +upgrade: + - | + Security group rule listings now have the ``Ethertype`` field displayed + by default to more easily differentiate between IPv4 and IPv6 rules. + In addition, the ``IP Range`` field of a security group will be + changed to ``0.0.0.0/0`` for IPv4 and ``::/0`` for IPv6 if no + value is returned for the address, based on the Ethertype field of + the rule. For further information see + [Bug `1735575 <https://bugs.launchpad.net/bugs/1735575>`_] |