- From: Alex Soto <
>
- To: "
" <
>
- Cc: "
" <
>
- Subject: [chef] Re: Re: Re: Re: Gradual deployments
- Date: Tue, 19 Oct 2010 16:07:41 -0700
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=references:in-reply-to:mime-version:content-transfer-encoding :content-type:message-id:cc:x-mailer:from:subject:date:to; b=wqZl9aDiA1ALzm7/hR8ohGOFmDq4SOd/Gi9P7mgMYG0cRPxn5DAYhxHYrgHokMHcoo AZ9lPgoiZ6ACymRKfk6CLxyfUjUp0coepjbHpoV6ciiQGz9SJBTibq6KNLG+4BW3z1XC kJtX6EdoQbi/VQLeXW8MxOR+CmM7bsdCQ/sRc=
No I don't. Each environment has it's own nodes.
A side effect I kind of like is the node list is less cluttered with nodes that don't gave anything to do with each others environments.
Sent from my phone
On Oct 19, 2010, at 2:24 PM, Brian Akins <
">
> wrote: On Tue, Oct 19, 2010 at 3:20 PM, Alex Soto <
">
">
> wrote:
In the mean time, I use multiple opscode platforms which is equivalent to multiple chef-servers for each 'environment'. I use a single cookbook git repo with qa/staging/production branches and promote cookbooks through the branches.
Do you swing nodes between platforms?
|
Archive powered by MHonArc 2.6.16.