Upgrading cookbooks/resources


#1

Hi all,

Me again! So, I’m at the stage where I’m about ready to be writing some
resources/cookbooks/whatever for various different packages of mine under
Chef, but I can’t seem to find any information about how one would go about
say, deploying a latest version of one’s code to all of the nodes.

Obviously, this is something I would think just about every user out there
would have a need for, so I’m fairly sure I’m missing something (again).
What is the general procedure for this? Clearly this is probably something
that would have to be synchronised across all the nodes, but with how the
clients are configured to run, I don’t see how this is possible?

—Oliver


#2

Oliver, is what you mean, that you have (say) x web-application nodes, (and
maybe other deployable nodes too)… and that the code for all of these
needs to be deployed/updated at the same time?

If so, I’m also interested in hearing the best practice here (am getting
around this by either running chef-client imperatively (using knife ssh
chef-client) when I want to deploy – and by having systems so unintensive
(one or two node systems, where the single webapp node runs migrations on
the single db node when deployed) that this isn’t an issue).

Tim

On Wed, Jul 20, 2011 at 10:14 AM, Oliver Beattie oliver@luckyvoice.comwrote:

Hi all,

Me again! So, I’m at the stage where I’m about ready to be writing some
resources/cookbooks/whatever for various different packages of mine under
Chef, but I can’t seem to find any information about how one would go about
say, deploying a latest version of one’s code to all of the nodes.

Obviously, this is something I would think just about every user out there
would have a need for, so I’m fairly sure I’m missing something (again).
What is the general procedure for this? Clearly this is probably something
that would have to be synchronised across all the nodes, but with how the
clients are configured to run, I don’t see how this is possible?

—Oliver