You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@mesos.apache.org by "Chris Lambert (JIRA)" <ji...@apache.org> on 2014/05/12 20:24:18 UTC
[jira] [Updated] (MESOS-1228) Container level network monitoring
[ https://issues.apache.org/jira/browse/MESOS-1228?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Chris Lambert updated MESOS-1228:
---------------------------------
Affects Version/s: (was: 0.19.0)
Fix Version/s: (was: 0.19.0)
0.20.0
> Container level network monitoring
> ----------------------------------
>
> Key: MESOS-1228
> URL: https://issues.apache.org/jira/browse/MESOS-1228
> Project: Mesos
> Issue Type: Story
> Components: containerization, isolation, statistics
> Reporter: Jie Yu
> Assignee: Jie Yu
> Fix For: 0.20.0
>
>
> Our goal is to get per-container network statistics. For instance, number of packets received/sent (RX_PACKETS, TX_PACKETS), how many bytes received/sent (RX_BYTES, TX_BYTES), etc.
> We have a couple of options here for implementing it.
> 1) If we have enough IPs (we are assuming IPv4 here as most people are still using IPv4) such that each container can has an individual IP, we can leverage the Linux bridge.
> 2) If we don't have enough IPs, we can use port forwarding based on port ranges. In other words, each container will be assigned a range of ports from the host. The isolator will setup filters to properly redirect packets to the corresponding containers based on dst ip/ports.
> 3) We can use NAT if the processes running inside a container does not need public IPs.
> Our first step is to go with option (2).
--
This message was sent by Atlassian JIRA
(v6.2#6252)