Heat service is not configured as corosync resource

[Ilya Bumarskov]

Fuel 10 build #1575

Steps to reproduce:
   Deploy HA cluster
   Check corosync resources

Observed behavior:
heat service isn't configured as corosync resource:

root@node-4:~# crm_resource list
 Clone Set: clone_p_vrouter [p_vrouter]
     Started: [ node-1.test.domain.local node-3.test.domain.local node-4.test.domain.local ]
 vip__management (ocf::fuel:ns_IPaddr2): Started
 vip__vrouter_pub (ocf::fuel:ns_IPaddr2): Started
 vip__vrouter (ocf::fuel:ns_IPaddr2): Started
 vip__public (ocf::fuel:ns_IPaddr2): Started
 Clone Set: clone_p_haproxy [p_haproxy]
     Started: [ node-1.test.domain.local node-3.test.domain.local node-4.test.domain.local ]
 Master/Slave Set: master_p_conntrackd [p_conntrackd]
     Masters: [ node-3.test.domain.local ]
     Slaves: [ node-1.test.domain.local node-4.test.domain.local ]
 sysinfo_node-3.test.domain.local (ocf::pacemaker:SysInfo): Started
 sysinfo_node-4.test.domain.local (ocf::pacemaker:SysInfo): Started
 Master/Slave Set: master_p_rabbitmq-server [p_rabbitmq-server]
     Masters: [ node-4.test.domain.local ]
     Slaves: [ node-1.test.domain.local node-3.test.domain.local ]
 Clone Set: clone_p_mysqld [p_mysqld]
     Started: [ node-1.test.domain.local node-3.test.domain.local node-4.test.domain.local ]
 Clone Set: clone_p_dns [p_dns]
     Started: [ node-1.test.domain.local node-3.test.domain.local node-4.test.domain.local ]
 sysinfo_node-1.test.domain.local (ocf::pacemaker:SysInfo): Started
 Clone Set: clone_neutron-openvswitch-agent [neutron-openvswitch-agent]
     Started: [ node-1.test.domain.local node-3.test.domain.local node-4.test.domain.local ]
 Clone Set: clone_neutron-l3-agent [neutron-l3-agent]
     Started: [ node-1.test.domain.local node-3.test.domain.local node-4.test.domain.local ]
 Clone Set: clone_neutron-metadata-agent [neutron-metadata-agent]
     Started: [ node-1.test.domain.local node-3.test.domain.local node-4.test.domain.local ]
 Clone Set: clone_neutron-dhcp-agent [neutron-dhcp-agent]
     Started: [ node-1.test.domain.local node-3.test.domain.local node-4.test.domain.local ]
 Clone Set: clone_p_ntp [p_ntp]
     Started: [ node-1.test.domain.local node-3.test.domain.local node-4.test.domain.local ]
 Clone Set: clone_ping_vip__public [ping_vip__public]
     Started: [ node-1.test.domain.local node-3.test.domain.local node-4.test.domain.local ]

[Michael Polenchuk (mpolenchuk)]

heat-engine service (kind of stateless) will be restarted on failure by systemd, so there is no reason to get this service under pacemaker control.

[Michael Polenchuk (mpolenchuk)]

Anyway there is an option to enable heat under pacemaker control:
https://github.com/openstack/fuel-library/blob/master/deployment/puppet/openstack_tasks/manifests/heat/heat.pp#L242-L248