- From: James Sulinski <
>
- To:
- Cc:
- Subject: [chef] Re: Serial deployment
- Date: Wed, 3 Nov 2010 17:56:47 -0400
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:from:date :x-google-sender-auth:message-id:subject:to:cc:content-type; b=SXNfNzCShoVokIsm3oHrRWJo0DQhNOnzfItD4UsOTPtxGCj4oz6q7S4c3RT/C9dXXK wnttcCh4/Uzwp7FWsXVIFkmdszt/NNRHs238dYIAZxBBMhhaGp7WpuzSePDt1YNMjsrC 35J7plTAU5FzOoscU3S11o0PHzJBRIfjhqnEY=
Rob,
I know this isn't exactly what you're looking for, but figured I'd toss it out there:
It's possible to do something like this using Unicorn and nginx, without removing hosts from the proxy/load balancer. This assumes that you do "smoke testing" in a staging environment prior to deploying to production. The removal/warm up/addition process is no longer necessary: unicorn is capable of rolling restarts, and nginx can skip hosts which aren't ready using the proxy_next_upstream param.
James
On Tue, Nov 2, 2010 at 1:38 PM, Rob Guttman
<
">
> wrote:
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
Archive powered by MHonArc 2.6.16.