airavata-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apoorv Palkar <apoorv_pal...@aol.com>
Subject Re: [GSoC] Distributed Workload Management.
Date Mon, 27 Mar 2017 17:17:52 GMT
https://github.com/airavata-courses/spring17-workload-management/wiki/%5BFinal%5D-Centralized-architecture-for-workload-management


The above is the link to the data. I was told during HackIllinois by Gourav that the workers
should pull from the queue rather than the scheduler pushing to the workers. I worked on implementing
the Serf and gossip protocol, but I ran out of time. This is something I'm looking to do as
part of my GSoC project.



-----Original Message-----
From: Shameera Rathnayaka <shameerainfo@gmail.com>
To: dev <dev@airavata.apache.org>
Sent: Sun, Mar 26, 2017 10:18 pm
Subject: Re: [GSoC] Distributed Workload Management.



Hi Apoorv, 


Why do you want to remove all RabbitMQ implementation and replaced it with gossip protocol?

Where did you find the article you mentioned above? (any web link?)


Regards, 
Shameera.


On Sat, Mar 25, 2017 at 4:21 PM Apoorv Palkar <apoorv_palkar@aol.com> wrote:

I am creating a GSoC proposal for the distributed workload management part of Airavata. I
read the article titled "A Centralized, Apache Mesos Inspired Architecture". I was wondering
if anybody had actually coded the idea proposed in the article? It seems very interesting.
In addition to this, I wanted to remove all of the RabbitMQ implementation and replace it
with the gossip protocol via Serf.


Thanks,
Apoorv Palkar

-- 


Shameera Rathnayaka



Mime
View raw message