Ceph puppet module

Ceph puppet module

[Loic Dachary]

[-- Attachment #1: Type: text/plain, Size: 837 bytes --]

Hi Ceph,

How about creating 

https://github.com/ceph/puppet-ceph 

to federate the development efforts for a puppet module exclusively focused on deploying / maintaining a Ceph cluster ? It looks like we are at a point in time where the fragmentation of the work created a desire for a central place. And the https://github.com/ceph/ seems agreeable to everyone involved.

The discussion initialy started on Ceph + OpenStack + puppet but it seems sensible to separate the OpenStack specific part and host it on https://github.com/stackforge/

The full thread that leads to this proposal is at:

https://groups.google.com/a/puppetlabs.com/d/msg/puppet-openstack/ibnrmXBAxVg/Y3Z3e6sZoa4J

Cheers

-- 
Loïc Dachary, Artisan Logiciel Libre
All that is necessary for the triumph of evil is that good people do nothing.


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 263 bytes --]

Re: Ceph puppet module

[Dan van der Ster]

Hi,
We would support this. The enovance module is a good starting point if
you will accept something that doesn't yet use all the udev magic.
Cheers, Dan
CERN IT

On Wed, Oct 16, 2013 at 10:00 AM, Loic Dachary <loic@dachary.org> wrote:
> Hi Ceph,
>
> How about creating
>
> https://github.com/ceph/puppet-ceph
>
> to federate the development efforts for a puppet module exclusively focused on deploying / maintaining a Ceph cluster ? It looks like we are at a point in time where the fragmentation of the work created a desire for a central place. And the https://github.com/ceph/ seems agreeable to everyone involved.
>
> The discussion initialy started on Ceph + OpenStack + puppet but it seems sensible to separate the OpenStack specific part and host it on https://github.com/stackforge/
>
> The full thread that leads to this proposal is at:
>
> https://groups.google.com/a/puppetlabs.com/d/msg/puppet-openstack/ibnrmXBAxVg/Y3Z3e6sZoa4J
>
> Cheers
>
> --
> Loïc Dachary, Artisan Logiciel Libre
> All that is necessary for the triumph of evil is that good people do nothing.
>
--
To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: Ceph puppet module

[Sébastien Han]

Hi Dan,

During the cephdays you mentioned that you were about to redistribute all the changes you’ve made on puppet-ceph to the enovance repo.
It would be great to merge both before starting anything.

What’s the progress?

Thanks :)

––––
Sébastien Han
Cloud Engineer

"Always give 100%. Unless you're giving blood.”

Phone: +33 (0)1 49 70 99 72
Mail: sebastien.han@enovance.com
Address : 10, rue de la Victoire - 75009 Paris
Web : www.enovance.com - Twitter : @enovance

On October 16, 2013 at 11:37:44 AM, Dan van der Ster (dan@vanderster.com) wrote:
>
>Hi,
>We would support this. The enovance module is a good starting point if
>you will accept something that doesn't yet use all the udev magic.
>Cheers, Dan
>CERN IT
>
>On Wed, Oct 16, 2013 at 10:00 AM, Loic Dachary wrote:
>> Hi Ceph,
>>
>> How about creating
>>
>> https://github.com/ceph/puppet-ceph
>>
>> to federate the development efforts for a puppet module exclusively focused on deploying / maintaining a Ceph cluster ? It looks like we are at a point in time where the fragmentation of the work created a desire for a central place. And the https://github.com/ceph/ seems agreeable to everyone involved.
>>
>> The discussion initialy started on Ceph + OpenStack + puppet but it seems sensible to separate the OpenStack specific part and host it on https://github.com/stackforge/
>>
>> The full thread that leads to this proposal is at:
>>
>> https://groups.google.com/a/puppetlabs.com/d/msg/puppet-openstack/ibnrmXBAxVg/Y3Z3e6sZoa4J
>>
>> Cheers
>>
>> --
>> Loïc Dachary, Artisan Logiciel Libre
>> All that is necessary for the triumph of evil is that good people do nothing.
>>
>--
>To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
>the body of a message to majordomo@vger.kernel.org
>More majordomo info at http://vger.kernel.org/majordomo-info.html
>

