Current Series Release Notes¶

0.0.0¶

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

The task dropping the cloudkitty 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.

The service setup in keystone for cloudkitty will now be executed through delegation to the cloudkitty_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.
```
cloudkitty_service_setup_host: "{{ groups['utility_all'][0] }}"
```

For the os_cloudkitty role, the systemd unit TimeoutSec 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. The 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. These values can be adjusted by using the cloudkitty_*_init_config_overrides variables which use the config_template task to change template defaults.

Support separate oslo.messaging services for RPC and Notifications to enable operation of separate and different messaging backend servers.

The os_cloudkitty 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 cloudkitty_package_state to present.

For the os_cloudkitty role, the systemd unit TimeoutSec 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. The 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. These values can be adjusted by using the cloudkitty_*_init_config_overrides variables which use the config_template task to change template defaults.

Installation of cloudkitty and its dependent pip packages will now only occur within a Python virtual environment. The cloudkitty_venv_bin and cloudkitty_venv_enabled variables have been removed.

The os_cloudkitty 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 cloudkitty_package_state should be set to present.

The variables cloudkitty_requirements_git_repo and cloudkitty_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.

cloudkitty_uwsgi_bind_address inherits openstack_service_bind_address and defaults to 0.0.0.0

The variable cloudkitty_requires_pip_packages is no longer required and has therefore been removed.

The log path, /var/log/cloudkitty is no longer used to capture service logs. All logging for the cloudkitty service will now be sent directly to the systemd journal.

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. - cloudkitty_oslomsg_rpc_servers replaces rabbitmq_servers - cloudkitty_oslomsg_rpc_port replaces rabbitmq_port - cloudkitty_oslomsg_rpc_userid replaces rabbitmq_userid - cloudkitty_oslomsg_rpc_vhost replaces rabbitmq_vhost - cloudkitty_oslomsg_rpc_use_ssl replaces rabbitmq_use_ssl - added cloudkitty_oslomsg_notify_servers - added cloudkitty_oslomsg_notify_port - added cloudkitty_oslomsg_notify_use_ssl - added cloudkitty_oslomsg_notify_userid - added cloudkitty_oslomsg_notify_vhost

Remove cloudkitty_rpc_backend option due to deprecation of rpc_backend option in oslo.messaging.

cloudkitty_collected_services is deprecated and should instead be configured in Cloudkitty metrics config