Zed Series Release Notes¶
18.0.0.0b1-219¶
New Features¶
It is possible to configure Glance to allow cross origin requests by specifying the allowed origin address using the
glance_cors_allowed_origin
variable. By default, this will be the load balancer address.
The service setup in keystone for glance will now be executed through delegation to the
glance_service_setup_host
which, by default, islocalhost
(the deploy host). Deployers can opt to rather change this to the utility container by implementing the following override inuser_variables.yml
.glance_service_setup_host: "{{ groups['utility_all'][0] }}"
Added variable
glance_image_cache_stall_time
to control glance cache time if needed. Defaults to86400
.
The role now supports using the distribution packages for the OpenStack services instead of the pip ones. This feature is disabled by default and can be enabled by simply setting the
glance_install_method
variable todistro
.
Support separate oslo.messaging services for RPC and Notifications to enable operation of separate and different messaging backend servers in glance.
Upgrade Notes¶
The glance v1 API is now removed upstream and the deployment code is now removed from this glance ansible role. The variable
glance_enable_v1_api
is removed.
Deprecation Notes¶
The variable
glance_requires_pip_packages
is no longer required and has therefore been removed.
Glance registry service has been finally removed
Variable
glance_nfs_local_directory
has been renamed toglance_images_local_directory
to better reflect purpose of the variable.glance_nfs_local_directory
remains for backwards compatability but will be removed in Zed release.
Variable
glance_nfs_client
has been replaced withglance_remote_client
. New variable has new keys for defining mounts to cover wider range of supported filesystems. Compatability forglance_nfs_client
has been kept until Zed release.
The rabbitmq server parameters have been replaced by corresponding oslo.messaging RPC and Notify parameters in order to abstract the messaging service from the actual backend server deployment. - glance_oslomsg_rpc_servers replaces glance_rabbitmq_servers - glance_oslomsg_rpc_port replaces glance_rabbitmq_port - glance_oslomsg_rpc_use_ssl replaces glance_rabbitmq_use_ssl - glance_oslomsg_rpc_userid replaces glance_rabbitmq_userid - glance_oslomsg_rpc_vhost replaces glance_rabbitmq_vhost - glance_oslomsg_notify_servers replaces glance_rabbitmq_telemetry_servers - glance_oslomsg_notify_port replaces glance_rabbitmq_telemetry_port - glance_oslomsg_notify_use_ssl replaces glance_rabbitmq_telemetry_use_ssl - glance_oslomsg_notify_userid replaces glance_rabbitmq_telemetry_userid - glance_oslomsg_notify_vhost replaces glance_rabbitmq_telemetry_vhost - glance_oslomsg_notify_password replaces glance_rabbitmq_telemetry_password
Other Notes¶
external_lb_vip_address
was added to the default value forglance_cors_allowed_origin
regardless of other variables.