On Mon, Mar 20, 2017 at 2:25 PM, Lukas Zapletal <l...@redhat.com> wrote:
> Hey, > Howdy :-) > > I can't remember recommending such a big change :-) Sorry I meant about tagging the email with [RFE] > Can you elaborate more on motivation? Multi-homed proxy is still one > instance, why would > Foreman need to reach to it in two different ways? This is for clients to reach a proxy in the different ways, NOT foreman. > Isn't the result always the same (a change on the same instance)? How > about relaxing > the constraing when each individual proxy must have unique URL? Just > checking before introducing another table (more SQL joins and query > complexity). > If a Host / HostGroups can be assigned a URL/Hostname instead of a proxy its useful for Multi-homing, loadbalancing & NAT'ed environments, maybe others? What does relaxing the unique URL constrain actually give us? I think if you have 2 proxies with the same URL that's just effectively duplicating the object? Or if you mean creating 2 proxies with different URLs (an external & and another internal one) I think would be problematic when Foreman needs to talk to the Proxy. E.g Host needs to talk to proxy1-external.example.com but foreman must talk to the proxy via proxy1-internal.example.com. If we have 2 proxies in foreman ( proxy1-internal & proxy1-external ) and you assign a host proxy1-external foreman would try to connect to proxy1-external.example.com to create a DHCP or DNS or something else with would not work. > > By the way this is (a properly tagged) RFC thread, why you already > imlemented that? You had to spend lot of time on this already, we may > find an alternative and less intrusive solution instead. > Because IMO proper discussions don't tend to actually happen until someone writes the code. Thanks for the reply! Sean > > LZ > > > On Wed, Mar 15, 2017 at 11:18 AM, Sean O'Keeffe <sokee...@redhat.com> > wrote: > > Hey! > > > > So lzap suggested this.. lets see how it goes :-) > > > > I'm looking to solve the following issues > > - I would like to have a multi-homed proxy. > > - I would like clients to connect to a Proxy when there is a NAT between. > > > > My approach has been for proxies to have multiple URLs and during > > provisioning the user would then select a URL instead of the current > method > > of selecting a Proxy, This would be then mean all communication between > the > > Client -> Proxy would be via the selected URL. Each proxy would also > have a > > 'primary' URL which Foreman would always use to connect to it via. > > > > Does this approach make sense? > > Any feedback to greatly appreciated > > > > Changes required: > > Foreman: https://github.com/theforeman/foreman/pull/4346 > > - Adds Proxy URL concept > > - Puppet CA & Puppet Master selection are now URLS > > > > Katello: PR to be raised > > Content Source selection need to list URLS. > > Bootstrap RPM will need to create one for each URL > > > > Let me know what you think or any questions you have! > > Sean > > > > -- > > You received this message because you are subscribed to the Google Groups > > "foreman-dev" group. > > To unsubscribe from this group and stop receiving emails from it, send an > > email to foreman-dev+unsubscr...@googlegroups.com. > > For more options, visit https://groups.google.com/d/optout. > > > > -- > Later, > Lukas @lzap Zapletal > > -- > You received this message because you are subscribed to the Google Groups > "foreman-dev" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to foreman-dev+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "foreman-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to foreman-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
