summaryrefslogtreecommitdiff
path: root/releasenotes/notes
diff options
context:
space:
mode:
authorDean Troyer <dtroyer@gmail.com>2019-09-09 11:48:28 -0500
committerDean Troyer <dtroyer@gmail.com>2019-09-10 23:48:32 -0500
commitcb0c20b23c564dc6b260492923aef58ee66620d9 (patch)
tree89cc8e9a9b7db380d4473569293b205938ebf91a /releasenotes/notes
parentb7b124f32745eb4063ded5f2a175d559fba04dc9 (diff)
downloadpython-openstackclient-cb0c20b23c564dc6b260492923aef58ee66620d9.tar.gz
Update release table for Train and 4.0.0
Also clean up some docs and release notes. Change-Id: I73feec747ca1bd12be5e5700c9ca608ed3a8b2c2 Signed-off-by: Dean Troyer <dtroyer@gmail.com>
Diffstat (limited to 'releasenotes/notes')
-rw-r--r--releasenotes/notes/add-server-migrate-with-host-4884a71903c5c8a9.yaml2
-rw-r--r--releasenotes/notes/better-ipv6-address-suppport-security-group-rules-95272847349982e5.yaml5
-rw-r--r--releasenotes/notes/bug-1716789-abfae897b7e61246.yaml15
-rw-r--r--releasenotes/notes/volume-v3-default-0ffa9bebb43b5057.yaml2
4 files changed, 8 insertions, 16 deletions
diff --git a/releasenotes/notes/add-server-migrate-with-host-4884a71903c5c8a9.yaml b/releasenotes/notes/add-server-migrate-with-host-4884a71903c5c8a9.yaml
index dd974ff0..8da704ac 100644
--- a/releasenotes/notes/add-server-migrate-with-host-4884a71903c5c8a9.yaml
+++ b/releasenotes/notes/add-server-migrate-with-host-4884a71903c5c8a9.yaml
@@ -1,7 +1,7 @@
---
features:
- |
- Added the ability to specify ``--host`` with ``server migrate``
+ Add ``--host`` option to ``server migrate`` command
(cold migration) to specify the target host of the migration.
Requires ``--os-compute-api-version`` 2.56 or greater to target a
specific host for the (cold) migration.
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
index 6cac67cf..7177873a 100644
--- a/releasenotes/notes/better-ipv6-address-suppport-security-group-rules-95272847349982e5.yaml
+++ b/releasenotes/notes/better-ipv6-address-suppport-security-group-rules-95272847349982e5.yaml
@@ -1,9 +1,8 @@
---
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.
+ Add ``--ethertype`` option to ``security group rule list`` command.
+ Valid values are ``ipv4`` and ``ipv6``.
upgrade:
- |
Security group rule listings now have the ``Ethertype`` field displayed
diff --git a/releasenotes/notes/bug-1716789-abfae897b7e61246.yaml b/releasenotes/notes/bug-1716789-abfae897b7e61246.yaml
index 1fd0a13d..4177f80b 100644
--- a/releasenotes/notes/bug-1716789-abfae897b7e61246.yaml
+++ b/releasenotes/notes/bug-1716789-abfae897b7e61246.yaml
@@ -1,17 +1,10 @@
---
-features:
+fixes:
- |
- Change to use ``any`` as the default ``--protocol`` option to
+ Change the default value of ``--protocol`` option to ``any`` in
``security group rule create`` command when using the Neutron v2 API.
[Bug `1716789 <https://bugs.launchpad.net/bugs/1716789>`_]
-fixes:
- - |
- The default protocol used to create a security rule was changed to
- ``tcp``, which was a regression from the neutron client when using
- the Neutron v2 API. Change it back to ``any``, which skips sending
- the protocol to the API server entirely.
upgrade:
- |
- Users that had been creating rules without specifying a protocol
- and expecting ``tcp`` need to change to use ``--protocol tcp``
- explicitly when using the Neutron v2 API.
+ Commands that assumed the default value of ``--protocol`` to be ``tcp``
+ now must include ``--protocol tcp`` explicitly in Network commands.
diff --git a/releasenotes/notes/volume-v3-default-0ffa9bebb43b5057.yaml b/releasenotes/notes/volume-v3-default-0ffa9bebb43b5057.yaml
index a38a5434..6b084077 100644
--- a/releasenotes/notes/volume-v3-default-0ffa9bebb43b5057.yaml
+++ b/releasenotes/notes/volume-v3-default-0ffa9bebb43b5057.yaml
@@ -3,5 +3,5 @@ upgrade:
- |
Volume commands now default to Volume API 3. On older clouds
that do not support Volume 3.x ``--os-volume-api-version 2``
- of the adition of ``volume_api_version: '2' in ``clouds.yaml``
+ or the adition of ``volume_api_version: '2'`` in ``clouds.yaml``
will be required.