mesos-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Benjamin Bannier (JIRA)" <>
Subject [jira] [Updated] (MESOS-7074) port_mapping isolator: do not depend on /sys/class/net/<ifname>/speed
Date Thu, 09 Feb 2017 14:25:42 GMT


Benjamin Bannier updated MESOS-7074:
    Component/s: isolation

> port_mapping isolator: do not depend on /sys/class/net/<ifname>/speed
> ---------------------------------------------------------------------
>                 Key: MESOS-7074
>                 URL:
>             Project: Mesos
>          Issue Type: Improvement
>          Components: isolation
>            Reporter: Pierre Cheynier
>            Priority: Minor
> I tried to use network/port_mapping isolator and faced this issue:  {{/sys/class/net/<ifname>/speed}}
is unreadable because it is not set by the underlying network driver.
> * on virtualized environment (KVM, virtualbox, AMIs, etc.)
> * on CentOS 7 with teaming driver enabled, it doesn't report the speed.
> {noformat}
> # cat /sys/class/net/team0/speed 
> cat: /sys/class/net/team0/speed: Invalid argument
> {noformat}
> Here is a pointer to the code blocks that perform those tests:;a=blob;f=src/slave/containerizer/mesos/isolators/network/port_mapping.cpp;h=f6f2bfe1d5d3c113036ad44a480f97bbb462a269;hb=HEAD#l1588
> In my opinion, to solve most of these use-cases, we could make those tests non-blocking,
i.e. replace errors by log/warnings.
> It could result in an inconsistency between the interface speed and the bw_limit set,
but I guess there are more benefits in making it usable in more environments.

This message was sent by Atlassian JIRA

View raw message