[
https://issues.apache.org/jira/browse/MESOS-4738?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15157959#comment-15157959
]
Ian Downes commented on MESOS-4738:
-----------------------------------
[~adam-mesos] The port_mapping isolator does measure ingress and egress
bandwidth per container (plus many other network related metrics) and can set
egress limits (currently at the agent level but the actual isolating code is
flexible). We are definitely interested in supporting bandwidth as a resource!
[~wangcong] for visibility.
> Make ingress and egress bandwidth a resource
> --------------------------------------------
>
> Key: MESOS-4738
> URL: https://issues.apache.org/jira/browse/MESOS-4738
> Project: Mesos
> Issue Type: Improvement
> Reporter: Sargun Dhillon
> Priority: Minor
> Labels: mesosphere
>
> Some of our users care about variable network network isolation. Although we
> cannot fundamentally limit ingress network bandwidth, having it as a
> resource, so we can drop packets above a specific limit would be attractive.
> It would be nice to expose egress and ingress bandwidth as an agent resource,
> perhaps with a default of 10,000 mbps, and we can allow people to adjust as
> needed. Alternatively, a more advanced design would involve generating
> heuristics based on an analysis of the network MII / PHY.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
