By default as per Puppet behaviour the Puppet Master, Puppet CA and NATS brokers are all found on the name puppet. If you are doing a single node NATS installation on the Puppet Master called puppet you do not neeed to configure anything and can continue to the next page.
When not using puppet you can configure these settings manually but we strongly suggest you use SRV records if at all possible.
You can configure where your NATS brokers live using these SRV records:
_x-puppet-mcollective._tcp IN SRV 10 0 4222 nats1.example.net. _x-puppet-mcollective._tcp IN SRV 11 0 4222 nats2.example.net. _x-puppet-mcollective._tcp IN SRV 12 0 4222 nats3.example.net.
This means you have 3 of them and they all listen on port 4222.
If your Puppet CA, PuppetDB and Puppet Server are all on the same host, you can configure that all with a single SRV record that is compatible with Puppet SRV setup.
_x-puppet._tcp IN SRV 10 0 8140 puppet1.example.net.
But if you wish to split the CA and DB from the master add these:
_x-puppet-ca._tcp IN SRV 10 0 8140 puppetca1.example.net. _x-puppet-db._tcp IN SRV 10 0 8081 puppetdb1.example.net.
By default these SRV records will be looked for in your machines domain fact, but you can customize this by creating data in your Hiera:
mcollective_choria::config: srv_domain: "prod.example.net"
You might be in a situation where you have multiple environments like development and production in the same domain. You might want to use SRV for production but not for development.
0.0.16 you can disable SRV lookups entirely:
mcollective_choria::config: use_srv_records: false
If you have to you can configure these locations manually by creating Hiera data:
mcollective_choria::config: use_srv_records: false puppetserver_host: "puppet1.example.net" puppetserver_port: 8140 puppetca_host: "ca1.example.net" puppetca_port: 8140 puppetdb_host: "pdb1.example.net" puppetdb_port: 8081 middleware_hosts: "nats1.example.net:4222,nats2.example.net:4222,nats3.example.net:4222"