<div dir="ltr">I'd be happy to see more collaboration here as well, I'd like to hear from the maintainers on both sides identify some of what isn't implemented on each so we can better decide which one to continue from, develop feature parity and then switch to.<br></div><br><div class="gmail_quote"><div dir="ltr">On Thu, Mar 17, 2016 at 12:03 PM Emilien Macchi <<a href="mailto:emilien@redhat.com">emilien@redhat.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On Thu, Mar 17, 2016 at 2:22 PM, Sergii Golovatiuk<br>
<<a href="mailto:sgolovatiuk@mirantis.com" target="_blank">sgolovatiuk@mirantis.com</a>> wrote:<br>
> Guys,<br>
><br>
> Fuel has own implementation of pacemaker [1]. It's functionality may be<br>
> useful in other projects.<br>
><br>
> [1] <a href="https://github.com/fuel-infra/puppet-pacemaker" rel="noreferrer" target="_blank">https://github.com/fuel-infra/puppet-pacemaker</a><br>
<br>
I'm afraid to see 3 duplicated efforts to deploy Pacemaker:<br>
<br>
* puppetlabs/corosync, not much maintained and not suitable for Red<br>
Hat for some reasons related to the way to use pcs.<br>
* openstack/puppet-pacemaker, only working on Red Hat systems,<br>
suitable for TripleO and previous Red Hat installers.<br>
* fuel-infra/puppet-pacemaker, which looks like a more robust<br>
implementation of puppetlabs/corosync.<br>
<br>
It's pretty clear Mirantis and Red hat, both OpenStack major<br>
contributors who deploy Pacemaker do not use puppetlabs/corosync but<br>
have their own implementations.<br>
Maybe it would be time to converge at some point. I see a lot of<br>
potential in fuel-infra/puppet-pacemaker to be honest. After reading<br>
the code, I think it's still missing some features we might need to<br>
make it work on TripleO but we could work together at establishing the<br>
list of missing pieces and discuss about implementing them, so our<br>
modules would converge.<br>
<br>
I don't mind using X or Y tool, I want the best one and it seems both<br>
of our groups have some expertise that could help to maybe one day<br>
replace puppetlabs/corosync code by Fuel & Red Hat's module.<br>
What do you think?<br>
<br>
><br>
> --<br>
> Best regards,<br>
> Sergii Golovatiuk,<br>
> Skype #golserge<br>
> IRC #holser<br>
><br>
> On Sat, Feb 13, 2016 at 6:20 AM, Emilien Macchi <<a href="mailto:emilien.macchi@gmail.com" target="_blank">emilien.macchi@gmail.com</a>><br>
> wrote:<br>
>><br>
>><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.<br>
>><br>
>> The thing is, we might want to gate it on tripleo since it's the first<br>
>> consumer right now. Though I agree VP would be a good place too, to attract<br>
>> more puppet users.<br>
>><br>
>> Dilemma!<br>
>> Maybe we could start using VP, with good testing and see how it works.<br>
>><br>
>> Iterate later if needed. Thoughts?<br>
>><br>
>> ><br>
>> > [0] <a href="https://voxpupuli.org/" rel="noreferrer" target="_blank">https://voxpupuli.org/</a><br>
>> > [1] <a href="https://github.com/voxpupuli/puppet-corosync" rel="noreferrer" 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" rel="noreferrer" 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<br>
>> > > > module<br>
>> > > > hosted<br>
>> > > > > & managed by Github.<br>
>> > > > > The module was created and mainly maintained by Redhat. It<br>
>> > > > 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<br>
>> > > > OpenStack Infra<br>
>> > > > > benefits (Gerrit, Releases, Gating, etc). Another idea would<br>
>> > > > 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" rel="noreferrer" target="_blank">https://github.com/redhat-openstack/puppet-pacemaker</a><br>
>> > > ><br>
>> > > > Seems like a module that would be useful outside of TripleO, so<br>
>> > > > it<br>
>> > > > doesn't seem like it should live under that. Other than that I<br>
>> > > > don't<br>
>> > > > have enough knowledge of the organization of the puppet modules<br>
>> > > > to<br>
>> > > > comment.<br>
>> > > ><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" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
>> > > ><br>
>> > > > <<a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a>><br>
>> > > ><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>
>> > > ><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>
>> > > > __________________________________________________________________________<br>
>> > > > OpenStack Development Mailing List (not for usage questions)<br>
>> > > > Unsubscribe:<br>
>> > > > <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>
>> > ><br>
>> > > --<br>
>> > > Emilien Macchi<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" 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>
>> > > Email had 1 attachment:<br>
>> > > + signature.asc<br>
>> > > 1k (application/pgp-signature)<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" 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>
>><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>
><br>
><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>
<br>
<br>
<br>
--<br>
Emilien Macchi<br>
<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>
</blockquote></div><div dir="ltr">-- <br></div><div dir="ltr"><p dir="ltr">--</p><p dir="ltr"><span style="font-size:13.1999998092651px">Andrew Woodward</span></p><p dir="ltr"><span style="font-size:13.1999998092651px">Mirantis</span></p><p dir="ltr"><span style="font-size:13.1999998092651px">Fuel Community Ambassador</span></p><p dir="ltr"><span style="font-size:13.1999998092651px">Ceph Community</span></p>
</div>