Re: [openstack-dev] [tripleo] [puppet] move puppet-pacemaker

On Wed, Mar 23, 2016 at 09:58:17AM +0100, Sofer Athlan-Guyot wrote: > > Can I change the interface of pcmk_resource? > > > > You have pcmk_constraint but I have pcmk_location/colocation/order > > separately. I can merge then into a single resource like you did > > or I can keep them separated. Or

Re: [openstack-dev] [tripleo] [puppet] move puppet-pacemaker

Dmitry Ilyin writes: > I've started my merging effort here > https://github.com/dmitryilyin/openstack-puppet-pacemaker Great, thanks. > > Can I change the interface of pcmk_resource? > > You have pcmk_constraint but I have pcmk_location/colocation/order > separately. I can

Re: [openstack-dev] [tripleo] [puppet] move puppet-pacemaker

I've started my merging effort here https://github.com/dmitryilyin/openstack-puppet-pacemaker Can I change the interface of pcmk_resource? You have pcmk_constraint but I have pcmk_location/colocation/order separately. I can merge then into a single resource like you did or I can keep them

Re: [openstack-dev] [tripleo] [puppet] move puppet-pacemaker

Hi, I've been working on it lately, mainly adding idempotency and beaker jobs to the openstack/puppet-pacemaker version. Such a merge would be great. I'm in for such project. Emilien Macchi writes: > On Fri, Mar 18, 2016 at 10:55 AM, Dmitry Ilyin

Re: [openstack-dev] [tripleo] [puppet] move puppet-pacemaker

Guys, Fuel has own implementation of pacemaker [1]. It's functionality may be useful in other projects. [1] https://github.com/fuel-infra/puppet-pacemaker -- Best regards, Sergii Golovatiuk, Skype #golserge IRC #holser On Sat, Feb 13, 2016 at 6:20 AM, Emilien Macchi

Re: [openstack-dev] [tripleo] [puppet] move puppet-pacemaker

Hello. I'm the author of fuel-infra/puppet-pacemaker and I guess I would be able to merge the code from "fuel-infra/puppet-pacemaker" to "openstack/puppet-pacemaker" We will be having a single set of pcmk_* types and two providers for the each type: "pcs" and "xml", there is also a "noop"

Re: [openstack-dev] [tripleo] [puppet] move puppet-pacemaker

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. On Thu, Mar 17, 2016 at 12:03 PM Emilien Macchi

Re: [openstack-dev] [tripleo] [puppet] move puppet-pacemaker

On Thu, Mar 17, 2016 at 2:22 PM, Sergii Golovatiuk wrote: > Guys, > > Fuel has own implementation of pacemaker [1]. It's functionality may be > useful in other projects. > > [1] https://github.com/fuel-infra/puppet-pacemaker I'm afraid to see 3 duplicated efforts to

Re: [openstack-dev] [tripleo] [puppet] move puppet-pacemaker

On Fri, Mar 18, 2016 at 10:55 AM, Dmitry Ilyin wrote: > Hello. > > I'm the author of fuel-infra/puppet-pacemaker and I guess I would be able to > merge the code from "fuel-infra/puppet-pacemaker" to > "openstack/puppet-pacemaker" > We will be having a single set of pcmk_*

Re: [openstack-dev] [tripleo] [puppet] move puppet-pacemaker

On Feb 12, 2016 11:06 PM, "Spencer Krum" wrote: > > 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. > >

Re: [openstack-dev] [tripleo] [puppet] move puppet-pacemaker

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

Re: [openstack-dev] [tripleo] [puppet] move puppet-pacemaker

I like the idea of moving it to use the OpenStack infrastructure. On Wed, Feb 10, 2016 at 12:13 AM, Ben Nemec 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

[openstack-dev] [tripleo] [puppet] move puppet-pacemaker

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

Re: [openstack-dev] [tripleo] [puppet] move puppet-pacemaker

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