Issue #3669 has been updated by Martin Marcher.
Ohad Levy wrote: > * will this support weight as well (e.g. try local server first, fallback to > a remote server)? > * what happens on a failure (timeout, manifest error etc) In my opinion it should. Not supporting weight would mean that actually there's no support for SRV records as it's part of the SRV record definition... ---------------------------------------- Feature #3669: Make puppet honor DNS SRV records http://projects.puppetlabs.com/issues/3669 Author: Martin Marcher Status: Accepted Priority: Normal Assigned to: Category: Target version: Affected version: development Keywords: Branch: I'd like to be able to define where puppet looks for the master server. I propose the following: By default try in the following order: 1. Look for a "_x-puppet._tcp.example.com" SRV record (or any name that you think is appropriate, but keep it a SRV record) 2. For backwards compatibility, if no SRV record is present look for puppet.example.com as a fallback or any value that is configured in the puppet config file Reasoning: A System Administrator can easily spread out the load over multiple puppet servers in this way or define some split horizon which answers with the "correct" hostname to use as a puppet master. Thanks, Martin -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://projects.puppetlabs.com/my/account -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" 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-bugs?hl=en.
