CEPH filesystem development
 help / color / mirror / Atom feed
From: Danny Al-Gaaf <danny.al-gaaf@bisect.de>
To: Sage Weil <sage@inktank.com>,
	ceph-devel@vger.kernel.org, ceph-users@ceph.com
Subject: Re: Red Hat to acquire Inktank
Date: Wed, 30 Apr 2014 22:34:18 +0200	[thread overview]
Message-ID: <53615E4A.1050004@bisect.de> (raw)
In-Reply-To: <alpine.DEB.2.00.1404300514590.14568@cobra.newdream.net>

Am 30.04.2014 14:18, schrieb Sage Weil:
> Today we are announcing some very big news: Red Hat is acquiring Inktank. 
> We are very excited about what this means for Ceph, the community, the 
> team, our partners, and our customers. Ceph has come a long way in the ten 
> years since the first line of code has been written, particularly over the 
> last two years that Inktank has been focused on its development. The fifty 
> members of the Inktank team, our partners, and the hundreds of other 
> contributors have done amazing work in bringing us to where we are today.
> 
> We believe that, as part of Red Hat, the Inktank team will be able to 
> build a better quality Ceph storage platform that will benefit the entire 
> ecosystem. Red Hat brings a broad base of expertise in building and 
> delivering hardened software stacks as well as a wealth of resources that 
> will help Ceph become the transformative and ubiquitous storage platform 
> that we always believed it could be.

What does that mean to the idea/plans to move Ceph to a Foundation? Are
they canceled?

Danny



  parent reply	other threads:[~2014-04-30 20:34 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-30 12:18 Red Hat to acquire Inktank Sage Weil
2014-04-30 13:27 ` [ceph-users] " Haomai Wang
     [not found]   ` <CACJqLybsq1Q3YRjGOPnqRK+RsvPQnHO8b9Ft096G_P_4Yem-Tg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-04-30 13:48     ` Travis Rhoden
2014-04-30 17:05 ` Mike Hanby
     [not found] ` <alpine.DEB.2.00.1404300514590.14568-vIokxiIdD2AQNTJnQDzGJqxOck334EZe@public.gmane.org>
2014-04-30 12:46   ` Asif Murad Khan
2014-04-30 13:01   ` Alexandre DERUMIER
2014-04-30 16:05   ` Pawel Stefanski
2014-04-30 16:07   ` Pawel Stefanski
2014-04-30 16:46     ` [ceph-users] " Ketor D
     [not found]     ` <CAC96waFOcyVMcZ08KX69oEfqP7m3hSH0gZTF14KYmNst5qfjrw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-05-02  4:49       ` Suresh Sadhu
2014-04-30 18:29   ` Zach Hill
2014-04-30 20:21   ` Gandalf Corvotempesta
     [not found]     ` <CAJH6TXieGN0WhXaw5Q-EKTb7nWFrV3NRaErzy0KK1fV3bK4nVQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-04-30 20:27       ` Mark Nelson
2014-04-30 22:05         ` [ceph-users] " Gandalf Corvotempesta
2014-04-30 22:11           ` Mark Nelson
     [not found]             ` <53617523.90400-4GqslpFJ+cxBDgjK7y7TUQ@public.gmane.org>
2014-04-30 22:17               ` Gandalf Corvotempesta
2014-04-30 22:20                 ` [ceph-users] " Matt W. Benjamin
2014-04-30 22:33                   ` Gandalf Corvotempesta
2014-04-30 22:37                     ` Matt W. Benjamin
2014-04-30 22:52                     ` Mark Nelson
2014-04-30 20:28     ` Infiniband: was: " Matt W. Benjamin
2014-04-30 20:34 ` Danny Al-Gaaf [this message]
     [not found]   ` <53615E4A.1050004-2YacvwyR+KOzQB+pC5nmwQ@public.gmane.org>
2014-04-30 20:46     ` Patrick McGarry

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=53615E4A.1050004@bisect.de \
    --to=danny.al-gaaf@bisect.de \
    --cc=ceph-devel@vger.kernel.org \
    --cc=ceph-users@ceph.com \
    --cc=sage@inktank.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox