I am trying push configuratioin from the server. Here is the simple
config
node ''client.master.com'' {
package { ''curl'': ensure => present
}
}
-bash-3.2#puppet site.pp
dnsdomainname: Unknown host
Could not find default node or by name with ''domu-12-31-39-09-a4-
c4.com, domu-12-31-39-09-a4-c4, domU-12-31-39-09-A4-C4.com,
domU-12-31-39-09-A4-C4'' on node domu-12-31-39-09-a4-c4.com
ping client.master.com
PING client.master.com (10.193.125.130) 56(84) bytes of data
64 bytes from client.master.com (10.193.125.130): icmp_seq=1 ttl=61
time=0.739 ms
I can pull config from client but not able to push it from server, I
get this weird DNS error. Please help
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
On Apr 4, 2010, at 7:00 PM, JT wrote:> I am trying push configuratioin from the server. Here is the simple > config > > node ''client.master.com'' { > package { ''curl'': ensure => present > } > } > > -bash-3.2#puppet site.pp > dnsdomainname: Unknown host > Could not find default node or by name with ''domu-12-31-39-09-a4- > c4.com, domu-12-31-39-09-a4-c4, domU-12-31-39-09-A4-C4.com, > domU-12-31-39-09-A4-C4'' on node domu-12-31-39-09-a4-c4.com > ping client.master.com > PING client.master.com (10.193.125.130) 56(84) bytes of data > 64 bytes from client.master.com (10.193.125.130): icmp_seq=1 ttl=61 > time=0.739 ms > > I can pull config from client but not able to push it from server, I > get this weird DNS error. Please help >I can''t quite figure out what you are doing. First, I''m not sure if there''s a misunderstanding about terminology, or something more fundamental. Puppet in the default configuration is based on a standard client to server model. The server doesn''t push information. Instead the client pulls information. Sorry if I''m repeating what you already know. (This is mostly true. There is a command-line option that allows you to push configuration, but that probably isn''t what you want right now.) Now that I have that out of the way I''ll continue. In this case, the client thinks that the client''s name is domU-12-31-39-09-A4-C4.com. The manifest only lists a client called client.master.com. There are three direct solutions: *) Change something to the client thinks its name is client.master.com. *) Change the manifest so it lists a configuration for *) Add a configuration for ''default'' to the manifest. I won''t have a very good idea of which is best until I get more information about what you are doing. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
jatindergiri@gmail.com
2010-Apr-05 04:53 UTC
Re: [Puppet Users] How to push config from master ?
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. Of-course I can do cron job that runs svn update, but I would like to revert to previous version on fly if needed. So maybe I need to use that tool you are talking about ? Sent via BlackBerry by AT&T -----Original Message----- From: Patrick <kc7zzv@gmail.com> Date: Sun, 4 Apr 2010 21:43:45 To: <puppet-users@googlegroups.com> Subject: Re: [Puppet Users] How to push config from master ? On Apr 4, 2010, at 7:00 PM, JT wrote:> I am trying push configuratioin from the server. Here is the simple > config > > node ''client.master.com'' { > package { ''curl'': ensure => present > } > } > > -bash-3.2#puppet site.pp > dnsdomainname: Unknown host > Could not find default node or by name with ''domu-12-31-39-09-a4- > c4.com, domu-12-31-39-09-a4-c4, domU-12-31-39-09-A4-C4.com, > domU-12-31-39-09-A4-C4'' on node domu-12-31-39-09-a4-c4.com > ping client.master.com > PING client.master.com (10.193.125.130) 56(84) bytes of data > 64 bytes from client.master.com (10.193.125.130): icmp_seq=1 ttl=61 > time=0.739 ms > > I can pull config from client but not able to push it from server, I > get this weird DNS error. Please help >I can''t quite figure out what you are doing. First, I''m not sure if there''s a misunderstanding about terminology, or something more fundamental. Puppet in the default configuration is based on a standard client to server model. The server doesn''t push information. Instead the client pulls information. Sorry if I''m repeating what you already know. (This is mostly true. There is a command-line option that allows you to push configuration, but that probably isn''t what you want right now.) Now that I have that out of the way I''ll continue. In this case, the client thinks that the client''s name is domU-12-31-39-09-A4-C4.com. The manifest only lists a client called client.master.com. There are three direct solutions: *) Change something to the client thinks its name is client.master.com. *) Change the manifest so it lists a configuration for *) Add a configuration for ''default'' to the manifest. I won''t have a very good idea of which is best until I get more information about what you are doing. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
On Apr 4, 2010, at 9:53 PM, jatindergiri@gmail.com 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. Of-course I can do cron job that runs svn update, but I would like to revert to previous version on fly if needed. So maybe I need to use that tool you are talking about ? >How many is "a bunch"? 5, 30, 100, 1000?> > -----Original Message----- > From: Patrick <kc7zzv@gmail.com> > Date: Sun, 4 Apr 2010 21:43:45 > To: <puppet-users@googlegroups.com> > Subject: Re: [Puppet Users] How to push config from master ? > > > On Apr 4, 2010, at 7:00 PM, JT wrote: > >> I am trying push configuratioin from the server. Here is the simple >> config >> >> node ''client.master.com'' { >> package { ''curl'': ensure => present >> } >> } >> >> -bash-3.2#puppet site.pp >> dnsdomainname: Unknown host >> Could not find default node or by name with ''domu-12-31-39-09-a4- >> c4.com, domu-12-31-39-09-a4-c4, domU-12-31-39-09-A4-C4.com, >> domU-12-31-39-09-A4-C4'' on node domu-12-31-39-09-a4-c4.com >> ping client.master.com >> PING client.master.com (10.193.125.130) 56(84) bytes of data >> 64 bytes from client.master.com (10.193.125.130): icmp_seq=1 ttl=61 >> time=0.739 ms >> >> I can pull config from client but not able to push it from server, I >> get this weird DNS error. Please help >> > > I can''t quite figure out what you are doing. > > First, I''m not sure if there''s a misunderstanding about terminology, or something more fundamental. Puppet in the default configuration is based on a standard client to server model. The server doesn''t push information. Instead the client pulls information. Sorry if I''m repeating what you already know. (This is mostly true. There is a command-line option that allows you to push configuration, but that probably isn''t what you want right now.) > > Now that I have that out of the way I''ll continue. In this case, the client thinks that the client''s name is domU-12-31-39-09-A4-C4.com. The manifest only lists a client called client.master.com. There are three direct solutions: > *) Change something to the client thinks its name is client.master.com. > *) Change the manifest so it lists a configuration for > *) Add a configuration for ''default'' to the manifest. > > I won''t have a very good idea of which is best until I get more information about what you are doing. > > -- > You received this message because you are subscribed to the Google Groups "Puppet Users" group. > To post to this group, send email to puppet-users@googlegroups.com. > To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. > For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en. > > -- > You received this message because you are subscribed to the Google Groups "Puppet Users" group. > To post to this group, send email to puppet-users@googlegroups.com. > To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. > For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en. >-- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
jatindergiri@gmail.com
2010-Apr-05 05:23 UTC
Re: [Puppet Users] How to push config from master ?
Around 70 Sent via BlackBerry by AT&T -----Original Message----- From: Patrick <kc7zzv@gmail.com> Date: Sun, 4 Apr 2010 22:22:10 To: <puppet-users@googlegroups.com> Subject: Re: [Puppet Users] How to push config from master ? On Apr 4, 2010, at 9:53 PM, jatindergiri@gmail.com 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. Of-course I can do cron job that runs svn update, but I would like to revert to previous version on fly if needed. So maybe I need to use that tool you are talking about ? >How many is "a bunch"? 5, 30, 100, 1000?> > -----Original Message----- > From: Patrick <kc7zzv@gmail.com> > Date: Sun, 4 Apr 2010 21:43:45 > To: <puppet-users@googlegroups.com> > Subject: Re: [Puppet Users] How to push config from master ? > > > On Apr 4, 2010, at 7:00 PM, JT wrote: > >> I am trying push configuratioin from the server. Here is the simple >> config >> >> node ''client.master.com'' { >> package { ''curl'': ensure => present >> } >> } >> >> -bash-3.2#puppet site.pp >> dnsdomainname: Unknown host >> Could not find default node or by name with ''domu-12-31-39-09-a4- >> c4.com, domu-12-31-39-09-a4-c4, domU-12-31-39-09-A4-C4.com, >> domU-12-31-39-09-A4-C4'' on node domu-12-31-39-09-a4-c4.com >> ping client.master.com >> PING client.master.com (10.193.125.130) 56(84) bytes of data >> 64 bytes from client.master.com (10.193.125.130): icmp_seq=1 ttl=61 >> time=0.739 ms >> >> I can pull config from client but not able to push it from server, I >> get this weird DNS error. Please help >> > > I can''t quite figure out what you are doing. > > First, I''m not sure if there''s a misunderstanding about terminology, or something more fundamental. Puppet in the default configuration is based on a standard client to server model. The server doesn''t push information. Instead the client pulls information. Sorry if I''m repeating what you already know. (This is mostly true. There is a command-line option that allows you to push configuration, but that probably isn''t what you want right now.) > > Now that I have that out of the way I''ll continue. In this case, the client thinks that the client''s name is domU-12-31-39-09-A4-C4.com. The manifest only lists a client called client.master.com. There are three direct solutions: > *) Change something to the client thinks its name is client.master.com. > *) Change the manifest so it lists a configuration for > *) Add a configuration for ''default'' to the manifest. > > I won''t have a very good idea of which is best until I get more information about what you are doing. > > -- > You received this message because you are subscribed to the Google Groups "Puppet Users" group. > To post to this group, send email to puppet-users@googlegroups.com. > To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. > For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en. > > -- > You received this message because you are subscribed to the Google Groups "Puppet Users" group. > To post to this group, send email to puppet-users@googlegroups.com. > To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. > For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en. >-- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
I''ve heard you can push config using puppet, but I''ve never tried it. If you''re interested, take a look at the command puppetrun and "puppetd --listen". When I need to do something now on all the nodes, I use a distributed ssh program. I setup the ssh server using puppet on each client. (Client means puppet client. In this case, all clients are running a webserver.) RJust a quick reminder, if all your clients update at once instead of one at a time, make sure that the server that you use (puppet and/or svn) can handle the load of being hit by all 70 at once. If it can''t, make sure they connect sequentially. On Apr 4, 2010, at 10:23 PM, jatindergiri@gmail.com wrote:> Around 70 > Sent via BlackBerry by AT&T > > -----Original Message----- > From: Patrick <kc7zzv@gmail.com> > Date: Sun, 4 Apr 2010 22:22:10 > To: <puppet-users@googlegroups.com> > Subject: Re: [Puppet Users] How to push config from master ? > > > On Apr 4, 2010, at 9:53 PM, jatindergiri@gmail.com 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. Of-course I can do cron job that runs svn update, but I would like to revert to previous version on fly if needed. So maybe I need to use that tool you are talking about ? >> > > How many is "a bunch"? 5, 30, 100, 1000? > >> >> -----Original Message----- >> From: Patrick <kc7zzv@gmail.com> >> Date: Sun, 4 Apr 2010 21:43:45 >> To: <puppet-users@googlegroups.com> >> Subject: Re: [Puppet Users] How to push config from master ? >> >> >> On Apr 4, 2010, at 7:00 PM, JT wrote: >> >>> I am trying push configuratioin from the server. Here is the simple >>> config >>> >>> node ''client.master.com'' { >>> package { ''curl'': ensure => present >>> } >>> } >>> >>> -bash-3.2#puppet site.pp >>> dnsdomainname: Unknown host >>> Could not find default node or by name with ''domu-12-31-39-09-a4- >>> c4.com, domu-12-31-39-09-a4-c4, domU-12-31-39-09-A4-C4.com, >>> domU-12-31-39-09-A4-C4'' on node domu-12-31-39-09-a4-c4.com >>> ping client.master.com >>> PING client.master.com (10.193.125.130) 56(84) bytes of data >>> 64 bytes from client.master.com (10.193.125.130): icmp_seq=1 ttl=61 >>> time=0.739 ms >>> >>> I can pull config from client but not able to push it from server, I >>> get this weird DNS error. Please help >>> >> >> I can''t quite figure out what you are doing. >> >> First, I''m not sure if there''s a misunderstanding about terminology, or something more fundamental. Puppet in the default configuration is based on a standard client to server model. The server doesn''t push information. Instead the client pulls information. Sorry if I''m repeating what you already know. (This is mostly true. There is a command-line option that allows you to push configuration, but that probably isn''t what you want right now.) >> >> Now that I have that out of the way I''ll continue. In this case, the client thinks that the client''s name is domU-12-31-39-09-A4-C4.com. The manifest only lists a client called client.master.com. There are three direct solutions: >> *) Change something to the client thinks its name is client.master.com. >> *) Change the manifest so it lists a configuration for >> *) Add a configuration for ''default'' to the manifest. >> >> I won''t have a very good idea of which is best until I get more information about what you are doing. >> >> -- >> You received this message because you are subscribed to the Google Groups "Puppet Users" group. >> To post to this group, send email to puppet-users@googlegroups.com. >> To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. >> For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en. >> >> -- >> You received this message because you are subscribed to the Google Groups "Puppet Users" group. >> To post to this group, send email to puppet-users@googlegroups.com. >> To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. >> For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en. >> > > -- > You received this message because you are subscribed to the Google Groups "Puppet Users" group. > To post to this group, send email to puppet-users@googlegroups.com. > To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. > For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en. > > -- > You received this message because you are subscribed to the Google Groups "Puppet Users" group. > To post to this group, send email to puppet-users@googlegroups.com. > To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. > For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en. >-- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Patrick <kc7zzv@gmail.com> writes:> I''ve heard you can push config using puppet, but I''ve never tried it. > If you''re interested, take a look at the command puppetrun and "puppetd > --listen".FWIW, this isn''t pushing configuration. The puppetrun invocation sends a message to puppetd on the client, which then pulls configuration from the central server and acts on it. So, it triggers the client pull on demand, but the client still pulls. [...]> on apr 4, 2010, at 10:23 pm, jatindergiri@gmail.com wrote: >> -----original message----- >> from: patrick <kc7zzv@gmail.com> >> subject: re: [puppet users] how to push config from master ? >> >> on apr 4, 2010, at 9:53 pm, jatindergiri@gmail.com 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.>>> of-course i can do cron job that runs svn update, but i would like to >>> revert to previous version on fly if needed.i am not quite sure how you envision puppet helping with that, but one approach that doesn''t require another tool is: get the puppetrun facility working, or use some other mechanism, so you can trigger client runs on demand. use puppet to run the svn update process, then ensure that a symlink points to the correct (typically, latest) release of your software. puppet can additionally take other actions if it changes that symlink. then, to update you need to ensure that the new version is available in svn at a new top level path, update the puppet configuration to that version, and the rest happens by magic. More or less. Daniel -- ✣ Daniel Pittman ✉ daniel@rimspace.net ☎ +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 puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Bruce Richardson
2010-Apr-07 22:58 UTC
Re: [Puppet Users] How to push config from master ?
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.I don''t understand why so many puppet people say this. Cfengine users do this kind of thing all the time (it''s one of the very few things that is possibly slightly easier in Cfengine and is perfectly secure; you can''t run arbitrary commands remotely via cfengine any more than you can with puppet). Cfengine does this by allowing you to define arbitary "classes" (which in cfengine means named conditions which are either defined/active or undefined/inactive) when you trigger a run of cfengine either locally or remotely. It''s perfectly secure because all you can do is trigger whatever actions are associated with that "class" in the client''s config file. The worst you can do is DOS the client machine by repeatedly triggering cfengine (and there are ways to protect against that). Seems to me that the same thing can be achieved with puppetrun and tags (or custom facts or some method you roll for yourself of communicating arbitrary conditions to puppet). What am I missing? -- Bruce I must admit that the existence of Disneyland (which I know is real) proves that we are not living in Judea in AD 50. -- Philip K. Dick -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
On Wed, Apr 7, 2010 at 6:58 PM, Bruce Richardson <itsbruce@workshy.org> 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.I disagree. There''s nothing wrong with doing this with Puppet, and we see this to be a very good way to deploy, for example, hosted apps and things that are traditionally hard to package. For instance, you can do a checkout at a specific git revision (I''m not positive the SVN module does this yet... but it should). Take a look at http://github.com/bruce/puppet-vcsrepo for a nice example of how to do this. If you can share other reasons why this doesn''t work for you, or have additional ideas for improvements, let everyone know, and we can make it better. 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. 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. http://github.com/reductivelabs/puppet-external-resource --Michael -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Bruce Richardson <itsbruce@workshy.org> writes:> 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. > > I don''t understand why so many puppet people say this.FWIW, I wouldn''t claim to be anything but an end user of puppet, really.> Cfengine users do this kind of thing all the time (it''s one of the very few > things that is possibly slightly easier in Cfengine and is perfectly secure; > you can''t run arbitrary commands remotely via cfengine any more than you can > with puppet). > > Cfengine does this by allowing you to define arbitary "classes" (which > in cfengine means named conditions which are either defined/active or > undefined/inactive) when you trigger a run of cfengine either locally or > remotely.*nod* This is all equally true of puppet. [...]> Seems to me that the same thing can be achieved with puppetrun and tags > (or custom facts or some method you roll for yourself of communicating > arbitrary conditions to puppet). What am I missing?...that deploying software to more than one machine is *significantly* more complicated than just "run svn update" on them. For example, I bet that the OP really doesn''t want to react to an SVN update failing by just trying again, but wants to pull that machine out of the active pool until the problem is fixed. That is harder to script in puppet, and as far as I can see requires that you write your own wrapper around the process. It is also hard to synchronise actions across machines with puppet[1]: it is much harder to have puppet robustly update all the machines, and then if, and only if, every single machine updated successfully, restart the application server to load those new changes.[2] It is even worse when you want to synchronise "do A many times, do B once, do C many times" across machines; the classic example is that A and C are software updates, and B a database schema update, and that if you don''t get the sequence right you get an outage. On the other hand, these are tasks that specialised tools exist for, and which mean you don''t have to write "svn update and check for errors", but just lean on the existing tool that has built-in support for that. So, puppet can do it. It just doesn''t provide (right now) all that many tools to make this *easy* for you. Does that clarify why I believe what I said? Daniel Footnotes: [1] ...and, boy, I really wish it was easier because it would make my life much better when dealing with complex software roll-outs. [2] ...or update the "current" symlink from the old version to the new version, or whatever mechanism you use to change the running version. -- ✣ Daniel Pittman ✉ daniel@rimspace.net ☎ +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 puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Michael DeHaan <michael@puppetlabs.com> writes:> On Wed, Apr 7, 2010 at 6:58 PM, Bruce Richardson <itsbruce@workshy.org> 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 youMost 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 ✉ daniel@rimspace.net ☎ +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 puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.