Project

General

Profile

Feature #26164

Provide Puppet (CA) multi homing

Added by Ewoud Kohl van Wijngaarden 3 months ago. Updated 6 days ago.

Status:
Ready For Testing
Priority:
Normal
Category:
-
Target version:
Difficulty:
Triaged:
No
Bugzilla link:
Team Backlog:
Fixed in Releases:
Found in Releases:

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.


Related issues

Related to Foreman - Feature #4345: Puppet CA proxyNew2014-02-14
Related to Smart Proxy - Feature #26322: Expose the Puppet API URLsClosed

History

#1 Updated by The Foreman Bot 3 months ago

  • Assignee set to Ewoud Kohl van Wijngaarden
  • Status changed from New to Ready For Testing
  • Pull request https://github.com/theforeman/foreman/pull/6513 added

#2 Updated by Ewoud Kohl van Wijngaarden 3 months ago

#3 Updated by Ewoud Kohl van Wijngaarden 3 months ago

#4 Updated by Tomer Brisker 6 days ago

  • Target version changed from 1.22.0 to 1.23.0

Looks like this didn't make it in to 1.22.

Also available in: Atom PDF