Download Genesis: Towards Programmable Virtual Networks

Survey
yes no Was this document useful for you?
   Thank you for your participation!

* Your assessment is very important for improving the workof artificial intelligence, which forms the content of this project

Document related concepts
no text concepts found
Transcript
Genesis Project
Towards Programmable Virtual Networks
John Vicente
Columbia University
October 5, 1998
Visiting Researcher
Intel Corporation
OPENSIG‘98
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)
Observations

OPENSIG and active 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
Architectural Viewpoints
communication & computation support
Transport layer
Network layer
Data link layer
Management plane
Control plane
Transport plane
Application layer
Generalized Programmable Framework
Communication
Model
Programmable Network Architecture
Computational
Model
Network Programming Environment
Node
Kernel
Node
Kernel
Node HW
Node HW
Network
programming
interfaces
Node
interfaces
Comparison of programmable network projects
Some Thoughts

Open Programmable Interfaces

Virtualization through Abstractions

Virtual Networking
Virtual
Networking

Requirements:
Group Collaboration
Director’s Meeting
Conference Call
Simulation
Network
Field Sales
Network
– Isolation
– Security & privacy
– Connectivity - QoS

Challenge:
Automation
– Deployment
– Configuration
– Virtualization
President’s
Video Address
to Sales Team
Manufacturing Network
Sales & Marketing
Network
IT Task Force
Mgmt Network
• Separation
• Resource
partitioning
– Management
Company X
Physical Network
Infrastructure
Genesis Life Cycle Process
Network Objects
Topology graph
Resource requirements
Profiling
Refinement
Monitoring
Visualization
Virtual Network
Life Cycle
Management
Spawning
Object deployment
Admission control
Resource partitioning
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
Genesis System
Containers
T: Transport
C: Control
M: Management
CNPE: Child NPE
CNK: Child NK
VS: VN Scheduler
child
communication
model
child
computation
model
Spawning
virtual network
architecture
Profiling
T
C
M
T
virtual network
programming
interface
C
C’
T
CNPE
CNPE
CNPE
VS
VS
VS
CNK
CNK
CNK
virtual network
thread
node thread
Parent Network Programming Environment
to/from client
Management
Spawning
Virtual
Network
Server
M
Virtual Network
Controller
Node Scheduler
Virtual Network
Manager
Parent Node Kernel
switchlet
object
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.
genesis: /’d3en|s|s/ n. 1. The origin, or mode
of formation or generation of a thing
Related documents