Re: Catching the webui up to features

2017-10-18 Thread Timothy Anderegg
We have a similar scenario using an actual proxy (Apache in this case) in front of a firewalled VLAN, that also does Kerberos authentication against the endpoints. This currently works fine for external API requests but the WebUI is only partially functional, since I haven't looked into the newer

Re: Catching the webui up to features

2017-10-18 Thread Aaron Wood
In this case localhost is my host (OSX) and u64 is my guest (Ubuntu VM). What I was doing was viewing the Mesos UI from my host by making use of port mapping in my VM. Port 10050 on my host maps to 5050 inside my VM. So in a way this is like viewing the UI with a proxy in the middle. What I was

Re: Catching the webui up to features

2017-10-17 Thread Benjamin Mahler
What does localhost vs u64 represent for you there in terms of your actual cluster? Are you expecting to be able to publicly access the masters and agents? Or are you running a proxy (like DC/OS's adminrouter)? We recently made some changes that makes it easier to patch the UI to work with a

Re: Catching the webui up to features

2017-09-26 Thread Aaron Wood
You're right about the slaves section in 0.28.x. There are no error messages or modals that pop up but looking at the requests after you click on a slave in the slaves section shows these obvious failures (u64 is the hostname of my VM which won't be resolved from the host): Request URL:

Re: Catching the webui up to features

2017-09-25 Thread Benjamin Mahler
0.28.x UI is working for you even when you click into an agent? Can you show us which requests are being made in the old UI vs the new UI and which ones do not work for you? (use chrome's built-in debugging tools) On Mon, Sep 25, 2017 at 3:38 PM, Aaron Wood wrote: > I

Re: Catching the webui up to features

2017-09-25 Thread Aaron Wood
I just built Mesos 0.28.x and tried out this scenario. It seems that this issue presents itself only in 1.0.x and up. I also found out that DCOS hides this issue if someone uses https://github.com/dcos/adminrouter I have not dug through the 0.28.x code enough to pinpoint the exact area for where

Re: Catching the webui up to features

2017-09-13 Thread Benjamin Mahler
+haosdent, vinod Blaming the lines you pointed to gives me: https://github.com/apache/mesos/commit/b2fc58883e2cd0ca144fd1b0e10cad4235a50223 I've added vinod and haosdent since they were involved in the change, it looks like this makes the master talk directly to a different master host:port. Is

Re: Catching the webui up to features --> setup for AWS cluster

2017-09-12 Thread Paul Verdone
    On a brand new installation without a tunnel, I get the same behavior on AWS builds (external IP to users of GUI, internal IP between the members of the cluster). I believe the solution is to reconfigure the IP and hostname files so that the external IP is recognized for the GUI and the

Re: Catching the webui up to features

2017-09-11 Thread Aaron Wood
Hey Ben, There was a change sometime after Mesos 1.0.x (I think) that altered how the leader state was obtained https://github.com/apache/mesos/blob/master/src/webui/master/static/js/controllers.js#L362-L364 This seems to be an intended change but this causes UI error modals to continually pop

Catching the webui up to features

2017-09-11 Thread Benjamin Mahler
Hi folks, Over time the webui has lagged behind for some of the features that have been added. I'm currently tracking what's required to catch it up here: https://issues.apache.org/jira/browse/MESOS-6440 If you know of other features that make sense to display in the webui, feel free to file a