On 03/06/2015 06:50 PM, [email protected] 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 -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/54F9E97C.6030207%40alumni.tu-berlin.de. For more options, visit https://groups.google.com/d/optout.
