Should I summarize this is ceph-helm being being EOL? If I'm spinning up a toy cluster for a homelab, should I invest time in Rook, or stay with ceph-helm for now?
On Fri, Jan 19, 2018 at 11:55 AM, Kai Wagner <kwag...@suse.com> wrote: > Just for those of you who are not subscribed to ceph-users. > > > -------- Forwarded Message -------- > Subject: Ceph team involvement in Rook (Deploying Ceph in Kubernetes) > Date: Fri, 19 Jan 2018 11:49:05 +0100 > From: Sebastien Han <s...@redhat.com> <s...@redhat.com> > To: ceph-users <ceph-users@lists.ceph.com> <ceph-users@lists.ceph.com>, > Squid Cybernetic <ceph-de...@vger.kernel.org> <ceph-de...@vger.kernel.org>, > Dan Mick <dm...@redhat.com> <dm...@redhat.com>, Chen, Huamin > <hc...@redhat.com> <hc...@redhat.com>, John Spray <jsp...@redhat.com> > <jsp...@redhat.com>, Sage Weil <sw...@redhat.com> <sw...@redhat.com>, > bas...@tabbara.com > > Everyone, > > Kubernetes is getting bigger and bigger. It has become the platform of > choice to run microservices applications in containers, just like > OpenStack did for and Cloud applications in virtual machines. > > When it comes to container storage there are three key aspects: > > * Providing persistent storage to containers, Ceph has drivers in > Kuberntes already with kRBD and CephFS > * Containerizing the storage itself, so efficiently running Ceph > services in Containers. Currently, we have ceph-container > (https://github.com/ceph/ceph-container) > * Deploying the containerized storage in Kubernetes, we wrote > ceph-helm charts (https://github.com/ceph/ceph-helm) > > The third piece although it's working great has a particular goal and > doesn't aim to run Ceph just like any other applications in Kuberntes. > We were also looking for a better abstraction/ease of use for > end-users, multi-cluster support, operability, life-cycle management, > centralized operations, to learn more you can > readhttp://lists.ceph.com/pipermail/ceph-users-ceph.com/2017-October/021918.html. > As a consequence, we decided to look at what the ecosystem had to > offer. As a result, Rook came out, as a pleasant surprise. For those > who are not familiar with Rook, please visit https://rook.io but in a > nutshell, Rook is an open source orchestrator for distributed storage > systems running in cloud-native environments. Under the hood, Rook is > deploying, operating and managing Ceph life cycle in Kubernetes. Rook > has a vibrant community and committed developers. > > Even if Rook is not perfect (yet), it has firm foundations, and we are > planning on helping to make it better. We already opened issues for > that and started doing work with Rook's core developers. We are > looking at reconciling what is available today > (rook/ceph-container/helm), reduce the overlap/duplication and all > work together toward a single and common goal. With this > collaboration, through Rook, we hope to make Ceph the de facto Open > Source storage solution for Kubernetes. > > These are exciting times, so if you're a user, a developer, or merely > curious, have a look at Rook and send us feedback! > > Thanks! > -- > Cheers > > –––––– > Sébastien Han > Principal Software Engineer, Storage Architect > > "Always give 100%. Unless you're giving blood." > > Mail: s...@redhat.com > Address: 11 bis, rue Roquépine - 75008 Paris > -- > To unsubscribe from this list: send the line "unsubscribe ceph-devel" in > the body of a message to majord...@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html > > > _______________________________________________ > ceph-users mailing list > ceph-users@lists.ceph.com > http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com > >
_______________________________________________ ceph-users mailing list ceph-users@lists.ceph.com http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
