[ 
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

        

Reply via email to