Issue #3669 has been updated by Jacob Helwig.
Status changed from Code Insufficient to In Topic Branch Pending Merge
I've had some time to work on my WIP branch, and address the concerns that were
raised previously. I'd appreciate it if people could test this branch out, and
provide feedback.
<pre>
(#3669) Find servers via DNS SRV records
This adds two new configuration variables:
* use_srv_records: Will attempt to lookup SRV records for hostname
found in srv_record (default: true)
* srv_domain: The domain that will be queried for SRV records,
(default: $domain)
If use_srv_records is set to true, then Puppet will attempt to find
the list of servers to use from SRV records on the domain specified
via srv_domain. The CA, report, and file servers can all be specified
via independent SRV records from the SRV records to use for looking up
the catalog server.
The SRV records must be for hosts in the form:
_puppet._tcp.$srv_domain
_puppet_ca._tcp.$srv_domain
_puppet_report._tcp.$srv_domain
_puppet_fileserver._tcp.$srv_domain
If no records are found for the _puppet_ca, _puppet_report, or
_puppet_fileserver services , then the SRV records for the _puppet
service. However, if records exist for any of the more specific
services, Puppet will not attempt to use the _puppet service to find
an applicable server.
If Puppet is unable to connect to any of the servers specified in the
SRV records, then it will attempt to connect to the "normal" servers
settable via puppet.conf.
</pre>
----------------------------------------
Feature #3669: Make puppet honor DNS SRV records
https://projects.puppetlabs.com/issues/3669
Author: Martin Marcher
Status: In Topic Branch Pending Merge
Priority: Normal
Assignee: Jacob Helwig
Category:
Target version: 2.7.x
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.
