- From: Rob Guttman <
>
- To:
- Subject: [chef] Serial deployment
- Date: Tue, 2 Nov 2010 13:38:17 -0400
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:reply-to:date:message-id:subject:from:to:content-type; b=fSZe3hobQVYPjKqzy1dNI2tTKdjPgGPqA75ouVaDgXHrRiasMnIkb6JS7lYf5BKsqd J6wyO7fZXiLp6lwBQTE4wdX6GD1diFE0kYReIUHdCNDb1Cvsq+rQf47gWdq5qfAK/w2N tt2obd6wf7y8prdth0EtCySXOuY90Nr8jl4F4=
We're just starting to use chef for managing nagios configs - so far, so good.
What
we would like to eventually use it for is to deploy all of our web apps
and services. A specific use case we have is to be able to *serially*
deploy to hosts/instances within a cluster behind a load balancer. For
example, we would take one host out of rotation, deploy to it, warm it
up and/or smoke test, and when warming completes and/or if smoke tests
pass then put it back into rotation and move on to the next host in the
cluster.
How best to achieve that?
Thanks.
- Rob
- [chef] Serial deployment, Rob Guttman, 11/02/2010
Archive powered by MHonArc 2.6.16.