On Wed, Mar 22, 2017 at 1:40 PM, Ewoud Kohl van Wijngaarden < ew...@kohlvanwijngaarden.nl> wrote:
> On Mon, Mar 20, 2017 at 03:50:30PM +0000, Sean O'Keeffe wrote: > > On Mon, Mar 20, 2017 at 2:25 PM, Lukas Zapletal <l...@redhat.com> wrote: > > > 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. > > I think a different URL for clients and Foreman itself makes a lot of > sense. Now I have some trouble reading the design from the code. Could > you describe how this would be used by a user? Maybe a screenshot from > the new configuration page. > Sure, I've added another tab to the Smart Proxies form, where you can add "Secondary URLs". On the Host/Hostgroup from the user can then select a URL for attributes like Puppet Master, Puppet CA (and Openscap and content source for those plugins). I've uploaded some pictures to the PR as well which should explain it much better. https://github.com/theforeman/foreman/pull/4346#issuecomment-288461410 One thing Stephen mentioned on the PR was if URLs could have many proxies as well as proxies have many URLs. That would go someway to better load balanced proxies. Which I think would be great, though I personally don't like the idea of another form & menu item just to create URLs, I think we have lots of forms and menu items already.. Sean > > > > 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. > -- 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.
