Re: [Fab-user] deploy to loadbalancer and application server

[Eric Buckley]

Thanks for getting back to me, to be more specific I'd like to create a task called 'deploy' which is responsible for invoking a series of other methods (e.g. pull(), checkout(), requirements(), restart(), etc.).  Most of these sub methods will need to run on a set of application servers, right now I'm setting env.roles to "application" and these methods are working properly.  However there are 2 sub methods that can't run on the application servers and instead need to execute on a set of loadbalancer servers.  I tried adding the @roles('loadbalancer') decorator to these 2 sub methods, but no luck, the methods still get executed on the application servers.  Any ideas?

Thanks,

Eric

On Wed, Sep 15, 2010 at 10:11, Jeff Forcier <address@hidden> wrote:

Can you be more specific? You can easily deploy to more than one
system with Fabric; however, right now there is no parallel
deployment, meaning tasks are run in serial. There are unreleased
branches of Fabric which can deploy in parallel, and they will become
Fabric 1.0 in the not-too-distant future, but they're currently
unstable.

If that doesn't frighten you, then I'm sure myself and the other
developers on those branches would welcome the additional real-world
testing. Otherwise, if your setup can tolerate rolling deployments,
you may find the stable releases more solid.

Best,
Jeff

On Tue, Sep 14, 2010 at 10:45 AM, Eric Buckley <address@hidden> wrote:
> Is it possible to write a deployment task(s) that deploys to both a set of
> loadbalancers and a set of application servers?
> Thanks,
> Eric

> _______________________________________________
> Fab-user mailing list
> address@hidden
> http://lists.nongnu.org/mailman/listinfo/fab-user
>
>



--
Jeff Forcier
Unix sysadmin; Python/Ruby developer
http://bitprophet.org