--
To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: Ceph puppet module

[Dan van der Ster]

Hi,

On Wed, Oct 16, 2013 at 1:22 PM, Sébastien Han
<sebastien.han@enovance.com> wrote:
> Hi Dan,
>
> During the cephdays you mentioned that you were about to redistribute all the changes you’ve made on puppet-ceph to the enovance repo.
> It would be great to merge both before starting anything.
>
> What’s the progress?

I don't think this will happen before mid-November, based on upcoming
work and travel. But I honestly don't think our changes should block
the move of puppet-ceph to ceph.com

Cheers, Dan
--
To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: Ceph puppet module

[Sage Weil]

On Wed, 16 Oct 2013, Dan van der Ster wrote:
> Hi,
> We would support this. The enovance module is a good starting point if
> you will accept something that doesn't yet use all the udev magic.

My only concern is that it may be challenging to make a smooth transition 
from the old-style to new-style udev goodness.  Something to consider!

sage


> Cheers, Dan
> CERN IT
> 
> On Wed, Oct 16, 2013 at 10:00 AM, Loic Dachary <loic@dachary.org> wrote:
> > Hi Ceph,
> >
> > How about creating
> >
> > https://github.com/ceph/puppet-ceph
> >
> > to federate the development efforts for a puppet module exclusively focused on deploying / maintaining a Ceph cluster ? It looks like we are at a point in time where the fragmentation of the work created a desire for a central place. And the https://github.com/ceph/ seems agreeable to everyone involved.
> >
> > The discussion initialy started on Ceph + OpenStack + puppet but it seems sensible to separate the OpenStack specific part and host it on https://github.com/stackforge/
> >
> > The full thread that leads to this proposal is at:
> >
> > https://groups.google.com/a/puppetlabs.com/d/msg/puppet-openstack/ibnrmXBAxVg/Y3Z3e6sZoa4J
> >
> > Cheers
> >
> > --
> > Lo?c Dachary, Artisan Logiciel Libre
> > All that is necessary for the triumph of evil is that good people do nothing.
> >
> --
> To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 
> 

Re: Ceph puppet module

[Andrew Woodward]

We need to have a reasonable license on this preferably Apache 2.0.
the enovance module is AGPL which can't come in contact with nearly
anything with out causing massive license issues. Starting with any of
the enovance code is a Non-starter as it will require the AGPL
License.

On Wed, Oct 16, 2013 at 2:36 AM, Dan van der Ster <dan@vanderster.com> wrote:
> Hi,
> We would support this. The enovance module is a good starting point if
> you will accept something that doesn't yet use all the udev magic.
> Cheers, Dan
> CERN IT
>
> On Wed, Oct 16, 2013 at 10:00 AM, Loic Dachary <loic@dachary.org> wrote:
>> Hi Ceph,
>>
>> How about creating
>>
>> https://github.com/ceph/puppet-ceph
>>
>> to federate the development efforts for a puppet module exclusively focused on deploying / maintaining a Ceph cluster ? It looks like we are at a point in time where the fragmentation of the work created a desire for a central place. And the https://github.com/ceph/ seems agreeable to everyone involved.
>>
>> The discussion initialy started on Ceph + OpenStack + puppet but it seems sensible to separate the OpenStack specific part and host it on https://github.com/stackforge/
>>
>> The full thread that leads to this proposal is at:
>>
>> https://groups.google.com/a/puppetlabs.com/d/msg/puppet-openstack/ibnrmXBAxVg/Y3Z3e6sZoa4J
>>
>> Cheers
>>
>> --
>> Loďc Dachary, Artisan Logiciel Libre
>> All that is necessary for the triumph of evil is that good people do nothing.
>>
> --
> To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html



-- 
If google has done it, Google did it right!
--
To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

RE: Ceph puppet module

[Don Talton (dotalton)]

This is one of the reasons Cisco pushed to create puppet-cephdeploy (Apache 2.0). I agree with your sentiment, and think that Apache 2.0 is ideal.

