MPlane: project and architecture The need of an intelligent measurement plane for the internet FIRE-GENI workshop May 5-6, Cambridge USA Disclaimer: I’m.

mPlane: project and architecture

The need of an intelligent measurement plane for the internet

FIRE-GENI workshopMay 5-6, Cambridge USA

Disclaimer: I’m not a testbed guy!I’m a measurement guy

Marco MelliaPolitecnico di Torino

for testbeds integration

2

A complicated technology…

The internet is a key infrastructure where different technologies are combined to offer a plethora of services. It’s horribly complicated.

We sorely miss the technology to understand what is happening in the network and to optimize its performance and utilization.

3

Who we are

Consortium

4

mPlane architecture

5

6

7

8

Sounds straightforwardBut the evil is in the details

9

Key insights

Three years isn’t enough time to rebuild all the tools we’ll need we must support easy integration of existing probes and repositories.

The core of the architecture is the mPlane protocol, anything which implements it a component... ...which can advertise its capabilities ...perform measurements or analyses given

specifications thereof ...and return or indirectly export results therefrom

Measurements completely defined by the types of data they produce and parameters they require.

10

Architecture Overview

14

Schema-level interoperability

Network measurement produces rows in databases.

Network data analysis munges rows in databases into other rows in databases.

The key to interoperability is ensuring that columns with the same name have the same meaning.

Operations of common measurement tools can be completely described by the schemas involved.

16

Example Capability: ping

capability: measureparameters: start.ms: now...+inf end.ms: now...+inf source.ip4: 10.2.3.4 destination.ip4: * period.s: 1...60results: - delay.twoway.icmp.ms.min - delay.twoway.icmp.ms.mean - delay.twoway.icmp.ms.max

17

Example Specification: ping

specification: measureparameters: start.ms: 2014-01-20 09:25:00 end.ms: 2014-01-20 09:26:00 source.ip4: 10.2.3.4 destination.ip4: 10.4.5.6 period.s: 1results: - delay.twoway.icmp.ms.min - delay.twoway.icmp.ms.mean - delay.twoway.icmp.ms.max

18

Example Result: ping

result: measureparameters: start.ms: 2014-01-20 09:25:01.135 end.ms: 2014-01-20 09:26:01.136 source.ip4: 10.2.3.4 destination.ip4: 10.4.5.6 period.s: 1results: - delay.twoway.icmp.ms.min - delay.twoway.icmp.ms.mean - delay.twoway.icmp.ms.maxresultvalues: - - 39 - 44 - 73

19

mPlane protocol for testbed

We build testbeds … to collect measurements Probes

… and we need algorithms to post-process results (Intelligent) repository

So why not extending the mPlane approach for testbed in general? [Submitted a FIRE proposal for a 3G/4G Eu

testbed]

CoNEXT TPC workshopBarcellona, 5/9/13

20

Questions

How to share resources? ISPa can run experiments from ISPb?

Supervisor(ISPa) talks to Supervisor(ISPb) Federated solutions?

How to share results? Value is in the data…

We have 10GB of data per day… (from our passive probes How to access to this data? What to do with this data?

CoNEXT TPC workshopBarcellona, 5/9/13

23