I like the idea of moving it to use the OpenStack infrastructure. On Wed, Feb 10, 2016 at 12:13 AM, Ben Nemec <openst...@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-requ...@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > -- Juan Antonio Osorio R. e-mail: jaosor...@gmail.com
__________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
