Ceilometer now uses the tooz coordination library to allow workload partitioning across scaled out central agents (previously a SPoF). For consistency, the ceilometer alarm evaluator can also optionally be scaled out in that way. We need to allow the coordination backend to be selected in the ceilometer advanced configuration dialog presented by rhel-osp-installer, and then the redis installation be driven via a openstack-foreman-installer deployment. At a minimum this should allow a single redis instance on the controller plane to be selected as the coordination.backend_url in the ceilometer.conf. Preferably, the redis-sentinel service should be installed on each controller, and the sentinel-style of address used in the coordination.backend_url so that sentinel can drive fail over from redis master to slaves if necessary.
Patch under review: https://github.com/redhat-openstack/astapor/pull/447
The original pull-request was inadvertently closed, now superseded by: https://github.com/redhat-openstack/astapor/pull/449
Bumping to A2 after discussion with fabbione recommended using pacemaker with a new redis resource-agent instead of redis-sentinel.
Bumping to A3 after discussion on the availability of the redis resource-agent.
Updated PR from Pradeep Kilambi: https://github.com/redhat-openstack/astapor/pull/506
Patch posted: https://github.com/redhat-openstack/astapor/pull/542
Closing list of bugs for RHEL OSP Installer since its support cycle has already ended [0]. If there is some bug closed by mistake, feel free to re-open. For new deployments, please, use RHOSP director (starting with version 7). -- Jaromir Coufal -- Sr. Product Manager -- Red Hat OpenStack Platform [0] https://access.redhat.com/support/policy/updates/openstack/platform