[
https://issues.apache.org/jira/browse/MESOS-2129?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14218297#comment-14218297
]
Cody Maloney commented on MESOS-2129:
-------------------------------------
So making the WebUI just work whatever master you connect to (Or even if you
connect to a slave if someone thinks it is useful) I think is an independent
ticket set. Currently people need to have firewall access to the master nodes
open for management. So I'm not trying to fix that.
Definitely you could sit on top of this work to solve MESOS-672 by registering
a "master leader" endpoint and having the WebUI always call through it to get
to all the cluster information. As it stands people worked around MESOS-672
already.
Solving the general "All mesos hosts must be able to route to all other mesos
hosts" problem which means things like NAT and internal vs. external IPs break
things at times I think is independent and very far out of scope from this
work. That work people also definitely want, but it requires a lot more
internal changes to how libprocess operates.
> Enable managing mesos without having to be able to connect to each slave
> ------------------------------------------------------------------------
>
> Key: MESOS-2129
> URL: https://issues.apache.org/jira/browse/MESOS-2129
> Project: Mesos
> Issue Type: Epic
> Reporter: Cody Maloney
> Assignee: Cody Maloney
>
> Ideally we want to use the full mesos WebUI from an office, which is
> firewalled off from the vast majority of hosts in the datacenter (mesos
> slaves). It also becomes burdensome to manage a precise firewall for
> additional hosts, since every time a slave comes/goes if we don't want to
> allow blanket access to the slave port, we have to add / remove firewall rules
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
