Wallaby Series Release Notes¶

19.3.0¶

When multiple availability zones are available, the default behavior is to allow the scheduler to spawn a VM in any of them. The new setting LAUNCH_INSTANCE_DEFAULTS.default_availability_zone allows an administrator to specify a default static availability zone for new VM creation.

Previously, ToggleSuspend class checked os-rescue policy for resume operation. By this fix, the class checks ‘os_compute_api:os-suspend-server:resume’ policy to align to resume operation.

Get the timezone offset for the current day instead of January 1st. This bug only appears to be a cosmetic one where the TZ offset would be calculated on current_year/01/01 so would remain in daylight saving offset when displaying the timezones list in the user configuration settings.

Setting ‘can_set_password’ to True in OPENSTACK_HYPERVISOR_FEATURES adds the option to set admin password from AngularJS Launch Instance dialog.

Horizon supports the registered default policies and operators now only need to define policies which they would like to override in policy files in POLICY_FILES setting. (Previously the policy files need to contain all defined policies including default policies.) The registered default policies are defined in files under DEFAULT_POLICY_FILES and they are synced with registered defaults of back-end services before the horizon release.

Chinese locales zh-cn and zh-tw are now changed to zh-hans and zh-hant respectively. This follows the change in Django which is a framework horizon depends on. The new locales decouples what are spoken from specific locations as they are also used outside of China/Taiwan.

Volume backups is now supported for admin panel. Admin is now able to view all volume backups for differenet users.

Policies with the system scoped token (system_scope:all) are not supported in horizon yet. The horizon team recognizes it as an important feature gap and would like to support it in near future.

The format of the policy files under POLICY_FILES is changed to YAML and all contents of these files are commented out now. You only need to define policies which you would like to modify from the default. You can still use policy files with JSON format. If you continue to use JSON format, configure POLICY_FILES setting to point JSON files.

Chinese locales zh-cn and zh-tw have been changed to zh-hans and zh-hant respectively. If you configure LANGUAGES in your setting explicitly, ensure to use the new Chinese locales if needed.

The Django version of the launch instance form is deprecated now. Switch to the AngularJS version of the form by setting LAUNCH_INSTANCE_NG_ENABLED to True and LAUNCH_INSTANCE_LEGACY_ENABLED to False. The horizon team believes that feature gaps between Django and AngularJS implementations have been closed and we can drop the Django version. If you see any feature gap, please file a bug to horizon or contact the horizon team.

A new setting OPENSTACK_USE_SIMPLE_TENANT_USAGE was introduced as a replacement of SimpleTenantUsage in the deprecated OPENSTACK_NOVA_EXTENSIONS_BLACKLIST setting. This new setting controls whether SimpleTenantUsage nova API is used in the usage overview. According to feedbacks to the horizon team, the usage of SimpleTenantUsage can cause performance issues in the nova API in larger deployments. Try to set this to False for such cases.

Deprecated opensatck_dashboard/wsgi/django.wsgi is removed. If you still use it, please change your configuration to use openstack_dashboard/wsgi.py now.

The legacy way to retrive neutron resource usages was dropped and horizon now assumes the quota_details neutron API extension implemented in Pike release (over three years ago), so we expect this is available in all Wallaby neutron deployments.

OPENSTACK_NOVA_EXTENSIONS_BLACKLIST setting is now dropped. If you specify SimpleTenantUsage in this setting, consider setting OPENSTACK_USE_SIMPLE_TENANT_USAGE to False instead. For other effective values in this setting, no replacement is provided as nova provides all features in recent versions of nova API. Note that you can enable/disable table actions via policy rules.

Password forms in horizon now does not strip leading/trailing spaces included in input passwords. Previously horizon stripped leading/trailing spaces in input passwords but on the other hand keystone accepts leading/trailing spaces and it can be an issue when such passwords are set via keystone API. To handle this situation horizon no longer strips leading/trailing spaces in passwords. See [bug 1861224] and the related mailing thread for more detail. (Note that this change is part of horizon 18.5.0 release but we forgot to mention it.)

Considering the deprecation of OPENSTACK_NOVA_EXTENSIONS_BLACKLIST, set a new setting OPENSTACK_USE_SIMPLE_TENANT_USAGE to False if you specify SimpleTenantUsage in OPENSTACK_USE_SIMPLE_TENANT_USAGE