Michael DeHaan <[email protected]> writes:
> On Wed, Apr 7, 2010 at 6:58 PM, Bruce Richardson <[email protected]> wrote:
>> On Mon, Apr 05, 2010 at 04:54:30PM +1000, Daniel Pittman wrote:
>>> >>> thank you so much for the reply. i have bunch of webserver, i want to 
>>> >>> able
>>> >>> be able run svn update to all the webserver from master.
>
>>> this is not what puppet specializes in.  you can probably do it, but you
>>> will almost certainly find it more productive to use some alternate tool
>>> to implement this feature.

[... VCS repository module ...]

> If you can share other reasons why this doesn't work for you

Most of my reasons are in my response to Bruce, so I will not repeat them
here.  However, to be clear: my issue is not that running 'svn update' or
whatever is hard in puppet.

It is that all the *other* parts of updating a software deployment are hard,
and most people don't have the luxury of using that one action, alone, to
achieve it.

Out of interest: how do you handle database schema updates and synchronisation
between multiple web servers in a load-balanced pool in your deployment
through puppet model?

[...]

> I don't see it desirable to manage the OS seperately from app deployments --
> that's an incomplete model -- and our current limitation in this area is in
> modelling interactions /between/ servers.

*nod*

> In the case of doing a simple SVN checkout, not a problem.  And for the idea
> of gating conditions on external resources, we're making strides in that
> direction.

...that, I look forward to the bigger picture — but my money was on the OP
solving the 'svn update' part of his deployment problem, then asking about the
next part of his deployment strategy. :)


So, yeah, I look forward to better tools in puppet for managing this, but
I really don't think it is there today ... and I don't know if it will get
there, either, since there *are* different demands.  I would like it to,
though.

        Daniel

FWIW, aside from modelling interactions between servers, my other major pain
from puppet comes from modelling systems that have multiple, independent
components that form part of another component; the plethora of "concatenated
file" modules are evidence of that. :)

-- 
✣ Daniel Pittman            ✉ [email protected]            ☎ +61 401 155 707
               ♽ made with 100 percent post-consumer electrons

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

Reply via email to