Ceph-mesos » History » Version 5
Zhongyue Luo, 06/16/2015 12:07 AM
1 | 2 | Zhongyue Luo | h3. +*Ceph on Apache Mesos*+ |
---|---|---|---|
2 | 1 | Zhongyue Luo | |
3 | *Summary* |
||
4 | 2 | Zhongyue Luo | The ceph-mesos project is a Apache Mesos framework for scaling a Ceph cluster. The framework scheduler decides which Ceph binaries to execute and the framework executors launch Ceph Docker containers on Mesos slaves accordingly. |
5 | 1 | Zhongyue Luo | |
6 | *Owners* |
||
7 | Zhongyue Nah (Intel) |
||
8 | Zhankun Tang (Intel) |
||
9 | Zhidong Yu (Intel) |
||
10 | |||
11 | *Interested Parties* |
||
12 | 4 | Zhongyue Luo | Zhongyue Nah (Intel) |
13 | 1 | Zhongyue Luo | |
14 | *Current Status* |
||
15 | 2 | Zhongyue Luo | The ceph-mesos project is external to the Ceph project. Currently it is under testing and will soon release it's initial version. |
16 | 1 | Zhongyue Luo | |
17 | *Detailed Description* |
||
18 | 2 | Zhongyue Luo | Big Data analytics is a hot issue in enterprise IT. However Big Data analytics consists of many components that it is a challenge to manage all applications in a significantly large cluster of hosts. The Apache Mesos project is one of the most promising solutions in datacenter management. It provides a high level interface for managing applications running in a datacenter that adding new applications hardly increases management entropy. |
19 | |||
20 | 5 | Zhongyue Luo | In conjunction with the [[Hadoop_over_Ceph_RGW_status_update]] BP, our team is building a Big Data analytics platform on top of Apache Mesos. We have developed a Apache Mesos framework to manage a Ceph cluster with all other Big Data related applications. This framework enables us to deploy Ceph within 10 seconds on a freshly installed 19 node rack since the binaries are launched within a Docker container. We plan to do more testing and share performance test results and usecase scenarios. |
21 | 1 | Zhongyue Luo | |
22 | *Work items* |
||
23 | This blueprint does not require work items on Ceph. |
||
24 | |||
25 | *Coding tasks* |
||
26 | This blueprint does not require coding work on Ceph. |
||
27 | |||
28 | *Build / release tasks* |
||
29 | This blueprint does not require build / release related work on Ceph. |
||
30 | |||
31 | *Documentation tasks* |
||
32 | This blueprint does not require documentation change on Ceph. |
||
33 | |||
34 | *Deprecation tasks* |
||
35 | This blueprint does not require any deprecation on Ceph. |