Comment 8 for bug 1664898

Bearing in mind where we are in the cycle, I think we need to make a minimal change to move things forward for release next week.

The intent of running the central polling agent under corosync/pacemaker is to ensure it only runs in a single location in the cluster (otherwise polls are duplicated), so we should ensure that as soon as the charm is clustered, the service checks for ceilometer-agent-central are dropped in the principle charm; there is also probably an impact on restarts of the ceilometer-agent-central service as well (this will need to be delegated to crm calls I think).