Return-Path: 
 <mesos-dev-return-214-apmail-incubator-mesos-dev-archive=incubator.apache.org@incubator.apache.org>
X-Original-To: apmail-incubator-mesos-dev-archive@minotaur.apache.org
Delivered-To: apmail-incubator-mesos-dev-archive@minotaur.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id 481D574DF
	for <apmail-incubator-mesos-dev-archive@minotaur.apache.org>;
 Tue, 18 Oct 2011 22:05:35 +0000 (UTC)
Received: (qmail 68660 invoked by uid 500); 18 Oct 2011 22:05:35 -0000
Delivered-To: apmail-incubator-mesos-dev-archive@incubator.apache.org
Received: (qmail 68625 invoked by uid 500); 18 Oct 2011 22:05:34 -0000
Mailing-List: contact mesos-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:mesos-dev-help@incubator.apache.org>
List-Unsubscribe: <mailto:mesos-dev-unsubscribe@incubator.apache.org>
List-Post: <mailto:mesos-dev@incubator.apache.org>
List-Id: <mesos-dev.incubator.apache.org>
Reply-To: mesos-dev@incubator.apache.org
Delivered-To: mailing list mesos-dev@incubator.apache.org
Received: (qmail 68596 invoked by uid 99); 18 Oct 2011 22:05:34 -0000
Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 18 Oct 2011 22:05:34 +0000
X-ASF-Spam-Status: No, hits=-2000.5 required=5.0
	tests=ALL_TRUSTED,RP_MATCHES_RCVD
X-Spam-Check-By: apache.org
Received: from [140.211.11.116] (HELO hel.zones.apache.org) (140.211.11.116)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 18 Oct 2011 22:05:31 +0000
Received: from hel.zones.apache.org (hel.zones.apache.org [140.211.11.116])
	by hel.zones.apache.org (Postfix) with ESMTP id BE9C730FAA6
	for <mesos-dev@incubator.apache.org>; Tue, 18 Oct 2011 22:05:10 +0000 (UTC)
Date: Tue, 18 Oct 2011 22:05:10 +0000 (UTC)
From: "Sumedh Sawant (Commented) (JIRA)" <jira@apache.org>
To: mesos-dev@incubator.apache.org
Message-ID: 
 <407619456.8152.1318975510782.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <2031549577.4249.1314072089403.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (MESOS-33) Fix slave webui representation and
 pass back to master.
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394
X-Virus-Checked: Checked by ClamAV on apache.org


    [ https://issues.apache.org/jira/browse/MESOS-33?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13130066#comment-13130066 ] 

Sumedh Sawant commented on MESOS-33:
------------------------------------

Hi, I'm an undergrad new to Mesos who is starting to work on fixing this bug. 

After looking at the code, I think on a broad level the "mesos/src/webui/slave/webui.py" file needs to be modified to add a new "@route('\master')" to return template(master's index.tpl, slave's master_port). 

It seems that in order for this to happen, the other relevant files need to be modified so that the slave's master_port can be accessed in "mesos/src/slave/webui.cpp" and treated the same way as slavePort, webuiPort, logDir, workDir. 

As I'm starting to figure out which files need to be modified, I noticed that the "start" method in the slave webui.cpp has a parameter called  
"process::PID<Slave>& slave". What is this parameter? I was thinking that some of the slave code could be modified to add access to the master port so that this "process::PID<Slave>& slave" parameter could be used to access the master port as well. 

Does anyone with more experience have some pointers?

                
> Fix slave webui representation and pass back to master.
> -------------------------------------------------------
>
>                 Key: MESOS-33
>                 URL: https://issues.apache.org/jira/browse/MESOS-33
>             Project: Mesos
>          Issue Type: Bug
>          Components: ec2, master, slave, webui
>            Reporter: Benjamin Hindman
>
> A slave needs to report both it's webui hostname AND it's port back to the master so that it can correctly display them in it's own webui.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira