On Tue, Jan 6, 2009 at 2:13 PM, Digant C Kasundra <dig...@stanford.edu>wrote:
> > > > If you want to do failover with puppet servers and you are using > > environments, there's a major gotcha that I really should add to that > > page... > > > > > > If a puppet client connects to server A, downloads the compiled > > manifest, and then starts requesting files via the puppet:/// > > protocol, and in the middle of all these short lived requests the > > server switches over to Server B, that server doesn't necessarily know > > what environment the client should be using, as that is stored in a > > file on the server. > > > > > > The only feasible solution is to somehow share those state files > > between servers. This may or may not be feasible in your environment > > (no pun intended...) > > How can the state files be shared between servers? The simplest way is probably to just use an NFS share for that location I reckon. I was thinking about other options, but I haven't tested this extensively, so am not sure if there are concurrency issues. -- Nigel Kersten Systems Administrator Tech Lead - MacOps --~--~---------~--~----~------------~-------~--~----~ 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+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~----------~----~----~----~------~----~------~--~---
