Virtualized ICN (vICN) Towards a Unified Network Virtualization - - PowerPoint PPT Presentation

• M. Sardara*, L. Muscariello, J. Augé, M. Enguehard*, A. Compagno, G. Carofiglio

September 28th 2017 ACM ICN, Berlin

Towards a Unified Network Virtualization Framework for ICN Experimentation

Virtualized ICN (vICN)

*also with Telecom ParisTech

A motivating example

Emulated wireless links Real nodes with applications High-speed forwarding Independence from deployment infrastructure Flexible network model for experimentation

A unified open-source framework for: Current approaches

Research Demonstrations Production networks Easy network changes Real nodes with applications Emulated wireless links Monitoring High-speed forwarding Independence from deployment infrastructure

Simulation? Testbed? Purpose-built infra?

vICN at a glance

I want to deploy and monitor a network model I know how things work I have some infrastructure you can use vICN

User intent Infrastructure description Resource description

• Deployment integrity
• Unified API for wide range of

resources

• Deployment efficiency

Challenges

Programmability Reliability Scalability

Functional architecture

Orchestrator Resource processor Resource Database Resource factory Scheduler I want to deploy and monitor a network model I know how things work Expressive user API Thread pool Worker

• Python script or static

JSON file

cons = LxcContainer() prod = LxcContainer() link = Link(src=cons, dst=prod)

User API

cons prod tasks monitoring

Programmability Reliability

• Model reflects

deployment status

• Changes by user

mapped to tasks

Intent-based approach

Virtual bridge Cons Relay TAP TAP veth veth veth veth Emulator

{ "type": "EmulatedLteChannel", "name": "lch", "ap": "relay", "stations": [ "cons" ], "node": "server", }

Programmability Scalability

Resource factory

Resource factory I know how things work

Resource Description

Relations Lifecycle Creation Teardown Attribute updates Requirements Decomposition Event handling

metis_daemon kill –9 $(pid) metis_control

Programmability

Metis needs its node to be up and running Metis = app + log file Forwarder up triggers ICN routes recompute

Orchestrator

Reliability

?

✓

✗ ✓ ✗ ➤ ✓ ✓ ✓ Scheduler

• 1. Probe
• 2. Update state
• 3. Compute actions
• 4. Act
• 5. Update state
• 6. Return to step 3

if necessary Goal Resource processor

• Handle parallelism through thread

pool

• Ensure system correctness and

integrity

• Multiple south-bound APIs

Scheduler

Scalability

• Linux foundation open source

project

• Current catalogue of resources
• Support for coexistence of

IPv4, IPv6 and ICN (over Ethernet, UDP or TCP)

Implementation

Scalability

Linux Containers

Back to the beginning

• 104 declared resources

vs ~800 deployed

• 1500 bash commands
• Bootstrap time <2min
• See Samain et al.,

SIGCOMM 2017

• vICN is a good fit for ICN research

and development

• Active development and support
• Join us: https://wiki.fd.io/view/Vicn

Conclusion

Questions: mengueha@cisco.com