Hi I've been banging my head against this problem and it seems that I cannot find a clean, elegant and working solution.
Scenario: heartbeat v1 (well, actually v2 in compatibility mode) cluster of 2 nodes with a shared disk and a virtual IP. I need to install a service - MySQL - via Puppet that will have it's data on the shared disk. I've found, at least, these problems: 1) on first install, initial mysql data on the passive node will be local only. 2) on next run, Puppet will have no idea of the cluster status, so if I define new mysql users, it will try to apply it on the passive node (where no mysql is running), failing. 3) heartbeat will fail to start if the resource "mysql" is defined, but Mysql should be installed AFTER configuring heartbeat (active host should mount the shared disk). So if while creating the role for the first time I can do things step by step but once finished, if I need to reinstall from scratch, it should work Ok, maybe the first 2 points are not a big deal [1] anyway but I wonder if anyone had found a better solution than just living with errors on the passive node (I have a 0 puppet errors on puppetrun policy), but the third point is a bit harder for me. TIA [1] I thought about a custom facter detecting if it's an active/passivehost or no HB cluster at all, but I'd like some other opinions. -- Davide Ferrari Senior System Administrator Atrapalo S.L. -- 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.
