All of lore.kernel.org
 help / color / mirror / Atom feed
From: Loic Dachary <loic@dachary.org>
To: Andrew Woodward <xarses@gmail.com>,
	David Moreau Simard <dms@redhat.com>,
	Ceph Development <ceph-devel@vger.kernel.org>,
	ceph-users <ceph-users@lists.ceph.com>,
	Ceph User Committee <ceph-community@lists.ceph.com>
Cc: openstack-dev@lists.openstack.org
Subject: Re: [ceph-users] [puppet] Moving puppet-ceph to the Openstack big tent
Date: Wed, 30 Sep 2015 00:11:28 +0200	[thread overview]
Message-ID: <560B0C90.1000500@dachary.org> (raw)
In-Reply-To: <CACEfbZjcC7AR3SXNrepxM=KAX64WXCtGxeHhnOKQ-PmCZU73gg@mail.gmail.com>

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

Good move :-)

On 29/09/2015 23:45, Andrew Woodward wrote:
> [I'm cross posting this to the other Ceph threads to ensure that it's seen]
> 
> We've discussed this on Monday on IRC and again in the puppet-openstack IRC meeting. The current census is that we will move from the deprecated stackforge organization and will be moved to the openstack one. At this time we will not be perusing membership as a formal OpenStack project. This will allow puppet-ceph to retain the tight relationship with OpenStack community and tools for the time being. 
> 
> On Mon, Sep 28, 2015 at 8:32 AM David Moreau Simard <dms@redhat.com <mailto:dms@redhat.com>> wrote:
> 
>     Hi,
> 
>     puppet-ceph currently lives in stackforge [1] which is being retired
>     [2]. puppet-ceph is also mirrored on the Ceph Github organization [3].
>     This version of the puppet-ceph module was created from scratch and
>     not as a fork of the (then) upstream puppet-ceph by Enovance [4].
>     Today, the version by Enovance is no longer officially maintained
>     since Red Hat has adopted the new release.
> 
>     Being an Openstack project under Stackforge or Openstack brings a lot
>     of benefits but it's not black and white, there are cons too.
> 
>     It provides us with the tools, the processes and the frameworks to
>     review and test each contribution to ensure we ship a module that is
>     stable and is held to the highest standards.
>     But it also means that:
>     - We forego some level of ownership back to the Openstack foundation,
>     it's technical committee and the Puppet Openstack PTL.
>     - puppet-ceph contributors will also be required to sign the
>     Contributors License Agreement and jump through the Gerrit hoops [5]
>     which can make contributing to the project harder.
> 
>     We have put tremendous efforts into creating a quality module and as
>     such it was the first puppet module in the stackforge organization to
>     implement not only unit tests but also integration tests with third
>     party CI.
>     Integration testing for other puppet modules are just now starting to
>     take shape by using the Openstack CI inrastructure.
> 
>     In the context of Openstack, RDO already ships with a mean to install
>     Ceph with this very module and Fuel will be adopting it soon as well.
>     This means the module will benefit from real world experience and
>     improvements by the Openstack community and packagers.
>     This will help further reinforce that not only Ceph is the best
>     unified storage solution for Openstack but that we have means to
>     deploy it in the real world easily.
> 
>     We all know that Ceph is also deployed outside of this context and
>     this is why the core reviewers make sure that contributions remain
>     generic and usable outside of this use case.
> 
>     Today, the core members of the project discussed whether or not we
>     should move puppet-ceph to the Openstack big tent and we had a
>     consensus approving the move.
>     We would also like to hear the thoughts of the community on this topic.
> 
>     Please let us know what you think.
> 
>     Thanks,
> 
>     [1]: https://github.com/stackforge/puppet-ceph
>     [2]: https://review.openstack.org/#/c/192016/
>     [3]: https://github.com/ceph/puppet-ceph
>     [4]: https://github.com/redhat-cip/puppet-ceph
>     [5]: https://wiki.openstack.org/wiki/How_To_Contribute
> 
>     David Moreau Simard
>     --
>     To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
>     the body of a message to majordomo@vger.kernel.org <mailto:majordomo@vger.kernel.org>
>     More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 
> -- 
> 
> --
> 
> Andrew Woodward
> 
> Mirantis
> 
> Fuel Community Ambassador
> 
> Ceph Community
> 
> 
> 
> _______________________________________________
> ceph-users mailing list
> ceph-users@lists.ceph.com
> http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
> 

-- 
Loïc Dachary, Artisan Logiciel Libre


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

      reply	other threads:[~2015-09-29 22:11 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-28 15:31 [puppet] Moving puppet-ceph to the Openstack big tent David Moreau Simard
     [not found] ` <CAH7C+Pr2rA65O8gm3B1A64fFPctb_-q=jE=a6AHKJcfHNY1OEw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-09-29 21:45   ` Andrew Woodward
2015-09-29 22:11     ` Loic Dachary [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=560B0C90.1000500@dachary.org \
    --to=loic@dachary.org \
    --cc=ceph-community@lists.ceph.com \
    --cc=ceph-devel@vger.kernel.org \
    --cc=ceph-users@lists.ceph.com \
    --cc=dms@redhat.com \
    --cc=openstack-dev@lists.openstack.org \
    --cc=xarses@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.