Zed Series Release Notes

18.0.0.0b1-221

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, is localhost (the deploy host). Deployers can opt to rather change this to the utility container by implementing the following override in user_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 to 86400.

  • 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 to distro.

  • 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 to glance_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 with glance_remote_client. New variable has new keys for defining mounts to cover wider range of supported filesystems. Compatability for glance_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 for glance_cors_allowed_origin regardless of other variables.

17.0.0.0b3

New Features

  • When using Glance and NFS the NFS mount point will now be managed using a systemd mount unit file. This change ensures the deployment of glance is not making potentially system impacting changes to the /etc/fstab and modernizes how we deploy glance when using shared storage.

  • New variables have been added to the glance role allowing a deployer to set the UID and GID of the glance user. The new options are, glance_system_user_uid and glance_system_group_uid. These options are useful when deploying glance with shared storage as the back-end for images and will only set the UID and GID of the glance user when defined.

17.0.0.0b2

Upgrade Notes

  • The glance v1 API is now disabled by default as the API is scheduled to be removed in Queens.

  • The glance registry service is now disabled by default as it is not required for the v2 API and is scheduled to be removed in the future. The service can be enabled by setting glance_enable_v2_registry to True.

Deprecation Notes

  • The glance_enable_v1_registry variable has been removed. When using the glance v1 API the registry service is required, so having a variable to disable it makes little sense. The service is now enabled/disabled for the v1 API using the glance_enable_v1_api variable.

Bug Fixes

  • When the glance_enable_v2_registry variable is set to True the corresponding data_api setting is now correctly set. Previously it was not set and therefore the API service was not correctly informed that the registry was operating.

16.0.0.0rc1

New Features

  • The glance-api service has moved to run as a uWSGI application. You can set the max number of WSGI processes, the number of processes, threads, and buffer size utilizing the glance_wsgi_processes_max, glance_wsgi_processes, glance_wsgi_threads, and glance_wsgi_buffer_size. Additionally, you can override any settings in the uWSGI ini configuration file using the glance_api_uwsgi_ini_overrides setting.

16.0.0.0b3

Deprecation Notes

  • Remove glance_rpc_backend option due to deprecation of rpc_backend option in oslo.messaging.

16.0.0.0b2

New Features

  • New variables have been added to allow a deployer to customize a glance systemd unit file to their liking.

  • The task dropping the glance systemd unit files now uses the config_template action plugin allowing deployers access to customize the unit files as they see fit without having to load extra options into the defaults and pollute the generic systemd unit file with jinja2 variables and conditionals.

  • For the os_glance role, the systemd unit RestartSec value which controls the time between the service stop and start when restarting has been reduced from 150 seconds to 2 seconds to make the restart happen faster. This value can be adjusted by using the glance_*_init_config_overrides variables which use the config_template task to change template defaults.

Upgrade Notes

  • For the os_glance role, the systemd unit RestartSec value which controls the time between the service stop and start when restarting has been reduced from 150 seconds to 2 seconds to make the restart happen faster. This value can be adjusted by using the glance_*_init_config_overrides variables which use the config_template task to change template defaults.

16.0.0.0b1

New Features

  • Capping the default value for the variables glance_api_workers and glance_registry_workers to 16 when the user doesn’t configure these variables. Default value is half the number of vCPUs available on the machine with a capping value of 16.

15.0.0.0b2

New Features

  • Set the glance_swift_store_auth_insecure variable to override the swift_store_auth_inscure value in /etc/glance/glance-api.conf. Set this value when using an external Swift store that does not have the same insecure setting as the local Keystone.

15.0.0.0b1

Upgrade Notes

  • The variables glance_requirements_git_repo and glance_requirements_git_install_branch have been removed in favour of using the URL/path to the upper-constraints file using the variable pip_install_upper_constraints instead.

14.0.0.0rc1

New Features

  • CentOS7/RHEL support has been added to the os_glance role.

Upgrade Notes

  • The glance_apt_packages variable has been renamed to glance_distro_packages so that it applies to multiple operating systems.

14.0.0.0b3

New Features

  • The os_glance role now supports the ability to configure whether apt/yum tasks install the latest available package, or just ensure that the package is present. The default action is to ensure that the latest package is present. The action taken may be changed to only ensure that the package is present by setting glance_package_state to present.

Upgrade Notes

  • The variable glance_apt_packages has been renamed to glance_distro_packages.

  • The os_glance role always checks whether the latest package is installed when executed. If a deployer wishes to change the check to only validate the presence of the package, the option glance_package_state should be set to present.

14.0.0.0b2

Upgrade Notes

  • Installation of glance and its dependent pip packages will now only occur within a Python virtual environment. The glance_venv_bin, glance_venv_enabled, glance_venv_etc_dir, and glance_non_venv_etc_dir variables have been removed.

14.0.0.0b1

New Features

  • The os_glance role now supports Ubuntu 16.04 and SystemD.

Upgrade Notes

  • The database create and user creates have been removed from the os_glance role. These tasks have been relocated to the playbooks.