Hi Guangya, Thanks for your reply. That is nice feature to group the slaves into different racks and etc...But is there any way I can get metric of other hardware features other than CPU,MEM, DISK like IO, PCI devices that exists with the node etc?
Thanks, Pradeep On 5 October 2015 at 17:45, Guangya Liu <gyliu...@gmail.com> wrote: > Hi Pradeep, > > I think that you can try Chronos and Marathon which can help you. > > *Marathon:* https://github.com/mesosphere/marathon > You can try Marathon + Mesos + Mesos Resource Attribute > > When you start up mesos slave, uses --attributes option, here is an > example: > ./bin/mesos-slave.sh --master=9.21.61.21:5050 --quiet > --log_dir=/tmp/mesos --attributes=rackid:r1;groupid:g1 > This basically defines two attributes for this mesos slave host. rackid > with value r1 and groupid with value g1. > > marathon start -i "like_test" -C "sleep 1000000" -n 4 -c 1 -m 50 -o > "rackid:LIKE:r1" > > this will place applications on the slave node whose rackid is r1 > > *Chronos:* https://github.com/mesos/chronos , Chronos supports the > definition of jobs triggered by the completion of other jobs. It supports > arbitrarily long dependency chains. > > Thanks, > > Guangya > > On Mon, Oct 5, 2015 at 11:21 PM, Pradeep Kiruvale < > pradeepkiruv...@gmail.com> wrote: > >> Hi All, >> >> Are there any frameworks that exists with the Mesos to schedule the >> bigger apps? >> I mean to say scheduling a app which has many services and will not fit >> into one physical node. >> >> Is there any frame work that can be used to >> schedule tasks based on the underlying hardware constraints like Network >> bandwidth ? >> > Schedule the tasks based on their dependencies and proximity to each >> other in a cluster or a rack? >> >> Thanks & Regards, >> Pradeep >> > >
