Ceph-mesos » History » Revision 2
Revision 1 (Zhongyue Luo, 06/12/2015 03:30 AM) → Revision 2/5 (Zhongyue Luo, 06/13/2015 01:22 AM)
h3. +*Ceph on Apache Mesos*+ OpenStack Murano*+ *Summary* The ceph-mesos project is Please provide a Apache Mesos framework for scaling a Ceph cluster. The framework scheduler decides which Ceph binaries brief description of this blueprint. For convenience, try to execute write something short and the framework executors launch Ceph Docker containers on Mesos slaves accordingly. easy to understand. *Owners* Zhongyue Nah (Intel) Zhankun Tang (Intel) Zhidong Yu (Intel) *Interested Parties* *Current Status* The ceph-mesos project is external to Please describe the current status of Ceph project. Currently as it is under testing and will soon release it's initial version. relates to this blueprint. Is there something that this replaces? Are there current features that are related? *Detailed Description* Big Data analytics This 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 big one! Please provide a high level interface detailed description for managing applications running in a datacenter that adding new applications hardly increases management entropy. In conjunction with the [[Hadoop_over_Ceph_RGW_status_update]] BP, our team is building proposed change. Where appropriate, include your architectural approach, a Big Data analytics platform on top list 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 19 node rack since the binaries systems involved, important consequences, and issues that are launch within a Docker container. We plan to do more testing and share performance test results and usecase scenarios. still unresolved. *Work items* This blueprint does not require work items on Ceph. *Coding tasks* This blueprint does not require coding work on Ceph. *Build / release tasks* This blueprint does not require build / release related work on Ceph. *Documentation tasks* This blueprint does not require documentation change on Ceph. *Deprecation tasks* This blueprint does not require any deprecation on Ceph.