Remove heat-engine from pacemaker control

[Sergey Kraynev]

Currently Heat-engine is under pacemaker control.
However it's not really necessary and we should remove it from pacemaker control.

There is a snippet from initial mail about this issue:
"currently in MOS we are placing heat-engine services under corosync/pacemaker control. That prominently differs from other OpenStack services, as all the other crm resources are either lower-level infrastructure pieces (DB, rabbit, haproxy...) or various neutron agents.

In my understanding this was done during development MOS 5.0 when Heat multi-engine setup was introduced, but due to then undiscovered bug (https://bugs.launchpad.net/mos/+bug/1387345) heat-engine could not actually work in multi-engine mode. Thus pacemaker was used to manually force only single heat-engine running.

In my view it is time to remove this workaround. For example, just recently it complicated debugging of a bug (https://bugs.launchpad.net/mos/+bug/1449007) caused by dependency mismatch, as pacemaker was stubbornly restarting heat-engines over and over instead of failing the deployment. This bug (https://bugs.launchpad.net/fuel/+bug/1450064) suggests adding "maximum restarts" but I think it is better to remove heat-engines from pacemaker altogether.

If there is though some other important reason why we are still controlling heat-engines with pacemaker that I've missed, please chime in.
"

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/307172

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/307172
Committed: https://git.openstack.org/cgit/openstack/fuel-library/commit/?id=897aea28aeba3f0fd0db865e0b3d8f63d6f514c0
Submitter: Jenkins
Branch: master

commit 897aea28aeba3f0fd0db865e0b3d8f63d6f514c0
Author: dmburmistrov <email address hidden>
Date: Thu Apr 14 15:24:32 2016 +0300

    Remove heat-engine from pacemaker controll

    Heat-engine service doesn't require pacemaker
    control since Fuel 7.0. This patch removes
    pacemaker usage by default, but still gives
    an ability to enable it (only for "N"-release).

    Closes-bug: #1570297

    Change-Id: Ibfe4a610c1196834aeede786cbcfa9521d1bec40