Open Stack

The module would also be welcome under the voxpupuli[0] namespace on
github. We currently have a puppet-corosync[1] module, and there is some
overlap there, but a pure pacemaker module would be a welcome addition.

I'm not sure which I would prefer, just that VP is an option. For
greater openstack integration, gerrit is the way to go. For greater
participation from the wider puppet community, github is the way to go.
Voxpupuli provides testing and releasing infrastructure.


[0] https://voxpupuli.org/
[1] https://github.com/voxpupuli/puppet-corosync

-- 
  Spencer Krum
  nibz at spencerkrum.com

On Fri, Feb 12, 2016, at 09:44 AM, Emilien Macchi wrote:
> Please look and vote:
> https://review.openstack.org/279698
> 
> 
> Thanks for your feedback!
> 
> On 02/10/2016 04:04 AM, Juan Antonio Osorio wrote:
> > I like the idea of moving it to use the OpenStack infrastructure.
> > 
> > On Wed, Feb 10, 2016 at 12:13 AM, Ben Nemec <openstack at nemebean.com
> > <mailto:openstack at nemebean.com>> wrote:
> > 
> >     On 02/09/2016 08:05 AM, Emilien Macchi wrote:
> >     > Hi,
> >     >
> >     > TripleO is currently using puppet-pacemaker [1] which is a module
> >     hosted
> >     > & managed by Github.
> >     > The module was created and mainly maintained by Redhat. It tends to
> >     > break TripleO quite often since we don't have any gate.
> >     >
> >     > I propose to move the module to OpenStack so we'll use OpenStack Infra
> >     > benefits (Gerrit, Releases, Gating, etc). Another idea would be to
> >     gate
> >     > the module with TripleO HA jobs.
> >     >
> >     > The question is, under which umbrella put the module? Puppet ?
> >     TripleO ?
> >     >
> >     > Or no umbrella, like puppet-ceph. <-- I like this idea
> > 
> > 
> > I think the module not being under an umbrella makes sense.
> >  
> > 
> >     >
> >     > Any feedback is welcome,
> >     >
> >     > [1] https://github.com/redhat-openstack/puppet-pacemaker
> > 
> >     Seems like a module that would be useful outside of TripleO, so it
> >     doesn't seem like it should live under that.  Other than that I don't
> >     have enough knowledge of the organization of the puppet modules to
> >     comment.
> > 
> > 
> > 
> >     __________________________________________________________________________
> >     OpenStack Development Mailing List (not for usage questions)
> >     Unsubscribe:
> >     OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> >     <http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe>
> >     http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> > 
> > 
> > 
> > 
> > -- 
> > Juan Antonio Osorio R.
> > e-mail: jaosorior at gmail.com <mailto:jaosorior at gmail.com>
> > 
> > 
> > 
> > __________________________________________________________________________
> > OpenStack Development Mailing List (not for usage questions)
> > Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> > 
> 
> -- 
> Emilien Macchi
> 
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe:
> OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> Email had 1 attachment:
> + signature.asc
>   1k (application/pgp-signature)