On Dec 14, 3:44 am, Daniel Pittman <[email protected]> wrote: > On Tue, Dec 14, 2010 at 19:31, James Turnbull <[email protected]> wrote: > > Andrew J. Forgue wrote: > >> This patch gives Puppet the ability to find a puppet master via SRV > >> records in DNS. First Puppet will try to resolve the server parameter > >> in puppet.conf (or supplied on command line) to an SRV record before > >> treating it as a regular host. This patch basically adds client-side > >> load-balancing. > > > I'd probably like to see this as configurable rather than the default > > perhaps? > > I can't personally see the harm in having it running by default, as > is: it only does anything if you have configured SRV records for the > puppet protocol, and only if they were against the default or > configured puppet server name.
This was my thought too. Plus - If you went to the trouble of configuring SRV records against 'puppet' (the default) you obviously did so on purpose. While not RFC spec _service._protocol.domain.com, puppet would still do the right thing. -Andrew > > I would be more reluctant to see auto-discovery in the form of doing > SRV lookups against, say, the default domain name of the client, but > that isn't what is being proposed here. > > Regards, > Daniel > -- > ✣ Daniel Pittman ✉ [email protected] ☎ +61 401 155 707 > ♽ made with 100 percent post-consumer electrons -- You received this message because you are subscribed to the Google Groups "Puppet Developers" 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-dev?hl=en.
