Towards Programmable Virtual Networks

1. Genesis Project Towards Programmable Virtual Networks John Vicente Columbia University October 5, 1998 Visiting Researcher Intel Corporation O P E N S I G ‘ 9 8

2. Genesis Team • Andrew T. Campbell (Columbia U) • Michael E. Kounavis (Columbia U) • Hermann de Meer (U of Hamburg, Germany) • Kazuho Miki (Hitachi, Japan) • John Vicente (Intel Corporation, USA)

3. Observations • OPENSIG andactive networks • Can you characterize programmable networks • Networking technology • Degree of programmability • Programmable communications abstractions • Programming methodology • Architectural domain • Common ground • making networks more programmable • Enabling technology

4. Architectural Viewpoints communication & computation support Computation model Communication model Application layer Transport layer Network layer Data link layer Management plane Control plane Transport plane

5. Network programming interfaces Communication Model Programmable Network Architecture Network Programming Environment Computational Model Node Kernel Node Kernel Node interfaces Node HW Node HW Generalized Programmable Framework

6. Comparison of programmable network projects

7. Some Thoughts • Open Programmable Interfaces • Virtualization through Abstractions • Virtual Networking

8. Director’s Meeting Conference Call Simulation Network Field Sales Network President’s Video Address to Sales Team Manufacturing Network Sales & Marketing Network IT Task Force Mgmt Network Company X Physical Network Infrastructure Virtual Networking • Requirements: Group Collaboration • Isolation • Security & privacy • Connectivity - QoS • Challenge: Automation • Deployment • Configuration • Virtualization • Separation • Resource partitioning • Management

9. Network Objects Topology graph Resource requirements Profiling Refinement Object deployment Monitoring Admission control Management Spawning Visualization Resource partitioning Genesis Life Cycle Process Profiling Virtual Network Life Cycle Management Spawning

10. Is there a VN Technology Gap? • State-of-the-art • How do I setup a VN in the same time it takes to open a socket/bind or RPC? • What is the middleware glue to do this? • Where are we today in the field? • TEMPEST, NETSCRIPT and X-Bone • Genesis • The middleware: a virtual network operating system? • Profiling, spawning, managing, architecting

11. virtual network programming interface Containers T: Transport C: Control M: Management CNPE: Child NPE CNK: Child NK VS: VN Scheduler child communication model C T C CNPE CNPE C’ CNPE T T M M child computation model VS VS VS CNK CNK CNK virtual network thread Spawning virtual network architecture node thread switchlet object Parent Network Programming Environment Profiling to/from client Virtual Network Controller Virtual Network Server Node Scheduler Management Spawning Virtual Network Manager Parent Node Kernel Genesis System

12. The Genesis Project • Checkout • comet.columbia.edu/genesis • Status • Spring 1998 • Design phase • Genesis White Papers • “Programmable Broadband Kernel”, Lazar, A.A., Nov 1997. • “Spawning Network Architectures”, Lazar, Campbell, Jan 1998 • OPENARCH’99 Submission • “Toward Programmable Virtual Networking”, Campbell, De Meer,Kounavis, Miki, Vicente, October 1998.

13. genesis: /’d3en|s|s/ n. 1. The origin, or mode of formation or generation of a thing