Mike, I would use a server side function that uses either LDAP or a flat file to determine the attributes applied to the node.
Although, if you need this to be more 'real time', you'll probably want to look at something like ControlTier, Capistrano, or Func. Trevor On Wed, Jan 21, 2009 at 04:37, Mike Pountney <mike.pount...@gmail.com> wrote: > > > On 20 Jan 2009, at 18:52, Jeff Leggett wrote: > >> >> I just did something similar to parse out what proxy my client should >> use - for a custom fact do: >> >> Facter.add(:network) do >> setcode do >> srcIP = Facter.value(:ipaddress) >> octets = srcIP.split (/\./ ) >> >> <logic specific to your use> >> >> end >> end > > > We currently use a similar system for establishing settings like > resolvers, proxies, and other local-network settings. > > However, I'm now thinking that using a host-generated fact was not > ideal for this purpose - after moving a bunch of servers from one > network to another. > > Essentially, as facter does not report the ipaddress change (and hence > network change) until the node is booted with its new IP, the network > settings are all wrong until the node can talk to the puppetmaster > again - which is likely cannot do as (for example) its resolver > settings are pointing to the DNS servers on the old network. > > For this reason, I'm planning to implement a node-level 'location' > variable, which can be changed manually before a node move, allowing > the node to get all its new settings prior to the move. > > What do others do to solve this problem? > > Regards, > > Mike > > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
