Feature #26164
closedProvide Puppet (CA) multi homing
Description
Currently the generated puppetmaster and puppet_ca_server hostnames are the same as the smart proxy.
This isn't always the case. When you have a setup:
Foreman <-> Smart Proxy <-> Hosts
Here you have a private LAN between Foreman and its Smart Proxies. There is another network which has hosts. Here you'd have the Puppet (CA) on the host network. In hostnames:
- foreman.lan.example.com (192.0.2.2)
- proxy.lan.example.com (192.0.2.3)
- proxy.wan.example.com (198.51.100.3)
- puppet.wan.example.com (198.51.100.4)
- puppetca.wan.example.com (198.51.100.5)
In /etc/foreman-proxy/settings.d/puppet_proxy_puppet_api.yml
you'd configure:
:puppet_url: https://puppet.wan.example.com:8140
In /etc/foreman-proxy/settings.d/puppetca_http_api.yml
(Proxy 1.22) you'd configure:
:puppet_url: https://puppetca.wan.example.com:8140
By using the new capabilities framework we can expose these settings to Foreman. Foreman can use these to present the correct hostnames, like in the provisioning templates.
Updated by The Foreman Bot over 5 years ago
- Status changed from New to Ready For Testing
- Assignee set to Ewoud Kohl van Wijngaarden
- Pull request https://github.com/theforeman/foreman/pull/6513 added
Updated by Ewoud Kohl van Wijngaarden over 5 years ago
- Related to Feature #4345: Puppet CA proxy added
Updated by Ewoud Kohl van Wijngaarden over 5 years ago
- Related to Feature #26322: Expose the Puppet API URLs added
Updated by Tomer Brisker over 5 years ago
- Target version changed from 1.22.0 to 1.23.0
Looks like this didn't make it in to 1.22.
Updated by Tomer Brisker about 5 years ago
- Target version deleted (
1.23.0)
this is still wip and missed the 1.23 branching.
Updated by Ewoud Kohl van Wijngaarden almost 5 years ago
- Status changed from Ready For Testing to Closed
Applied in changeset c2317d4430325be04df9ddfe65f47223b7733b8b.
Updated by Ewoud Kohl van Wijngaarden almost 5 years ago
- Category changed from PuppetCA to Puppet integration