Zed Series Release Notes

23.0.0

New Features

  • The new setting OPENSTACK_SERVER_DEFAULT_USER_DATA allows an administrator to specify a default user data (e.g. comments or instructions for cloudinit) for new VMs. It can be a raw string or string template that accepts the request.

  • The new settings LAUNCH_INSTANCE_DEFAULTS.enable_metadata and LAUNCH_INSTANCE_DEFAULTS.enable_net_ports allow to hide Metadata and Network Ports tabs from launch instance workflow.

  • Cinder user messages are now available for volume backups in a messages tab.

22.2.0

New Features

  • Horizon can now use a system scope token when performing admin operations. To enable that, a new setting, SYSTEM_SCOPE_SERVICES, has to list the OpenStack services for which this feature is to be enabled. When that setting is not empty, a new option, “system scope” will appear in the context switching menu, and the panels for the listed services will be moved into that context in the main menu.

Upgrade Notes

  • Horizon no longer requires the keystone admin endpoint. keystone does not distinguish public and admin endpoints and there is no functional difference between public and admin endpoints. There is no need for a separate endpoint for keystone admin operations, but horizon required the keystone admin endpoint is configured previously. This requirement no longer exists. An endpoint specified by OPENSTACK_ENDPOINT_TYPE setting is used for the keystone admin operations. You can drop the admin endpoint for keystone (unless other services require it). [bug 1950659]

Deprecation Notes

  • The Django version of the Images, Keypairs, and Roles panels is deprecated now. Switch to the AngularJS version by setting images_panel, key_pairs_panel and roles_panel keys in ANGULAR_FEATURES setting to True (or dropping these keys from ANGULAR_FEATURES setting). The horizon team believes that feature gaps between Django and AngularJS implementations have been closed for all these panels and we can drop the Django version. If you see any feature gap, please file a bug to horizon or contact the horizon team.