It would help both documentation and various sorts of task automation if we were to adopt a consistent naming scheme for our Pacemaker resources. For example, many of our services use the "openstack-" prefix, as in: openstack-nova-api-clone openstack-ceilometer-api-clone But others don't: keystone-clone glance-api-clone And sometimes we're not even consistent within the same service: openstack-ceilometer-alarm-notifier-clone ceilometer-delay-clone How about we just give all openstack services resource names that start with the "openstack-" prefix?
This won't be easy fix - would break updates. Deferring to post-OSP8
This bug did not make the OSP 8.0 release. It is being deferred to OSP 10.
OSP10 drops virtually all OSP components from pacemaker, except active/passive service. I don´t think the effort for those 2 services is worth the risk of breaking updates/upgrades given that in order to rename a service, the service has to be deconfigured and reconfigured within pacemaker.