Support #11319
closed
foreman smart proxy concept
Description
hello,
can someone help me understand this smart proxy concept? i have already read through all your documentation that's available to me and still not understand.
so example:
i have foreman server in network 105.1.43.x (eth0) and 192.168.10.x (eth1), a seperate host that i call proxy1 in network 105.1.43.x (eth0) and 192.168.100.x (eth2)
i am able to provision all my clients in 192.168.10.x without problem by configurating foreman itself as smart proxy on eth1
I am also able to provision all my clients in 105.1.43.x without problem even throught it seems i cannot get it done through foreman GUI and i have to hack it through back door by modifying it's dhcp configuration manully but i get it done.
The problem comes now, that when i am trying to setup provison clients on 192.168.100.x network through proxy1.
when clients on 192.168.100.x are booted and through dhcp and tftpboot of proxy1, it comes up to discovery mode. but when it tries to register proxy1 it says connection refused. so do you mean i have to configure it to make it to register to foreman host instead of proxy1? there is no network to connect to foreman. is there was network then why do i need smart proxy of proxy1?
can someone please kindly point me to the right direction how i should make this work?
thank you,
Files
Updated by Dominic Cleal almost 9 years ago
- Project changed from Smart Proxy to Discovery
- Category changed from DHCP to Smart Proxy Plugin
I think you're saying you're trying to use Discovery's smart proxy plugin for clients and are getting a connection refused message. Moving the ticket to that project - it'd probably help them to show precisely what kernel arguments your Discovery image is booting with.
Updated by Lukas Zapletal almost 9 years ago
Please read our discovery plugin carefully, there is explained how discovered nodes communicate with foreman instance (via proxy or not). Specifically "proxy.type" setting.
http://theforeman.org/plugins/foreman_discovery/3.0/index.html
Also prefer using our mailing lists to support tickets.
Updated by tony zheng almost 9 years ago
sorry company security policy not allow me to signing up mailing list from outside.
but here is my kernel lines from proxy server's tftpboot:
DEFAULT menu
PROMPT 0
MENU TITLE PXE Menu
TIMEOUT 200
TOTALTIMEOUT 6000
ONTIMEOUT discovery
LABEL local
MENU LABEL (local)
MENU DEFAULT
LOCALBOOT 0
LABEL discovery
MENU LABEL (discovery)
KERNEL boot/fdi-image/vmlinuz0 fdi.ssh=1 fdi.rootpw=redhat
APPEND initrd=boot/fdi-image/initrd0.img rootflags=loop root=live:/fdi.iso rootfstype=auto ro rd.live.image acpi=force rd.luks=0 rd.md=0 rd.dm=0 rd.lvm=0 rd.bootif=0 rd.neednet=0 nomodeset selinux=0 stateless proxy.url=http://192.168.12.1 proxy.type=foreman
IPAPPEND 2
once again, my clients booting up to the proxy getting error message registing with foreman. it says:
discovery-register620: Could not send facts to foreman: connection refused - connect (2)
let me know if you need anything else for troubleshoot.
thanks,
Updated by tony zheng almost 9 years ago
here is the foreman-debug output from the client that was booted off the proxy.
thanks,
Updated by Lukas Zapletal almost 9 years ago
- Status changed from New to Closed
Our mailing lists are available via web (Google Groups). http://theforeman.org/support.html You will get faster response as many more eyes will read your configuration issue.
What you pasted above is configuration for Discovery 1.x series, I assume you have newer version. Please read our documentation I linked above.
The debug you've sent is zero-sized and unusable. You can use `-u` option to upload the tarball to your debug server.