----- "Dan Bode" <[email protected]> wrote: >> sure, but it just shows why global variables have been abandoned by >> all but the most sucky devs and languages, puppet has some way to go >> to make this easy for us to do the right thing :) > > > I wish I had a better response for this point ;) Except I will say > that something feels natural about injecting parameters into a puppet > run (maybe thats what other global variable supporters would say).
I don't think it's the end of the world too right now, but puppet needs a lot of work to get to the point where we can really start sharing modules as a group. This is one of them and the work is ongoing so thats encouraging > there's no such tool - at least not in public domain, again I agree > with you but it would take ages to write a fully flexible node tool, > foreman and dashboard both suffer from a lot of assumption about how > the authors/designers thinks architectures should work that doesn't > translate well to all cases. > > The Dashboard is supposed to be this tool. > Can you be specific about what you think those limitations are? I need another look at it, it's been a while and I forget the specifics of what it was. > > Wouldnt there be cases where you have to change every line of puppet > > code that uses the extlookup tool if the properties that determine > the > > lookup change? > > not that I can think of. > > > when I say properties, I mean, its no longer determined by DC, but by > some other fact. that's fine - you have one place where you configure the lookup ordering - in site.pp in the global scope - and if you want to change you change the config not the extlookup calls. >> These are facts about a node, it should be on the node and it has a >> lot of use being on the node (see how mcollective does discovery for >> example). though that said, nothing prevents you from just writing a >> list of classifier provided facts onto the node to achieve the same. > > > thats an interesting point. How are you handle those facts? Do you > keep a description of the location of machines on the local > filesystem? Or is ipaddress enough to create these facts? it varies, these are some of my facts: country = dynamic location = dynamic by way of a nasty case statement on ips environment = saved on the box in a text file dom0 (fqdn of my dom0) = put there during kickstart customer = saved on the box in a text file, easy to do in ks too -- 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.
