You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@aurora.apache.org by "Abhinav Gupta (JIRA)" <ji...@apache.org> on 2015/01/27 21:49:34 UTC

[jira] [Commented] (AURORA-328) Scheduler should key slaves off slaveID, not hostname

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

Abhinav Gupta commented on AURORA-328:
--------------------------------------

Hello :)

I would like to contribute and I am good at coding in Java and C++. 
I have cloned the source of aurora, but since I haven't contributed to any open source project earlier, I wasn't sure on how bugs are taken up. 

I intend to solve this bug, could you please guide me on how to start with this bug ?

Thank you for your time :)

> Scheduler should key slaves off slaveID, not hostname
> -----------------------------------------------------
>
>                 Key: AURORA-328
>                 URL: https://issues.apache.org/jira/browse/AURORA-328
>             Project: Aurora
>          Issue Type: Story
>          Components: Scheduler
>            Reporter: Kevin Sweeney
>            Priority: Minor
>              Labels: newbie
>
> In the case that multiple slaves exist on the same host, the scheduler should be able to disambiguate. Mesos already provides the UUID "SlaveID" so this should be straightforward. Maintenance might need a refactor to support this.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)