<div dir="ltr">Guys,<div><br></div><div>Fuel has own implementation of pacemaker [1]. It's functionality may be useful in other projects.</div><div><br></div><div>[1] <a href="https://github.com/fuel-infra/puppet-pacemaker">https://github.com/fuel-infra/puppet-pacemaker</a></div></div><div class="gmail_extra"><br clear="all"><div><div class="gmail_signature"><div dir="ltr">--<br>
Best regards,<br>
Sergii Golovatiuk,<br>
Skype #golserge<br>
IRC #holser<br></div></div></div>
<br><div class="gmail_quote">On Sat, Feb 13, 2016 at 6:20 AM, Emilien Macchi <span dir="ltr"><<a href="mailto:emilien.macchi@gmail.com" target="_blank">emilien.macchi@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class=""><p dir="ltr"><br>
On Feb 12, 2016 11:06 PM, "Spencer Krum" <<a href="mailto:nibz@spencerkrum.com" target="_blank">nibz@spencerkrum.com</a>> wrote:<br>
><br>
> The module would also be welcome under the voxpupuli[0] namespace on<br>
> github. We currently have a puppet-corosync[1] module, and there is some<br>
> overlap there, but a pure pacemaker module would be a welcome addition.<br>
><br>
> I'm not sure which I would prefer, just that VP is an option. For<br>
> greater openstack integration, gerrit is the way to go. For greater<br>
> participation from the wider puppet community, github is the way to go.<br>
> Voxpupuli provides testing and releasing infrastructure.</p>
</span><p dir="ltr">The thing is, we might want to gate it on tripleo since it's the first consumer right now. Though I agree VP would be a good place too, to attract more puppet users.</p>
<p dir="ltr">Dilemma!<br>
Maybe we could start using VP, with good testing and see how it works.</p>
<p dir="ltr">Iterate later if needed. Thoughts?</p><div class="HOEnZb"><div class="h5">
<p dir="ltr">><br>
> [0] <a href="https://voxpupuli.org/" target="_blank">https://voxpupuli.org/</a><br>
> [1] <a href="https://github.com/voxpupuli/puppet-corosync" target="_blank">https://github.com/voxpupuli/puppet-corosync</a><br>
><br>
> --<br>
> Spencer Krum<br>
> <a href="mailto:nibz@spencerkrum.com" target="_blank">nibz@spencerkrum.com</a><br>
><br>
> On Fri, Feb 12, 2016, at 09:44 AM, Emilien Macchi wrote:<br>
> > Please look and vote:<br>
> > <a href="https://review.openstack.org/279698" target="_blank">https://review.openstack.org/279698</a><br>
> ><br>
> ><br>
> > Thanks for your feedback!<br>
> ><br>
> > On 02/10/2016 04:04 AM, Juan Antonio Osorio wrote:<br>
> > > I like the idea of moving it to use the OpenStack infrastructure.<br>
> > ><br>
> > > On Wed, Feb 10, 2016 at 12:13 AM, Ben Nemec <<a href="mailto:openstack@nemebean.com" target="_blank">openstack@nemebean.com</a><br>
> > > <mailto:<a href="mailto:openstack@nemebean.com" target="_blank">openstack@nemebean.com</a>>> wrote:<br>
> > ><br>
> > > On 02/09/2016 08:05 AM, Emilien Macchi wrote:<br>
> > > > Hi,<br>
> > > ><br>
> > > > TripleO is currently using puppet-pacemaker [1] which is a module<br>
> > > hosted<br>
> > > > & managed by Github.<br>
> > > > The module was created and mainly maintained by Redhat. It tends to<br>
> > > > break TripleO quite often since we don't have any gate.<br>
> > > ><br>
> > > > I propose to move the module to OpenStack so we'll use OpenStack Infra<br>
> > > > benefits (Gerrit, Releases, Gating, etc). Another idea would be to<br>
> > > gate<br>
> > > > the module with TripleO HA jobs.<br>
> > > ><br>
> > > > The question is, under which umbrella put the module? Puppet ?<br>
> > > TripleO ?<br>
> > > ><br>
> > > > Or no umbrella, like puppet-ceph. <-- I like this idea<br>
> > ><br>
> > ><br>
> > > I think the module not being under an umbrella makes sense.<br>
> > ><br>
> > ><br>
> > > ><br>
> > > > Any feedback is welcome,<br>
> > > ><br>
> > > > [1] <a href="https://github.com/redhat-openstack/puppet-pacemaker" target="_blank">https://github.com/redhat-openstack/puppet-pacemaker</a><br>
> > ><br>
> > > Seems like a module that would be useful outside of TripleO, so it<br>
> > > doesn't seem like it should live under that. Other than that I don't<br>
> > > have enough knowledge of the organization of the puppet modules to<br>
> > > comment.<br>
> > ><br>
> > ><br>
> > ><br>
> > > __________________________________________________________________________<br>
> > > OpenStack Development Mailing List (not for usage questions)<br>
> > > Unsubscribe:<br>
> > > <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
> > > <<a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" target="_blank">http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a>><br>
> > > <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
> > ><br>
> > ><br>
> > ><br>
> > ><br>
> > > --<br>
> > > Juan Antonio Osorio R.<br>
> > > e-mail: <a href="mailto:jaosorior@gmail.com" target="_blank">jaosorior@gmail.com</a> <mailto:<a href="mailto:jaosorior@gmail.com" target="_blank">jaosorior@gmail.com</a>><br>
> > ><br>
> > ><br>
> > ><br>
> > > __________________________________________________________________________<br>
> > > OpenStack Development Mailing List (not for usage questions)<br>
> > > Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
> > > <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
> > ><br>
> ><br>
> > --<br>
> > Emilien Macchi<br>
> ><br>
> > __________________________________________________________________________<br>
> > OpenStack Development Mailing List (not for usage questions)<br>
> > Unsubscribe:<br>
> > <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
> > <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
> > Email had 1 attachment:<br>
> > + signature.asc<br>
> > 1k (application/pgp-signature)<br>
><br>
> __________________________________________________________________________<br>
> OpenStack Development Mailing List (not for usage questions)<br>
> Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
</p>
</div></div><br>__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
<br></blockquote></div><br></div>