Permalink
Browse files

I'm not going to be using Fabric

  • Loading branch information...
1 parent da079ce commit e0b016fda98fc95190a602ff2f2d08f2a245f4fe Nikhil Singh committed Dec 7, 2011
Showing with 2 additions and 2 deletions.
  1. +2 −2 README
View
4 README
@@ -11,5 +11,5 @@ Example use cases
How Roadrunner works
=====================
A roadrunner job flow consists of the following parts:
-1. Slot: A slot is a container that holds a set of jobs together. All the jobs in a single slot will run in parallel. For example, consider that case you want to run command X on a set of hosts and a command Y on another set of hosts, and if both these jobs succeed, only then run command Z on another set of hosts. In such a case, we can easily run first two jobs in the same slot (in case they are independent of the outcome of the other job) and then run the third job in another slot.
-2. Jobs: The jobs are nothing but a set of commands that are required to be run on a host or a set of hosts. The jobs in the same slot are run in parallel using Fabric. The output of the jobs are piped to output plugins. Custom plugins can be written by anyone.
+1. Slot: A slot is a container that holds a set of jobs together. All the jobs in a single slot will run in parallel. For example, consider that you want to run command X on a set of hosts and a command Y on another set of hosts, and if both these jobs succeed, only then run command Z on another set of hosts. In such a case, we can easily run first two jobs in the same slot (in case they are independent of the outcome of the other job) and then run the third job in another slot.
+2. Jobs: The jobs are nothing but a set of commands that are required to be run on a host or a set of hosts. The jobs in the same slot are run in parallel. The output of the jobs are piped to output plugins. Custom plugins can be written by anyone.

0 comments on commit e0b016f

Please sign in to comment.