Diff for "Foundations/NewTaskSystem/Technologies"

Not logged in - Log In / Register

Differences between revisions 1 and 2
Revision 1 as of 2010-08-27 14:28:16
Size: 733
Editor: abentley
Comment:
Revision 2 as of 2010-08-27 14:31:22
Size: 888
Editor: abentley
Comment:
Deletions are marked like this. Additions are marked like this.
Line 26: Line 26:
However, it could allow us to take advantage of our internal UEC cloud, and might make it feasible for individuals to run their own buildfarms as a test.

Candidate technologies

Some technologies to consider for the new task system

Job system + RabbitMQ

Extend the current job system to be a daemon that listens to RabbitMQ for notification of pending jobs.

Job system + ampoule

Extend the current job system to be a daemon that listens for AmpQ messages for notification of pending jobs.

Celery

http://celeryproject.org/

Gearman

http://gearman.org/

Beanstalk

http://kr.github.com/beanstalkd/

Kestrel

http://wiki.github.com/robey/kestrel/

UEC

We could use UEC to manage our worker machines, but this does not support non-virtualizable architectures. However, it could allow us to take advantage of our internal UEC cloud, and might make it feasible for individuals to run their own buildfarms as a test.

Landscape

We could use Landscape to manage our worker machines.

Foundations/NewTaskSystem/Technologies (last edited 2010-08-27 14:31:22 by abentley)