Usage of pacemaker::resource::systemd should be avoided

[Giulio Fidente]

The puppet pacemaker::resource::systemd class assumes pacemaker is running on a systemd capable distro, that is not always the case. When dealing with 'system services' (in contrast with resource agents), the resource type should be abstracted.

[Crag Wolfe (cwolfe)]

Users should consume
https://github.com/redhat-openstack/puppet-pacemaker/blob/master/manifests/resource/service.pp
rather than pacemaker::resource::systemd directly. Right now, service.pp declares pacemaker::resource::sytemd or pacemaker::resource::lsb based on distro. I think it would be safe to close this as "notabug."

[Crag Wolfe (cwolfe)]

Based on IRC convo, rather than closing than notabug, this bug is really about changing ::sytemd to ::service in the tripleo manifests.

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/180506
Committed: https://git.openstack.org/cgit/openstack/tripleo-heat-templates/commit/?id=ada9662b8b92fd4ec925407fd675c7941f6a3267
Submitter: Jenkins
Branch: master

commit ada9662b8b92fd4ec925407fd675c7941f6a3267
Author: Giulio Fidente <email address hidden>
Date: Mon May 11 15:26:27 2015 +0200

    Use pacemaker::resource::service instead of ::systemd

    The puppet-pacemaker module realizes some abstraction for the
    different service types in ::service already.

    Change-Id: Icd897e18fda01b1bf4722a975c991e26341ac129
    Closes-Bug: 1449988

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/tripleo-heat-templates 0.8.6 release.