We are amped to announce the release of: openstack-ansible 15.1.3: Ansible playbooks for deploying OpenStack This release is part of the ocata stable release series. The source is available from: http://git.openstack.org/cgit/openstack/openstack-ansible Download the package from: https://tarballs.openstack.org/openstack-ansible/ For more details, please see below. 15.1.3 ^^^^^^ New Features ************ * New variables have been added to allow a deployer to customize a aodh systemd unit file to their liking. * The task dropping the aodh 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_aodh" 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 "aodh_*_init_config_overrides" variables which use the "config_template" task to change template defaults. * For the "os_barbican" 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 "barbican_*_init_config_overrides" variables which use the "config_template" task to change template defaults. * New variables have been added to allow a deployer to customize a ceilometer systemd unit file to their liking. * The task dropping the ceilometer 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_ceilometer" 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 "ceilometer_*_init_config_overrides" variables which use the "config_template" task to change template defaults. * 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_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. * 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 polute 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. * 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 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 "gnocchi_*_init_config_overrides" variables which use the "config_template" task to change template defaults. * New variables have been added to allow a deployer to customize a heat systemd unit file to their liking. * The task dropping the heat 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_heat" 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 "heat_*_init_config_overrides" variables which use the "config_template" task to change template defaults. * New variables have been added to allow a deployer to customize a ironic systemd unit file to their liking. * The task dropping the ironic 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_ironic" 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 "ironic_*_init_config_overrides" variables which use the "config_template" task to change template defaults. * New variables have been added to allow a deployer to customize a keystone systemd unit file to their liking. * The task dropping the keystone 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_keystone" 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 "keystone_*_init_config_overrides" variables which use the "config_template" task to change template defaults. * New variables have been added to allow a deployer to customize a magnum systemd unit file to their liking. * The task dropping the magnum 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_magnum" 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 "magnum_*_init_config_overrides" variables which use the "config_template" task to change template defaults. * New variables have been added to allow a deployer to customize a neutron systemd unit file to their liking. * The task dropping the neutron 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_neutron" 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 "neutron_*_init_config_overrides" variables which use the "config_template" task to change template defaults. * New variables have been added to allow a deployer to customize a nova systemd unit file to their liking. * The task dropping the nova 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_nova" 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 "nova_*_init_config_overrides" variables which use the "config_template" task to change template defaults. * In the Ocata release, Trove added support for encrypting the rpc communication between the guest DBaaS instances and the control plane. The default values for "trove_taskmanager_rpc_encr_key" and "trove_inst_rpc_key_encr_key" should be overridden to specify installation specific values. * New variables have been added to allow a deployer to customize a sahara systemd unit file to their liking. * The task dropping the sahara 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_sahara" 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 "sahara_*_init_config_overrides" variables which use the "config_template" task to change template defaults. * New variables have been added to allow a deployer to customize a swift systemd unit file to their liking. * The task dropping the swift 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. * New variables have been added to allow a deployer to customize a trove systemd unit file to their liking. * The task dropping the trove 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_trove" 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 "trove_*_init_config_overrides" variables which use the "config_template" task to change template defaults. Upgrade Notes ************* * For the "os_aodh" 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 "aodh_*_init_config_overrides" variables which use the "config_template" task to change template defaults. * For the "os_barbican" 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 "barbican_*_init_config_overrides" variables which use the "config_template" task to change template defaults. * For the "os_ceilometer" 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 "ceilometer_*_init_config_overrides" variables which use the "config_template" task to change template defaults. * 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. * For the "os_gnocchi" 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 "gnocchi_*_init_config_overrides" variables which use the "config_template" task to change template defaults. * For the "os_heat" 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 "heat_*_init_config_overrides" variables which use the "config_template" task to change template defaults. * For the "os_ironic" 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 "ironic_*_init_config_overrides" variables which use the "config_template" task to change template defaults. * For the "os_keystone" 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 "keystone_*_init_config_overrides" variables which use the "config_template" task to change template defaults. * For the "os_magnum" 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 "magnum_*_init_config_overrides" variables which use the "config_template" task to change template defaults. * For the "os_neutron" 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 "neutron_*_init_config_overrides" variables which use the "config_template" task to change template defaults. * For the "os_nova" 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 "nova_*_init_config_overrides" variables which use the "config_template" task to change template defaults. * For the "os_sahara" 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 "sahara_*_init_config_overrides" variables which use the "config_template" task to change template defaults. * For the "os_trove" 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 "trove_*_init_config_overrides" variables which use the "config_template" task to change template defaults. Changes in openstack-ansible 15.1.2..15.1.3 ------------------------------------------- 3ac6ae0 Update haproxy check script in keepalived. 82b2e9d Bump ceph role tags b41f1f0 [Docs] Cleanup developer section 0e75e1d [Docs] Describe variable files locations 40713bd Update all SHAs for 15.1.3 4cf94d9 Update role SHA's to fix CentOS builds da679d6 Use package module to install distro packages e15ff3b Add designate public and internal URL config bcdfdae Bugfix for wait_for_ssh for waiting for connectivity Diffstat (except docs and test files) ------------------------------------- ansible-role-requirements.yml | 54 +++++------ playbooks/defaults/repo_packages/gnocchi.yml | 2 +- .../defaults/repo_packages/openstack_services.yml | 60 ++++++------ playbooks/inventory/group_vars/all.yml | 2 +- playbooks/inventory/group_vars/designate_all.yml | 6 ++ playbooks/lxc-containers-create.yml | 4 +- playbooks/utility-install.yml | 26 +----- playbooks/vars/configs/keepalived_haproxy.yml | 2 +- ...odh-init-config-overrides-f152b8fd098efb0d.yaml | 10 ++ .../aodh_init_time_settings-9661d23a9bb6682c.yaml | 23 +++++ ...rbican_init_time_settings-d7510910912fa061.yaml | 23 +++++ ...ter-init-config-overrides-bfce7e419061c4da.yaml | 10 ++ ...ometer_init_time_settings-2eebfa58227ae31a.yaml | 23 +++++ ...der-init-config-overrides-9e495aee023deed6.yaml | 10 ++ ...cinder_init_time_settings-1ef46f6b9d4fc1df.yaml | 30 +++--- ...nce-init-config-overrides-dfce7e419061c4da.yaml | 10 ++ ...glance_init_time_settings-d3cc064fd8acf107.yaml | 15 +++ ...chi-init-config-overrides-4fc9ec27ea1bd090.yaml | 10 ++ ...nocchi_init_time_settings-ba554f29fc7fd351.yaml | 23 +++++ ...eat-init-config-overrides-004872081661a34c.yaml | 10 ++ .../heat_init_time_settings-5f9f7cd4326ded97.yaml | 23 +++++ ...nic-init-config-overrides-e73d9fd46a69afcf.yaml | 10 ++ .../ironic_init_time_settings-b8ab3c3c4d733dc.yaml | 23 +++++ ...one-init-config-overrides-1857d5e5bc5a905f.yaml | 10 ++ ...ystone_init_time_settings-62a1aab4bcfc9779.yaml | 23 +++++ ...num-init-config-overrides-aec21cbbd9da8e4e.yaml | 9 ++ .../magnum_init_time_settings-6ecc4ff27d7dca1.yaml | 23 +++++ ...ron-init-config-overrides-9d1d2b3b908705ed.yaml | 10 ++ ...eutron_init_time_settings-66ad8a3d9eb951b0.yaml | 23 +++++ ...ova-init-config-overrides-7221a8f9d5be9291.yaml | 9 ++ .../nova_init_time_settings-cef7e89ab41da256.yaml | 23 +++++ .../notes/rpc-encryption-b75fb0d08579a7dd.yaml | 7 ++ ...ara-init-config-overrides-4c35b88618b0d0b4.yaml | 10 ++ ...sahara_init_time_settings-5ed44feb1285b867.yaml | 23 +++++ ...ift-init-config-overrides-822ec734e02a0dd1.yaml | 10 ++ ...ove-init-config-overrides-a78ed428a32adef8.yaml | 10 ++ .../trove_init_time_settings-dd293238c53c517.yaml | 23 +++++ 41 files changed, 622 insertions(+), 202 deletions(-)