Bug #11583
closed
unattended_url is not high available
Added by Daniel Lobato Garcia over 8 years ago.
Updated over 8 years ago.
Description
On installations of Foreman that serve templates through the smart-proxy, we want Foreman to show the smart-proxy URL on the 'compiled' templates, so that hosts would access the smart-proxy instead of Foreman.
This works well if you have one smart-proxy.
However, if your network is segmented, and you're trying to serve templates from the smart-proxy to your hosts, that is not possible currently. With only one unattended_url setting, all you can do is to serve templates to hosts in the same network as the smart-proxy URL you set in unattended_url.
My proposed solution would be to allow subnets in Foreman to have their own unattended_url setting which would take precedence over the default one. This way hosts in segmented networks could get templates from their respective smart-proxies. As of now, it's not possible.
- Status changed from New to Feedback
unattended_url should be set on Foreman to be the same as the template_url (on /etc/smart-proxy/settings.d/templates.yml) to provide that URL on the PXE/kickstart templates. Unless I missed something, the proxy will not modify the templates coming from Foreman and compile them with the proxy URL. foreman_url('provision') for instance, will just use the unattended_url (which can be a single proxy URL).
A way to reproduce this with libvirt:
- Create 2 networks, network A 192.168.122.0/24 , and network B 192.168.121.0/24 . All that matters is that hosts in one won't be able to access the other.
- Setup Foreman in any of the networks, or a third. Setup a proxy in each network. Only proxies can connect to Foreman, but nothing else on these networks can reach outside traffic.
- Problem: Modify unattended_url in Foreman to be the same as template_url. So that foreman_url('provision') would be able to resolve to the proxy for templates.
Which template_url? The one on proxy in network A or proxy in network B? At this point we are effectively disabling provisioning on one of the networks, as foreman_url('xxxx') is going to resolve to the URL of one of the proxies.
- Status changed from Feedback to Closed
Closing as I didn't read that part. Thanks!
- Status changed from Closed to Rejected
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by