[
https://issues.apache.org/jira/browse/MESOS-5545?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15320093#comment-15320093
]
Fan Du commented on MESOS-5545:
-------------------------------
[~avin...@mesosphere.io] Thanks for the comments, apparently you did LLDP
homework :)
The topology here only refer to the access layer, that is the switch the agent
directly connected to. And lldptool will take care of parsing LLDP packet in
various ways, so to my best knowledge, this will not relate to libprocess part.
You are right about LLDP has boundary of next bridge, i.e. only hop one time,
in the scenario when OpenvSwitch invovled, Mesos runs inside KVM guest, I can
think of two ways here:
1. It's the LLDP packets set by ovs bridge that matters so far, because ovs
bridge now is the access bridge, and lldpad daemon will broadcast LLDP packets.
2. After commit
[784b58a3|https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=784b58a327ad16967ab64bbfa558df81980d31e9],
sys knobs could be tweaked to forward LLDP packets.
I don't have any comments about using the label/attributes at the time being, I
will work out something more appealing based on it.
Will let you my thoughts!
> Add rack awareness support for Mesos resources
> ----------------------------------------------
>
> Key: MESOS-5545
> URL: https://issues.apache.org/jira/browse/MESOS-5545
> Project: Mesos
> Issue Type: Story
> Components: hadoop, master
> Reporter: Fan Du
> Attachments: RackAwarenessforMesos-Lite.pdf
>
>
> Resources managed by Mesos master have no topology information of the
> cluster, for example, rack topology. While lots of data center applications
> have rack awareness feature to provide data locality, fault tolerance and
> intelligent task placement. This ticket tries to investigate how to add rack
> awareness for Mesos resources topology.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
