BNL Dimitrios Katramatos Sushant Sharma Dantong Yu

Size: px

Start display at page:

Download "BNL Dimitrios Katramatos Sushant Sharma Dantong Yu"

Blaise Hicks
5 years ago
Views:

Ramaprasad (UMass) UNM Nasir Ghani Feng Gu Kaile

2 USC/ISI Tom Lehman Xi Yang ESnet Chin Guok Eric Pouyoul Inder Monga Vangelis Chaniotakis Bharath Ramaprasad (UMass) UNM Nasir Ghani Feng Gu Kaile Liang BNL Dimitrios Katramatos Sushant Sharma Dantong Yu

4 Network "Service Plane" formalization Composable Network Service architecture ARCHSTONE Network Service Interface as client entry point Extensions to Topology and Provisioning Schemas to enable: multi-layer topologies multi-point topologies requests in the form of a "service-topology" vendor specific features technology specific features node level constraints MX-TCE (Multi-Dimensional Topology Computation Engine) Computation Process and Algorithms Enable a New class of Network Services referred to as "Intelligent Network Services" clients can ask the network "what is possible?" questions can ask for "topologies" instead of just point-to-point circuits

Advanced Network Service Interface "Request

Common Network Resource Description schema

Multi-Dimensional Topology Computation Element

5 Advanced Network Service Interface "Request Topology" and "Service Topology" concepts Common Network Resource Description schema Network Service Plane access point Multi-Dimensional Topology Computation Element (MX-TCE) High Performance computation with flexible application of constraints Use OSCARSv6 as base infrastructure and development environment request Network Service Requester reply Network Provider Agent OSCARSv6 MX-TCE Network Resource Description

6 Network Services Interface Network Service Plane Composite Service (S1 = S2 + S3) Composite Service (S2 = AS1 + AS2) Composite Service (S3 = AS3 + AS4) Atomic Service (AS1) Atomic Service (AS2) Atomic Service (AS3) Atomic Service (AS4) Multi-Layer Network Data Plane

Topology Service to determine resources and

Service to specify data plane connectivity

encryption) to ensure data integrity Store and

the network Measurement Service to enable

Protection Service to enable resiliency through

7 Topology Service to determine resources and orientation Resource Computation Service* to determine possible resources based on multi-dimensional constraints (*MX-TCE) Connection Service to specify data plane connectivity Security Service (e.g. encryption) to ensure data integrity Store and Forward Service to enable caching capability in the network Measurement Service to enable collection of usage data and performance stats Protection Service to enable resiliency through redundancy Monitoring Service to ensure proper support using SOPs for production service Restoration Service to facilitate recovery

8 Extensions to OSCARS v0.6 Added features for: multi-layer topologies multi-point topologies requests in the form of a "service-topology" vendor specific features technology specific features node level constraints Result is a schema "Superset" to what OSCARSv0.6 now uses schema with ARCHSTONE extensions will be backward compatible with current OSCARS operations Uses perfsonar Topology and Lookup Services

MX-TCE role in OSCARS perform basic path computation

Computation element to: answer "what is possible?

for OSCARS services Advanced multi-layer and

topologies are available next week for 3 hour

Current OSCARS Service: "Please try and reserve a 5

January 16, 2012 for 3 hour duration" Client

9 MX-TCE role in OSCARS perform basic path computation for current OSCARS service standalone Topology Computation element to: answer "what is possible?" questions for clients to subsequently make request for OSCARS services Advanced multi-layer and multi-point computations Client Application What topologies are available next week for 3 hour duration? Current OSCARS Service: "Please try and reserve a 5 Gbps VLAN circuit between A and B at 15:00 on January 16, 2012 for 3 hour duration" Client Application Here's Two MX-TCE can perform basic path computations as needed to respond to current OSCARS point-to-point VLAN service

10 java web service, C++ multi-threaded core

11 Unified API/NSI support for P2P, Multi-Point, Multi-Layer, schedule and co-scheduling requests under extended NML schema Implemented OSCARS PCE API to become swappable OSCARS module support existing OSCARS PCE capability as a single TcePCE support co-scheduling via optionalconstraint extension Multiple path and topology computation workflows kicked off based on request types: P2P, MP, MLN/MRN, cosheduling etc. and combinations support concurrent requests through multi-threading Modularized differentiated algorithm execution driven by workflows Transform computation results into provisioning friendly path object depending on path control scenarios NSI and OSCARS compliant reply messages

