[MESOS-1228] Container level network monitoring

• Type: Epic
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 0.20.0
• Component/s: containerization, statistics
• Epic Name: Container Network Monitoring
• Target Version/s: 0.20.0
• Assignee: Jie Yu
• Reporter: Jie Yu
• Shepherd: Vinod Kone
• Created: 22/Apr/14 06:02
• Updated: 26/Apr/17 16:53
• Resolved: 14/Aug/14 17:05

Description

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).

Issue Links

• blocks: MESOS-431 Port isolation / sharing in the ephemeral range.
• blocks: MESOS-359 "port" isolation module utilizing ephemeral selinux roles