Re: [ceph-users] Fwd: Ceph team involvement in Rook (Deploying Ceph in Kubernetes)

2018-01-21 Thread Hans van den Bogert 
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  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  
> To: ceph-users  ,
> Squid Cybernetic  ,
> Dan Mick  , Chen, Huamin
>  , John Spray 
> , Sage Weil  ,
> 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

Re: [ceph-users] Fwd: Ceph team involvement in Rook (Deploying Ceph in Kubernetes)

2018-01-19 Thread Marc Roos 
 
Are the guys of apache mesos agreeing to this? I have been looking at 
mesos, dcos and still have to make up my mind which way to go. I like 
that mesos has the unified containerizer that runs the docker images and 
I don’t need to run the dockerd, how the adapt the to the cni standard. 
How is this going with kubernetes? Link maybe to why I should use 
kubernetes?



-Original Message-
From: Kai Wagner [mailto:kwag...@suse.com] 
Sent: vrijdag 19 januari 2018 11:55
To: Ceph Users
Subject: [ceph-users] Fwd: Ceph team involvement in Rook (Deploying Ceph 
in Kubernetes)

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> 
<mailto:s...@redhat.com> 
To: ceph-users <ceph-users@lists.ceph.com> 
<mailto:ceph-users@lists.ceph.com> , Squid Cybernetic 
<ceph-de...@vger.kernel.org> 
<mailto:ceph-de...@vger.kernel.org> , Dan Mick <dm...@redhat.com> 
<mailto:dm...@redhat.com> , Chen, Huamin <hc...@redhat.com> 
<mailto:hc...@redhat.com> , John Spray <jsp...@redhat.com> 
<mailto:jsp...@redhat.com> , Sage Weil <sw...@redhat.com> 
<mailto: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 read 
http://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] Fwd: Ceph team involvement in Rook (Deploying Ceph in Kubernetes)

2018-01-19 Thread Kai Wagner 
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 
To: ceph-users , Squid Cybernetic
, Dan Mick , Chen, Huamin
, John Spray , Sage Weil
, 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 read
http://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



signature.asc
Description: OpenPGP digital signature
___
ceph-users mailing list
ceph-users@lists.ceph.com
http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com