On Saturday, March 7, 2015 at 6:53:23 AM UTC+13, Felix.Frank wrote: > > On 03/06/2015 06:50 PM, lupin...@gmail.com <javascript:> wrote: > > hi, > > > > thank you for the reply, however the end state really is to have both > machine in sync and working as pair of primary/standby Database log > shipping. > > > > The flow therefore are: > > 1) create backup in serverA > > 2) copy to serverB > > 3) restore copy serverB > > 4) start replication mode serverB > > 5) start replication serverA > > > > the crucial point of ordering dependency is between 4 & 5, I've done an > exported file resource on serverB to serve as flag for serverA to start but > it fails to complie the catalog since that dependency is not in the catalog > yet. > > Hi, > > I'm with Garrett - Puppet is an awkward fit for this task. > > Have you considered a classic publish/subscribe queue such as RabbitMQ > or Gearman? Puppet can set those up for you, and your nodes can then > orchestrate themselves in a more natural fashion. > > HTH, > Felix >
Hello Frank, Garret, Thanks for the insightful advises, especially the message queue stuff but seems an overkill for my requirement. I ended up using the "exported" resource and wait for apparent convergence after multiple Puppet run. Cheers Lupin -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/50d69f65-14a7-462a-b5dd-9faf0f2ed4e8%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
