Rocky Series Release Notes¶
18.0.0.0b1-33¶
New Features¶
The service setup in keystone for gnocchi will now be executed through delegation to the
gnocchi_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
.gnocchi_service_setup_host: "{{ groups['utility_all'][0] }}"
Deprecation Notes¶
The variable
gnocchi_requires_pip_packages
is no longer required and has therefore been removed.
16.0.0.0b2¶
New Features¶
New variables have been added to allow a deployer to customize a gnocchi systemd unit file to their liking.
The task dropping the gnocchi 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 polute the generic systemd unit file with jinja2 variables and conditionals.
For the
os_gnocchi
role, the systemd unitTimeoutSec
value 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. TheRestartSec
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. These values can be adjusted by using thegnocchi_*_init_config_overrides
variables which use theconfig_template
task to change template defaults.
Upgrade Notes¶
For the
os_gnocchi
role, the systemd unitTimeoutSec
value 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. TheRestartSec
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. These values can be adjusted by using thegnocchi_*_init_config_overrides
variables which use theconfig_template
task to change template defaults.
16.0.0.0b1¶
New Features¶
Capping the default value for the variable
gnocchi_wsgi_processes
to 16 when the user doesn’t configure this variable. Default value is twice the number of vCPUs available on the machine with a capping value of 16.
The
os_gnocchi
role now includes a facility where you can place your own defaultapi-paste.ini
orpolicy.json
file in/etc/openstack_deploy/gnocchi
(by default) and it will be deployed to the target host after being interpreted by the template engine.
Several configuration files that were not templated for the
os_gnocchi` role are now retrieved from git. The git repository used can be changed using the ``gnocchi_git_config_lookup_location
variable. By default this points togit.openstack.org
. These files can still be changed using thegnocchi_x_overrides
variables.
Upgrade Notes¶
Gnocchi service endpoint variables were not named correctly. Renamed variables to be consistent with other roles.
Deprecation Notes¶
The
gnocchi_keystone_auth_plugin
variable has been deprecated.gnocchi_keystone_auth_type
should be used instead to configure authentication type.
15.0.0.0rc1¶
New Features¶
Specify the
gnocchi_auth_mode
var to set theauth_mode
for gnocchi. This defaults tobasic
which has changed fromnoauth
to match upstream. Ifgnocchi_keystone_auth
istrue
oryes
this value will default tokeystone
.
Specify the
gnocchi_git_config_lookup_location
value to specify the git repository where thegnocchi
config files can be retrieved. Theapi-paste.ini
andpolicy.json
files are now retrieved from the specified git repository and are not carried in theos_gnocchi
role.
Upgrade Notes¶
The gnocchi_archive_policies and gnocchi_archive_policy_rules variables never had full support in the role so were ineffective at the intended purpose. The task references to them have been removed and the library to perform gnocchi operations has also been removed. This eliminates the need for the gnocchi client to be installed outside the virtual environment as well.
Deprecation Notes¶
The
gnocchi_keystone_auth
is deprecated, and will be removed in theQueen
cycle. Settinggnocchi_auth_mode
tokeystone
will achieve the same result.
15.0.0.0b2¶
New Features¶
CentOS7/RHEL support has been added to the os_gnocchi role.
Upgrade Notes¶
The variable
gnocchi_required_pip_packages
was incorrectly named and has been renamed tognocchi_requires_pip_packages
to match the standard across all roles.
15.0.0.0b1¶
Upgrade Notes¶
The variables
gnocchi_requirements_git_repo
andgnocchi_requirements_git_install_branch
have been removed in favour of using the URL/path to the upper-constraints file using the variablepip_install_upper_constraints
instead.
14.0.0.0b3¶
New Features¶
The os_gnocchi 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
gnocchi_package_state
topresent
.
Upgrade Notes¶
The os_gnocchi 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
gnocchi_package_state
should be set topresent
.