+1 on this. Great work guys. Volumes are a good start, but when we have users with large amounts of data, we need an API for storage to work seamlessly at the level within the band of Mesos (Disks or Multiple Disks should be offered as well as volumes). Storage drivers is also an important concept that we have been discussing for some time and is needed by Frameworks like Quobyte, HDFS, Hbase, etc.
-Elizabeth On Mon, Nov 2, 2015 at 11:40 AM, David Greenberg <dsg123456...@gmail.com> wrote: > Sorry for not directly linking! Yes, that is the doc. I'll update the > ticket to include it in the description. > > On Thu, Oct 29, 2015 at 1:00 PM David Greenberg <dsg123456...@gmail.com> > wrote: > > > Hello Everyone, > > At the MesosCon Dublin Hackathon, we started working on MESOS-191. The > > goal of this issue is to enable database and persistent disk frameworks > to > > make use of isolated and high-performance disks, to enable frameworks > like > > HDFS, Cotton, and Kafka to achieve production-level performance. > > > > First, we captured all of the potential applications of the feature > > through user stories. > > Then, we demonstrated the change we'll make to the Mesos API (this is > only > > a protobuf change, no new RPCs are needed). > > Finally, we explicitly point out features that we're not going to include > > in the v1 implementation, but are worthwhile to be added in later > > iterations. > > > > Please look over the document and contribute your feedback. > > > > Thank you! > > David, Jie, Joris, and Michael > > >
