Re: Metascheduler work

Hi Dimuthu, > On Dec 17, 2018, at 9:55 AM, DImuthu Upeksha > wrote: > > Metascheduling Usecase 3: Users within a gateway need to fairly use a > community account. Computational resources like XSEDE enforce fair-share > across users, but since gateway job submissions are funneled through a

Re: Metascheduler work

The solution I provided was to run MPI tasks with Mesos was with the help of Docker Swarm. It required me to develop a Mesos Framework and an Executor [here ]. Mesos containers could not communicate with each other and

Re: Metascheduler work

I thought Pankaj presented a way to implement MPI executions through mesos more recently. He may want to comment on this.. Thanks, Sudakar. From: Marlon Pierce Reply-To: Date: Monday, December 17, 2018 at 8:52 AM To: "dev@airavata.apache.org" Subject: Re: Metascheduler work Hi Dimuthu,

Re: Metascheduler work

Hi Marlon, Thanks for the clarification. Yes I agree that we need to re-evaluate both the use case and the approach we are going to implement this. Hi All, Considering current requirements of gateways, we somehow need a better job throttling/ scheduling proxy before the actual schedulers. I

Re: Metascheduler work

Hi Dimuthu, This is something we should re-evaluate. Mangirish Wangle looked at Mesos integration with Airavata back in 2016, but he ultimately ran into many difficulties, including getting MPI jobs to work, if I recall correctly. Marlon From: "dimuthu.upeks...@gmail.com"

Re: Unused modules

Hi Dimuthu, Yes, it's loaded at runtime. See the db_event_manager property in airavata-server.properties. See also [1]. Thanks, Marcus [1]