Ussuri Series Release Notes¶
You can now remove role assignments from keystone that reference non-existent users or groups.
volume backup recordcommands available in Volume API v3. Task 40279
[Story 2005246] The is_domain property safely handles type checking.
Complete switch from glanceclient to the SDK for image service.
Image service for v2 is switched from using glanceclient to OpenStackSDK.
Now user can add the description when user create’s the role using OSC
openstack role createcommand. User can add the description by adding –description <Description> to OSC
openstack role createcommand.
set subnetcommands to control the publishing of fixed IPs in DNS when the
subnet_dns_publish_fixed_ipNeutron extension is enabled. [Bug 1784879]
network createthe –default` option should be only used for external networks. After this release, we enforce this scenario. If a users attempts to create an internal default network or update a network to be internal default, the command will be denied. [Bug 1745658]
project listcommand to filter projects by the specified parent project.
server migrate confirmand
server migrate revertcommands. These are aliases of the
server resize confirmand
server resize revertcommands, respectively.
--enable-delete-on-terminationoptions to the
server add volumecommand to indicate when to delete the attached volume when the server is deleted. Note that it requires
--os-compute-api-version 2.79or greater. [Blueprint support-specifying-az-when-restore-shelved-server https://blueprints.launchpad.net/nova/+spec/support-delete-on-termination-in-server-attach-volume]
[blueprint whitelist-extension-for-app-creds] Added support for creating access rules as an attribute of application credentials as well as for listing, showing, and deleting access rules.
Python 2.7 support has been dropped. The last release of python-openstackclient to support Python 2.7 is OpenStack Train. The minimum version of Python now supported by python-openstackclient is Python 3.6.
Fixes the “No server with a name or ID of ‘id’ exists” error when running
server list --deleted --marker. The fix removes using a name for the marker when both
--markerare used. In this scenario an ID must be supplied for the marker. [Story 2006761]