puppet-openstack-integration/manifests/redis.pp

class openstack_integration::redis {
  include ::openstack_integration::config

  class { '::redis':
    bind           => $::openstack_integration::config::host,
    service_enable => false
  }
}
gnocchi: use redis as coordination url Currently gnocchi metricd is really slow making some tests timeout, because the tooz backend is mysql. And the futur autoscaling will reach the max connections of mysql by creating many tooz locks. This change switches to redis, this is one of the recommended backend to use (mysql is not). Change-Id: Iae81848e883f74b7f8f8f4cad58c2168e01b7321 2017-05-03 16:08:56 +02:00			`class openstack_integration::redis {`
			`include ::openstack_integration::config`

			`class { '::redis':`
Debian: fix redis service setup The redis-server appears as "masked" in the OpenStack CI, even though it did not in my test VM. As a consequence, "systemctl enable redis-server" fails, and consequently, the puppet run fails in OpenStack CI. The thing is, there's no need to enable this service, as in all distros, it's already enabled by default. Even in the OpenStack CI, the service appears as enabled, but masked (which by the way, should never happen, as this isn't a working systemd state). This patch simply removes the enabling of the systemd service, so that it also works in Debian in the CI. Change-Id: I1b37524ff1071d87e8a7df2fa3bca66aed162d1b 2018-05-31 21:24:10 +02:00			`bind => $::openstack_integration::config::host,`
			`service_enable => false`
gnocchi: use redis as coordination url Currently gnocchi metricd is really slow making some tests timeout, because the tooz backend is mysql. And the futur autoscaling will reach the max connections of mysql by creating many tooz locks. This change switches to redis, this is one of the recommended backend to use (mysql is not). Change-Id: Iae81848e883f74b7f8f8f4cad58c2168e01b7321 2017-05-03 16:08:56 +02:00			`}`
			`}`