Hi everyone,
First, thanks for your answers! Actually, after all the researches, I've
also found the Nginx way and this is the more pragmatic one for me.
Thanks again and have a nice day!
2017-06-20 16:29 GMT+02:00 haosdent <haosd...@gmail.com>:
> Hi, @Jean yes, for now, all requests still go to Mesos agents directly
> unless we resolve MESOS-2131.
>
> Our workaround is we have a Nginx proxy, it looks like
>
> ```
> server {
> list 5050;
> list 5051;
>
> location / {
> resolver internal-dns ipv6=off;
>
> auth_request @auth;
> error_page 401 = @sign_in;
>
> proxy_pass http://$http_host;
> }
> }
> ```
>
> So all the domains would bind to the IP of this proxy, but the
> internal-dns would return different internal IP and https/auth/forward your
> requests.
> Hope this could give you some ideas to resolve your problems.
>
> On Tue, Jun 20, 2017 at 7:56 PM, Tomek Janiszewski <jani...@gmail.com>
> wrote:
>
>> There was a try to make reverse proxy on Master https://issues.apache.o
>> rg/jira/browse/MESOS-2131
>> Agents are called directly by the browser so you need to create proxy
>> that will capture requests to agents and pass it to them.
>>
>> wt., 20 cze 2017 o 10:14 użytkownik Jean-Baptiste <jbfa...@gmail.com>
>> napisał:
>>
>>> Hi there!
>>>
>>> Is someone knows if it’s possible to access (from the *Mesos web UI*) to
>>> "*sandboxes*" by proxifying agent requests in any way?
>>>
>>> *Context: *Our network topology doesn’t allow users to access the
>>> agents subnet so when they try to reach the Mesos agent port (eg:
>>> `172.x.x.x:5051`), it doesn’t (obviously) work.
>>>
>>> *Web UI error:*
>>>
>>>
>>> Thanks!
>>>
>>> --
>>>
>>> Jean-Baptiste FAREZ
>>>
>>
>
>
> --
> Best Regards,
> Haosdent Huang
>
--
Jean-Baptiste FAREZ
