1 / 30

Spawning Networks

COMET Group Columbia University. Spawning Networks. People. Andrew T. Campbell (Columbia) Herman G.De Meer (Univ. of Hamburg) Michael E.Kounavis (Columbia) Kazuho Miki (Hitachi) John Vicente (Intel) Daniel Villela (Columbia). Motivation. deployment of network architectures:

peterilee
Télécharger la présentation

Spawning Networks

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. COMET Group Columbia University Spawning Networks

  2. People • Andrew T. Campbell (Columbia) • Herman G.De Meer (Univ. of Hamburg) • Michael E.Kounavis (Columbia) • Kazuho Miki (Hitachi) • John Vicente (Intel) • Daniel Villela (Columbia)

  3. Motivation • deployment of network architectures: • ad-hoc in nature and costly • no systematic exploration of the “network design space” • virtual networking • isolation and privacy • quality of service support

  4. State of the Art • open programmable interfaces • OPENSIG, IEEE P1520 • deployment at runtime • DARPA Active Networks • multiple control architectures • Multiservice Switching Forum

  5. Spawning Networks • new class of programmable networks • capable of creating new architectures on-the-fly • automate a “life cycle” process • enabling technology: • the Genesis kernel

  6. child virtual network differential service virtual network cellular IP virtual network physical network

  7. Life Cycle • profiling • Captures the “blueprint” of the virtual network • spawning • allocates resources, sets up topology, binds transport, control, and management • management • architecting • resource management

  8. Design Principles • separation • transparency of operation between parent and child networks • nesting • child networks, can be parent of their own children • inheritance • architectural components • provisioning characteristics

  9. network architecture #2 child virtual network kernel metabus #2 network architecture #1 life cycle services binding interface base parent virtual network kernel programming environment metabus #1 transport environment Genesis Kernel spawning

  10. Transport Environment • consists of programmable virtual nodes called “routelets” • routelets : • interconnected via “virtual links” • share parent routelet resources • may coexist in the same physical node • virtual links : • abstractions of resource partitions

  11. L1, L2, and L3 partitioning • L1: WDM • L2: Switchlets (Cambridge Univ.) • L3: Routlets (Columbia Univ.)

  12. spawning controller datapath controller allocation controller composition controller Routelet Architecture binding interface base metabus routelet state control unit forwarding engine output port input port

  13. virtual network demultiplexor output port forwarding engine capacity arbitrator input port virtual network classifier local routing control virtual network traffic control local traffic control Nested Routelets forwarding engine output port input port local routing control local traffic control packet packet

  14. Programming Environment • spawning networks • program their own routelets • deploy network architectures • metabus • per-virtual network software bus for object interaction • partitions distributed object space • binding interface base • supports open routelet control

  15. GUI spawning life cycle server resource management profiling architecting virtual network architecture transport Spawner Architect life cycle services routing QOS control Profiler Maestro management VirtualSpawningController VirtualRouteletState VirtualCompositionController VirtualAllocationController VirtualDatapathController binding interface base metabus

  16. Life Cycle Services • support profiling spawning and management of virtual networks • inherited during the spawning process • programmable upon the binding interface base and metabus

  17. Profiling • topology • specified in terms of a set of parent nodes and links • architectural elements • specified in terms of routelet components, and communication protocols • resource requirements • required bandwidth • capacity classes

  18. Profiling System GUI profiling life cycle server resource management spawning architecting profile database profile database profiler verifiers policy server

  19. Spawning • spawning services • spawner, constructors, component storage • spawning process: • creates child routelets • binds them together through virtual links • creates a metabus • deploys life cycle services • deploys a network architecture

  20. spawning controller datapath controller allocation controller composition controller arbitrator classifier GUI profiling life cycle server resource management spawning architecting spawner constructor BIB metabus routelet state output port forwarding engine input port CPU

  21. GUI profiling life cycle server resource management spawning architecting spawner constructor routelet state BIB metabus routelet state spawning controller datapath controller composition controller allocation controller arbitrator classifier output port CPU forwarding engine input port CPU

  22. GUI profiling life cycle server resource management spawning architecting spawner constructor routelet state BIB metabus routelet state spawning controller datapath controller composition controller allocation controller arbitrator classifier output port CPU forwarding engine input port CPU

  23. GUI profiling life cycle server resource management spawning architecting spawner constructor BIB metabus spawning controller composition controller allocation controller routelet state spawning controller datapath controller composition controller allocation controller arbitrator classifier output port forwarding engine input port CPU routelet state CPU

  24. output port routelet state spawning controller datapath controller composition controller allocation controller forwarding engine input port GUI profiling life cycle server resource management spawning architecting spawner constructor BIB metabus routelet state spawning controller datapath controller composition controller allocation controller output port CPU forwarding engine input port arbitrator classifier CPU

  25. GUI profiling life cycle server resource management life cycle services spawning architecting spawner BIB metabus constructor routelet state BIB metabus spawning controller datapath controller composition controller allocation controller routelet state output port forwarding engine spawning controller datapath controller composition controller allocation controller input port output port CPU forwarding engine input port arbitrator classifier CPU

  26. GUI profiling child network architecture life cycle server resource management spawning architecting spawner constructor routelet state BIB metabus spawning controller datapath controller composition controller allocation controller routelet state output port forwarding engine spawning controller datapath controller composition controller allocation controller input port output port CPU forwarding engine input port arbitrator classifier CPU life cycle services BIB metabus

  27. Virtual Network Management • Architecting • virtual networks can be visualized • services can added modified or deleted • Resource Management • distributed auctioning process • slow timescale • capacity classes • as general “resource pipes” • inheritance and autonomous control

  28. Management System spawner maestro resource management interfaces admission control interfaces auctioneers monitor delegate VirtualDatapathController BIB metabus arbitrator

  29. Related Word • Tempest Project • Multiple Control Architectures • Netscript Project • Virtual Active Networks • X-Bone • Automates the deployment of IP overlays • Supranet • Secure collaborative environments

  30. Conclusion • Spawning Networks: • automate the life cycle process • result in better network customization • enable the deployment of new network services • genesis:/’d3en|s|s/ n. 1. The origin, or mode of formation or generation of a thing

More Related