Re: [Fab-user] How important is making fabric parallel to everyone else?

[Xinan Wu]

I am interested, and my usage case is actually a little bit more
complicated: We have many machines in a production cluster. We don't
want to deploy all in parallel, but it's also very inefficient to do
it completely in series. So we deploy four at a time (pull out from
load balancer, wait a minute, deploy, restart, put back in load
balancer). After all this is done, we send a notification email. This
whole sequence is too fancy to implement with fabric but we managed to
write everything in fabfile with fabric 0.1.1 (basically fab call
os.system to start fab subprocess by threads and then join()
afterwards.) However I found it'd be very difficult (if not
impossible) to implement it with the new fabric 0.9 unless I change
fabric code or use a separate wrapper python script.

I think people are talking about adding parallel execution in fabric
but it's not very straightforward.

On Fri, Jul 17, 2009 at 11:43 AM, Matthew Wilson<address@hidden> wrote:
> I was surprised when I saw how fabric iterated through all the hosts
> in sequence rather than in parallel.  For more than a few boxes and
> for a fairly long set of tasks, my upgrades are going to take a long
> time.
>
> Am I alone here?
>
> I've got some vague ideas about how to use subprocess or
> multiprocessing to add parallel work to fabric.  Anyone already
> working on this?  Maybe we could get some of this part figured out
> ahead of time.
>
> Matt
>
> --
> Matthew Wilson
> address@hidden
> http://tplus1.com
>
>
> _______________________________________________
> Fab-user mailing list
> address@hidden
> http://lists.nongnu.org/mailman/listinfo/fab-user
>