> -----Original Message-----
> From: ceph-devel-owner@vger.kernel.org [mailto:ceph-devel-
> owner@vger.kernel.org] On Behalf Of Andrew Woodward
> Sent: Thursday, October 17, 2013 1:29 PM
> Cc: Ceph Development
> Subject: Re: Ceph puppet module
> 
> We need to have a reasonable license on this preferably Apache 2.0.
> the enovance module is AGPL which can't come in contact with nearly
> anything with out causing massive license issues. Starting with any of the
> enovance code is a Non-starter as it will require the AGPL License.
> 
> On Wed, Oct 16, 2013 at 2:36 AM, Dan van der Ster <dan@vanderster.com>
> wrote:
> > Hi,
> > We would support this. The enovance module is a good starting point if
> > you will accept something that doesn't yet use all the udev magic.
> > Cheers, Dan
> > CERN IT
> >
> > On Wed, Oct 16, 2013 at 10:00 AM, Loic Dachary <loic@dachary.org> wrote:
> >> Hi Ceph,
> >>
> >> How about creating
> >>
> >> https://github.com/ceph/puppet-ceph
> >>
> >> to federate the development efforts for a puppet module exclusively
> focused on deploying / maintaining a Ceph cluster ? It looks like we are at a
> point in time where the fragmentation of the work created a desire for a
> central place. And the https://github.com/ceph/ seems agreeable to
> everyone involved.
> >>
> >> The discussion initialy started on Ceph + OpenStack + puppet but it
> >> seems sensible to separate the OpenStack specific part and host it on
> >> https://github.com/stackforge/
> >>
> >> The full thread that leads to this proposal is at:
> >>
> >> https://groups.google.com/a/puppetlabs.com/d/msg/puppet-
> openstack/ibn
> >> rmXBAxVg/Y3Z3e6sZoa4J
> >>
> >> Cheers
> >>
> >> --
> >> Loďc Dachary, Artisan Logiciel Libre
> >> All that is necessary for the triumph of evil is that good people do nothing.
> >>
> > --
> > To unsubscribe from this list: send the line "unsubscribe ceph-devel"
> > in the body of a message to majordomo@vger.kernel.org More
> majordomo
> > info at  http://vger.kernel.org/majordomo-info.html
> 
> 
> 
> --
> If google has done it, Google did it right!
> --
> To unsubscribe from this list: send the line "unsubscribe ceph-devel" in the
> body of a message to majordomo@vger.kernel.org More majordomo info at
> http://vger.kernel.org/majordomo-info.html

Re: Ceph puppet module

[Danny Al-Gaaf]

Am 17.10.2013 22:29, schrieb Andrew Woodward:
> We need to have a reasonable license on this preferably Apache 2.0.
> the enovance module is AGPL which can't come in contact with nearly
> anything with out causing massive license issues. Starting with any of
> the enovance code is a Non-starter as it will require the AGPL
> License.

I agree with the Apache license.

Would it be an option to ask enovance (and the contributers) to
relicense under Apache v2.0? I would be happy to do that for my
contributions.

Danny

Re: Ceph puppet module

[Andrew Woodward]

Danny,

It would be great if it is accepted. It would require as you noted,
all contributers (external of enovance's employ if they have
delegation of rights terms with their employees) and enovance's
approval as well.

On Thu, Oct 17, 2013 at 3:15 PM, Danny Al-Gaaf <danny.al-gaaf@bisect.de> wrote:
> Am 17.10.2013 22:29, schrieb Andrew Woodward:
>> We need to have a reasonable license on this preferably Apache 2.0.
>> the enovance module is AGPL which can't come in contact with nearly
>> anything with out causing massive license issues. Starting with any of
>> the enovance code is a Non-starter as it will require the AGPL
>> License.
>
> I agree with the Apache license.
>
> Would it be an option to ask enovance (and the contributers) to
> relicense under Apache v2.0? I would be happy to do that for my
> contributions.
>
> Danny
>
>



-- 
If google has done it, Google did it right!