> > > > > Logging and ntp probably fall into the simple category. > > > > A couple more interesting ones are DHCP and Provisioner. Both of these > > need to have a list of all the nodes known to crowbar injected into > > them, for the recipes to use. Settling on a pattern there would > > probably be a great start for other places where we currently do search. > > I would not try to make the cookbooks in the provisioner barclamp attribute > driven right now. They might make ina interesting case study, but the > functionality they implement is both tied pretty intimately with the rest of > Crowbar and would not be made more comprehensible by removing search. >
I was suggesting we start the design discussion, not actual implementation. These 2 examples can serve as a basic start for the design discussion. That said, I've seen quite a few places where e.g. ssh authorized keys were not generated correctly because of search issues (computed by the provisioner), which might be alleviated with more consistent search results. _______________________________________________ Crowbar mailing list Crowbar@dell.com https://lists.us.dell.com/mailman/listinfo/crowbar For more information: http://crowbar.github.com/
