On 3/17/2010 8:41 PM, Luke Kanies wrote:
If you have two services, where one service specifies that it being in a 'running' state requires that the other service must also be in a 'running' state, when you got to restart the required service then the requiring service can automatically be brought down first.
+1
Once we start tracking resource collection as a dependency (because one host's configuration is now dependent on another's), plus a centralized database containing all compiled catalogs, we've basically got builtin node-order dependencies, all emergent rather than declared.
+1
Obviously, this is 80% theory, 15% plan, and 5% bs, but we do have ideas for how it'll work, and we're making baby steps toward getting some of it actually done.
+1 Regards, David -- dasz.at OG Tel: +43 (0)664 2602670 Web: http://dasz.at Klosterneuburg UID: ATU64260999 FB-Nr.: FN 309285 g FB-Gericht: LG Korneuburg -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
