On Tuesday, August 21, 2012 1:22:24 PM UTC-4, Craig White wrote: > > > ---- > if you have packages that are pre-requisites for more than one other > package, create a separate class and include the class where desired. Done. > ---- >
Ok, I'm just making sure that I understand what you're saying. Are you saying that the proper way to handle packages in puppet is to manage the packages required by my classes with the built in package resource type and whenever puppet pitches errors because of a package collision, to add a class that wraps that package resource definition and then change the manifests to include the class instead of defining the package directly? I guess I must not understand what you mean, because that doesn't sound particularly desirable to me. ---- > Hiera will be part and parcel of puppet 3 so you would be better off > designing to live with it rather than try to force life without it long > term. > > Ok, this is good to know. I guess I'll read up more on it. Thanks. > I'm sort of suspicious that you are trying to use Singleton as a means to > avoid a full implementation of puppet. It seems that trying to shortcut > understanding of puppet leads to frustration. > > I'm not sure what I said that led you to believe this is what I'm doing. I'm asking for advice as to what the "correct" way to handle this in puppet is. I laid out all the ways I've come up with to (try to) deal with my problem. What I don't know is why this isn't easier. It makes me feel like I'm doing it all wrong. And I'm not sure what you mean by "full implementation". You mean, without hiera? Or is there something else fundamentally wrong with what I'm doing? Honestly, we've barely started with our implementation of puppet. In our test environment, we have working classes for a few services and have a loose framework in place that handles some of the thornier issues of our environment. We've read a lot of docs, added parser functions, added custom facter facts, added custom augeas lenses, etc. I've found simple, fairly elegant ways to deal with almost everything I've tried to do in puppet. I'm just feeling that maybe I'm missing the big picture or maybe, at least, A big picture. I'm not trying to work around anything. I'm just trying to figure out the best way to use puppet to manage my hosts in a way that is easy to understand, audit and maintain. I'm sorry that wasn't clear from my original post. I guess I feel that I'm starting to understand some of the knobs in puppet, but I maybe don't understand the plan. That's why I came here. I hoped someone here had a better understanding of the big picture (or a simple solution to my current problem). thanks for your help, Michael -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/hKuxYppzCYoJ. 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.
