Wallaby Series Release Notes



There was a mismatch between the way heat create role behaved with the templates or with the openstack CLI on what relates to the default domain if the domain is not specified on both cases the CLI will not assign on to the created new role but the heat templates will assign the “default” domain

New Features

  • The lb_algorithm property of OS::Octavia::Pool resource now supports SOURCE_IP_PORT option required for Octavia OVN provider driver.

  • Add new properties backups and to backups_gigabytes resource OS::Cinder::Quota. These properties can be updated without replacement.

  • The wallaby template version introduces a new 2-argument form of the if function. This allows users to specify optional property values, so that when the condition is false Heat treats it the same as if no value were specified for the property at all. The behaviour of existing templates is unchanged, even after updating the template version to wallaby.

  • Now the OS::Neutron::Port type supports the no_fixed_ips property, which allows users to create a network port without any fixed ips.

  • Adds a new segments attribute to the OS::Neutron::ProviderNet resource. The attribute resolves the segments of the network.

  • The default policies provided by heat api have been updated to add support for default roles and system scope. This is part of a broader community effort to support read-only roles and implement secure, consistent default policies.

    Refer to the Keystone documentation for more information on the reason for these changes.

  • Operators can now set a separate stacks:update_no_change policy for PATCH updates that don’t modify the stack, independently of the existing stacks:update_patch policy.

  • The OS::Glance::WebImage resource type now supports an active property to allow administrators to deactivate and reactivate the Image. Images remain active by default.

  • The OS::Glance::WebImage resource type now supports a members property for managing a list of other tenants with access to the Image.

  • A new OS::Vitrage::Template resource is added to configure and create a Vitrage template. The Vitrage template can be used, for example, for executing a Mistral healing workflow in case there is an alarm on an instance.

Deprecation Notes

  • The old default policy rules have been deprecated for removal in Xena cycle.

Critical Issues

  • Templates that creates roles but does not specify the domain will not get a “default” domain from now on. To have a domain added to your new role it needs to be assigned in the template.

Bug Fixes

  • Oslo db config is able to control wrap_db_retry call in heat. We remove hard coded settings for wrap_db_retry and use following configs from oslo_db instead. * database.db_max_retries * database.db_retry_interval * database.db_inc_retry_interval * database.db_max_retry_interval So database cofig can now control db retries. Please reference [1] for what each config options can do. [1] https://opendev.org/openstack/oslo.db/src/branch/master/oslo_db/options.py

  • The ordering in the list of segments returned by OS::Neutron::Net resources is not predictable. Stack updates changeing attributes of the network can cause the list of segments to shift.

    The ordering is now slightly more predictable, segments with name=``None`` are now placed first in the list. This doesn’t guarantee the order, but typically only the segment implicitly created by neutron has no name attribute set. The template author should ensure other segments on the network does have a name set, so that the implicit segment will always be index 0. Resolving attributes of the implcitly created segment on the network resource can then predictibly happen using index 0. See bug: 1894920.