1 / 26

VNOD: Virtual Network On-Demand

VNOD: Virtual Network On-Demand. Dimitrios Katramatos , Dantong Yu, Sushant Sharma Brookhaven National Laboratory March 2012. VNOD Objectives. Capability t o construct on-demand, end-to-end virtual network domains service communities of users at multiple end-sites

taryn
Download Presentation

VNOD: Virtual Network On-Demand

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. VNOD: Virtual Network On-Demand DimitriosKatramatos, Dantong Yu, Sushant Sharma Brookhaven National Laboratory March 2012

  2. VNOD Objectives • Capability to construct on-demand, end-to-end virtual network domains • service communities of users at multiple end-sites • Provide a platform for applying various optimization schemes with diverse objectives • scheduling algorithms for end-to-end data transfer requests • A VNOD front-end • facilitate creation and management of virtual network domains by end users

  3. End Host End Host End Host End Host Virtual End-to-End Networking Layer End Host End Site End Site End Site ESDC Transit WAN IDC Transit WAN Transit WAN End Site End Site End Host End Host End Host

  4. VNOD Architecture Topology Service Community Membership service Topology Service distributed auxiliary services Community Membership service Service Discovery Service Discovery Monitoring Service Monitoring Service ViNet request (application requirement profile) ViNet registration and status logging ViNet registration and status logging Resource Scheduler (RS) (selects and schedules resources) Resource Scheduler (RS) (selects and schedules resources) VNOD VNOD remote RSs ViNet Controller (VNDC) (creates and manages ViNets) ViNet Controller (VNDC) (creates and manages ViNets) remote RSs remote VNDCs remote VNDCs virtual networking layer virtual end-to-end path layer remote ESCPS negotiation ESCPS ESCPS remote ESCPS Negotiation OSCARS with ARCHSTONE OSCARS with ARCHSTONE Transit WANs End-Site LAN End-Site LAN

  5. VNOD Components • Front End • Enables submission of virtual network requests • Interacts with VNODAPI for creating/activating schedules • VNOD API • Accepts input from front end • Invokes appropriate scheduling algorithm to obtain schedules • Forwards the schedules to ESCPS/TeraPaths to make reservations • Scheduling algorithms • Combines the input requests with resource availability to generate a feasible schedules • Resource availability is obtained from • End sites (via ESCPS) • WAN (via ARCHSTONE)

  6. VNOD Workflow • User requests a virtual domain setup via the front-end • The VNOD back-end: • Collects bandwidth availability information from domains involved in virtual path establishment • Interfaces with ARCHSTONE for WAN domains and TeraPaths/ESCPS for end-sites • Runs scheduling algorithm(s) • Makes appropriate reservation requests based on algorithm output by engaging ARCHSTONE and TeraPaths/ESCPS

  7. Front End

  8. Front End Workflow • Users have to provide their credentials to use VNOD (X.509 certificates)

  9. Front End Workflow User creating a virtual network request

  10. Front End Workflow User creating a virtual network request

  11. Front End Workflow History

  12. Front End Summary • Can be used by users to submit requests for virtual networks • Support user profiles • History of past network requests • Active and future virtual networks • Capability to create and save network templates • Capability to cancel any active/future reservations • Graphical representation of the selected network template on map

  13. Scheduling Algorithms

  14. Example Network SetupsSetup 1 • Multiple resource reservation requests in advance (e.g., one request corresponding to one file) • Objective is to create schedule that can finish the data transfer for all requests in minimum time possible • Assumption: Route and available bandwidth along hops is given • NP-hard problem:End-to-End network QoS via scheduling of flexible resource reservation requests, Sushant Sharma, DimitriosKatramatos, Dantong Yu, in ACM/IEEE Supercomputing 2011.

  15. Setup 1 (cont.)

  16. Example Network SetupsSetup 2 • Multiple requests traversing multiple domains • End-to-end route construction is now considered as part of the problem • Also NP-hard problem • Developed efficient algorithm (under submission to ACM HPDC 2012)

  17. Setup 2 (cont.)

  18. Setup 3(From one to N hosts) • Multiple flexible data transfer requests in advance • Every request could be for the data transfer from a single host to multiple other hosts • Need to develop and investigate the possible solution approaches

  19. Setup 4(Multiple WAN Domains) • End sites connected via multiple WAN domains • Multiple one-to-many requests • Significantly harder to generate the virtual network topology

  20. Code Development Details • Front-end • Google web toolkit • Jetty web-server • VNOD API • Web-service on a Jetty web-server • Scheduling algorithms • Exposed via an API deployed on Jetty web-server

  21. Example Use Case A file transfer tool to handle multiple files (e.g., Globus Online) • Needs to handle multiple file transfer requests • Existing tools cannot provide QoS guarantee • how many files can be transferred to meet deadlines? • transfer order? • what the underlying network can support? • Such tools can benefit from the use of VNOD • Pass file transfer list to VNOD, along with src/dst information, size, time windows • VNOD schedules the requests pursuing an optimization objective, e.g., minimum overall time • VNOD feeds the transfer schedule back to the tool and proceeds to reserve the necessary network resources

  22. Summary of Accomplishments • Identified key characteristics that will affect the final virtual network • Type of requests (fixed, flexible, hybrid) • Interface to ESCPS and OSCARS • Network setups (one domain, multiple domain, one-to-one, one-to-many, etc.) • Objective for data transfer • Front end that users can use to submit requests • Developed two scheduling algorithms for specific network setups • To accommodate multiple and flexible requests • E.g., shortest transfer time to finish all requests • One Scheduling algorithm accepted as regular paper in Supercomputing 2011 • The other under submission to ACM HPDC 2012

  23. Accomplishments (cont.) • Currently working towards implementing VNOD framework into code • Code base will be extensible to accommodate different scheduling algorithms, objectives, and heterogeneous network setups • VNOD code base • Finished implementing both end-to-end algorithms • Testing and debugging in progress • VNOD front-end and API is under development

  24. Status and Future Work • Implementation in progress • Increasingly difficult scheduling problems: • Single request/single path (TeraPaths/StorNet) • Multiple requests/single path/single WAN domain • Multiple requests/multiple paths/single WAN domain • Multiple requests/multiple paths/multiple WAN domains • Co-design with ARCHSTONE to attack scheduling complexities • Hierarchical scheduling (end-sites/WAN) • Tighter integration and interoperation

  25. Future Work (cont.) • Front End • Ability to delete network templates • Ability to reserve circuits between end-sites without TeraPaths/ESCPS (over WAN only) • Scheduling algorithms • Intelligent schedules for multiple sites • Tests on ESCPS testbed • Tests on ANI testbed

  26. Thank You

More Related