13 ARCHSTONE Extensions Multi-Layer Topology Representations Multi-Layer Topology Computations Multi-Layer Provisioning Layer Decisions driven by resource constraints or client requests for specific performance characteristics (i.e. low latency, low jitter, etc)

Prototype Deployment on Production Networks

being processed to provide answers to "what is

" questions that client can then use to make

project will discuss a specific use case for

start time: Wed, 08 Feb 2012 05:00:00 GMT end

bandwidth: 1 Gbps max number of path options: 3

14 Prototype Deployment on Production Networks ESnet and Internet2 Real-time reservations being processed to provide answers to "what is possible?" questions that client can then use to make requests on the operational networks VNOD project will discuss a specific use case for this Client Application coschedulerequest: start time: Wed, 08 Feb :00:00 GMT end time: Wed, 08 Feb :00:00 GMT min bandwidth: 1 Gbps max number of path options: 3 format for reply: bandwidth availability graph OSCARS MX-TCE OSCARS real-time reservations feed from production networks

15 archstone.east.isi.edu Architecture and Design Documents MX-TCE Software Extensions to OSCARS Topology and Request Schemas Example topology descriptions, service requests, service topologies (responses) ANI Testbed configuration and use OSCARSv0.6 project code.google.com/p/oscars-idc/ OSCARS ARCHSTONE Branch oscars.es.net/repos/oscars/branches/archstone/

16 Virtual Network On Demand (VNOD) is a project funded by DOE ASCR Objectives: To provide on-demand, end-to-end virtual network topologies dedicated to servicing communities of users at multiple end-sites To facilitate the creation and management of such virtual network domains - VNOD GUI based front-end To provide a platform for applying various optimization schemes with diverse objectives - Successfully schedule multiple, fixed and flexible, end-to-end data transfer requests between multiple end sites and hosts Currently working on developing technologies to address the integration and co-scheduling across Network and Middleware level resources This includes co-scheduling algorithms, protocols, and workflows which can operate in this "distributed heterogeneous multi-resource environment" Leveraging TeraPaths and ESCPS for end-host and site communications and configurations Future work will include integration with application specific workflows and systems Utilizing ARCHSTONE Intelligent Network Services as part of coscheduling workflows

17 End Site End Site End Site ESDC IDC Transit WAN Transit WAN Transit WAN End Site End Site

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

20 VNOD workflow: User requests a virtual domain setup via the front-end - Request can come from an application via the API - End-system resource availability (e.g., storage system bandwidth) can also be submitted for co-scheduling 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

21 + End Site A + Transit WAN W 1 or Transit WAN W 2 + or End Site B + +

22 (a) (b) (c) (d)

23 Available Bandwidth (Gb/s) Step 0 Request #3 Step 1 Request #2 Step 2 Request #0 Step 3 Request # Time (secs)

24 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 The architecture adopted by ARCHSTONE, OSCARS, VNOD: Centralized at the Intra-Domain level for resource management and service provisioning Distributed at the Inter-Domain level for resource management and service provisioning External topology distribution systems must limit the amount dynamic data exported (scalability and stability issues) Resource identification for real-time service provision can only be done by local domain systems Multi-domain service provision will require chain or tree mode protocols which include real-time negotiation/multi-phase commit features "Intelligent Network Services" is the key capability that needs to be developed next to support co-scheduling across network, middleware, application domains Network API needed to make service available to workflow engines OpenFlow/Software Defined Networking offers a set of network capabilities which can enhance these "Intelligent Network Services" but the "Intelligent Network Services" and co-scheduling technologies are the distinct and key value added feature set that we are addressing

Evolution of OSCARS. Chin Guok, Network Engineer ESnet Network Engineering Group. Winter 2012 Internet2 Joint Techs. Baton Rouge, LA.

Evolution of OSCARS. Chin Guok, Network Engineer ESnet Network Engineering Group. Winter 2012 Internet2 Joint Techs. Baton Rouge, LA. Evolution of OSCARS Chin Guok, Network Engineer ESnet Network Engineering Group Winter 2012 Internet2 Joint Techs Baton Rouge, LA Jan 23, 2012 Outline What was the motivation for OSCARS History of OSCARS