Newton Series Release Notes¶
14.2.7¶
New Features¶
The
os_cinderrole now provides for doing online data migrations once the db sync has been completed. The data migrations will not be executed until the boolean variablecinder_all_software_updatedis true. This variable will need to be set by the playbook consuming the role.
14.2.4¶
New Features¶
New variables have been added to allow a deployer to customize a cinder systemd unit file to their liking.
The task dropping the cinder systemd unit files now uses the
config_templateaction plugin allowing deployers access to customize the unit files as they see fit without having to load extra options into the defaults and polute the generic systemd unit file with jinja2 variables and conditionals.
14.2.1¶
New Features¶
Add support for the cinder v3 api. This is enabled by default, but can be disabled by setting the
cinder_enable_v3_apivariable tofalse.
For the
os_cinderrole, the systemd unitTimeoutSecvalue which controls the time between sending a SIGTERM signal and a SIGKILL signal when stopping or restarting the service has been reduced from 300 seconds to 120 seconds. This provides 2 minutes for long-lived sessions to drain while preventing new ones from starting before a restart or a stop. TheRestartSecvalue 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. These values can be adjusted by using thecinder_*_init_config_overridesvariables which use theconfig_templatetask to change template defaults.
Deprecation Notes¶
The variables
cinder_sigkill_timeoutandcinder_restart_waithave been deprecated and will be removed in Pike.
14.0.8¶
Upgrade Notes¶
The global override
cinder_nfs_clientis replaced in favor of fully supporting multi backends configuration via the cinder_backends stanza.
Deprecation Notes¶
The global override
cinder_nfs_clientis replaced in favor of fully supporting multi backends configuration via the cinder_backends stanza.
14.0.7¶
New Features¶
Additional volume-types can be created by defining a list named
extra_volume_typesin the desired backend of the variable(s)cinder_backends
Deployers can now define the varible
cinder_qos_specsto create qos specs and assign those specs to desired cinder volume types.
14.0.2¶
New Features¶
Deployers can now define the override
cinder_rpc_executor_thread_pool_sizewhich defaults to 64
Deployers can now define the override
cinder_rpc_response_timeoutwhich defaults to 60
Upgrade Notes¶
The variables
cinder_requirements_git_repoandcinder_requirements_git_install_branchhave been removed in favour of using the URL/path to the upper-constraints file using the variablepip_install_upper_constraintsinstead.
14.0.0¶
New Features¶
The
os_cinderrole now supports Ubuntu 16.04.
CentOS7/RHEL support has been added to the os_cinder role.
The os_cinder 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
cinder_package_statetopresent.
Upgrade Notes¶
Installation of cinder and its dependent pip packages will now only occur within a Python virtual environment. The
cinder_venv_enabledandcinder_venv_binvariables have been removed.
The variable
cinder_apt_packageshas been renamed tocinder_distro_packages.
The variable
cinder_volume_apt_packageshas been renamed tocinder_volume_distro_packages.
The variable
cinder_lvm_volume_apt_packageshas been renamed tocinder_lvm_volume_distro_packages.
The os_cinder 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
cinder_package_stateshould be set topresent.
The database create and user creates have been removed from the
os_cinderrole. These tasks have been relocated to the playbooks.