Issue #3669 has been updated by Jacob Helwig. Assignee deleted (Jacob Helwig) Branch set to https://github.com/jhelwig/puppet/tree/ticket/next/3669-make-puppet-honor-DNS-SRV-records
My branch has another "Work-In-Progress" commit on top of the work Daniel had done on the branch. My WIP commit fixes a couple of missed method renames, and adjusts the weighted shuffle used for picking servers to better match what is described in [RFC 2782](http://www.rfc-editor.org/rfc/rfc2782.txt) for handling 0 weighted entries. There is still some work left to do that Jesse and I discovered in our review of the branch. SRV record support shouldn't be turned off if you specify a server to use, since you should be able to specify a fall-back server to use other than the default of "puppet". Also, the CA, reports, and file-serving look like they would be broken by this, unless you had "puppet" resolvable by DNS. We should probably open up discussion about whether the full SRV record name should be specified in the setting, or just the domain to use for the SRV record. Jesse and I are of the opinion that only the domain should be specified in the config. It would be really nice to have SRV services for `_puppet_ca`, `_puppet_report`, and `_puppet_fileserver` (all of which falling back to `_puppet`, then the server setting), though these don't seem absolutely necessary for a first-round feature, provided you can still adjust the server setting when SRV record support is enabled. ---------------------------------------- Feature #3669: Make puppet honor DNS SRV records https://projects.puppetlabs.com/issues/3669 Author: Martin Marcher Status: Accepted Priority: Normal Assignee: Category: Target version: Statler Affected Puppet version: development Keywords: Branch: https://github.com/jhelwig/puppet/tree/ticket/next/3669-make-puppet-honor-DNS-SRV-records 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.
