Currently if the Puppet server hostname is not in DNS (e.g. private IP space and/or served from an alternate/private DNS server) provisioned nodes cannot connect to the puppet server. We want to allow for the custom/puppet_configure post script to be able to add and /etc/hosts entry for the Puppet server.
Here is the initial idea to address this...
Update custom/puppet_configure to:
Set the server from an optional command line flag, e.g. --host mf-pup01.local
If no --host flag is passed, default to using $puppetmaster from site table (the current approach in the script). This keeps current setups working as expected.
If an --ip flag is specified with an IP address (e.g. --ip 10.1.30.93), then add the supplied IP (and hostname from above) to /etc/hosts
The other advantage to this is that eventually we could point specific nodes or groups to differing Puppet servers. e.g. As we grow in scale we may need to have various parts of a cluster use unique Puppet servers.
Currently if the Puppet server hostname is not in DNS (e.g. private IP space and/or served from an alternate/private DNS server) provisioned nodes cannot connect to the puppet server. We want to allow for the
custom/puppet_configurepost script to be able to add and/etc/hostsentry for the Puppet server.Here is the initial idea to address this...
Update custom/puppet_configure to:
--host mf-pup01.local--hostflag is passed, default to using$puppetmasterfromsitetable (the current approach in the script). This keeps current setups working as expected.--ipflag is specified with an IP address (e.g.--ip 10.1.30.93), then add the supplied IP (and hostname from above) to/etc/hostsThe other advantage to this is that eventually we could point specific nodes or groups to differing Puppet servers. e.g. As we grow in scale we may need to have various parts of a cluster use unique Puppet servers.