GENI CCNIE Workshop GENI Network Stitching Architecture and

GENI CC-NIE Workshop GENI Network Stitching Architecture and Status National Science Foundation Arlington, Virginia January 7 -8, 2013 Tom Lehman University of Maryland Mid-Atlantic Crossroads

GENI Network Stitching Environment • GENI Resources are organized as independent "Aggregates" managed by independent "Aggregate Managers" GENI Aggregate network network GENI Aggregate • The intermediate "network(s)" will be of various types and capabilities • campus, regional, wide area, exchange points • some with dynamic network capabilities • some with static VLANs configured

GENI Network Stitching Environment • GENI Resources will be connected to a variety of wide area, regional, and campus infrastructures • Some of these infrastructures will have GENI AM, some will not • Stitching should be able to accommodate the unstructured placement of GENI resources in this ecosystem

Stitching Architecture Objectives • GENI Network Stitching Objective • Enable the provision of inter-aggregate network connections as part of multiaggregate slice instantiations • Stitching based on Layer 2 (Ethernet VLANs) to start • Integrate stitching into standard GENI AM API processes/functions • Leverage deployed dynamic network services/infrastructure where it helps GENI

GENI AM API Overview • Resource Specification (RSpec) • Advertisement RSpec: used by Aggregate Manager (AM) to publish their resources • Request RSpec: used by client tools to describe requested experiment resources • Manifest RSpecs: used by AM to describe instantiated experiment topology • Common XML Schemas used by all GENI AMs • GENI AM API messages • messages for credentials and RSpec exchange (advertisement, request, and manifest)

GENI Network Stitching Architecture

Stitching Topology Example • Stitching Finds a path thru ION and LONI • User Requests a Two Aggregate Topology

Existing Dynamic Network Services/Infrastructure • Dynamic Circuit Network (DCN) infrastructure available today • uses Inter Domain Controller Protocol (IDCP) • Implementation based on OSCARS and DRAGON software. • Participating networks include Internet 2 Advanced Layer 2 Network Services (AL 2 S), DYNES project deployments (approximately 40 campus, regional networks, exchange points), DOE ESnet, multiple international networks (RNP, JGN 2), and others • Other Dynamic Networks Services are expected in the future • additional deployments of DCN based services at Exchanges such as WIX and MANLAN • systems based on other technologies such as Open. Flow, Network Service Interface (NSI), others • Key objective for GENI Stitching Architecture is be able to use existing and future Dynamic Network Services

Existing Dynamic Network Services/Infrastructure • Internet 2's Advanced Layer 2 Network Services • ION Service • SDN/Open. Flow Network • Internet 2 will run a GENI AM (based on MAX AM) to "cover" ION on a trial basis to facilitate GENI Stitching • based on the MAX Regional Network GENI AM • will allow for immediate GENI stitching across ION and SDN/Open. Flow Network • Internet 2 is developing a GENI AM for the SDN/Open. Flow network. Additional services will be available once this GENI AM implementation is complete.

Stitching Architecture Components • Stitching Extension • for Advertisement, Request, and Manifest RSpecs • Stitching Topology Service • collects Advertisement RSpecs from GENI AMs • Stitching Computation Service • with workflow rule generation • Workflow Execution Stitching Library • for integration into clients such as OMNI, Flack, GENI Portal, and others • GENI AM API (v 2, v 3) Stitching Processing • v 3 has features to facilitate Stitching with negotiation

Stitching Extension for RSpecs • Mechanism for Advertisement RSpecs to define and describe inter-aggregate touch points • Advertisement RSpecs contain mostly static data, e. g. , 10 G physical inter-connect with vlans 20502099 reserved for GENI use • Mechanism for Request RSpecs and Manifest RSpecs to define slice specific stitching details • Implementation Status • Implemented by Proto. GENI AM, Insta. GENI, and MAX AM • Working with Exo. GENI and FOAM (Open. FLow) AM to implement

Topology Service • Stitching Topology Service • collects Advertisement RSpecs from all GENI AMs • allows the building of larger views (global if desired) of interconnected GENI AM space • planning to work with GEMINI project to build Stitching Topology Functionality into their UNIS based Topology Service • will also integrate topology data collection and views across the dynamic networking/perfsonar space to enable GENI stitching to better leverage these capabilities • Implementation Status • currently refining requirements and evaluating GEMINI topology service • some initial implementation work done by GEMINI project to collect AM Advertisement RSpecs

Computation Service Workflow Execution • Stitching Computation Service • uses Topology Service information to perform slice instantiation specific computations • includes a workflow rule generation function to facilitate use by clients such as OMNI • prototype under test now • Workflow Execution Stitching Library • working with OMNI developers who are building a stitching library • integration into other client tools (such as Flack and GENI Portal) once OMNI integration complete

GENI AM APIv 3 – Stitching Negotiation • GENI AM APIv 3 • changes AM interaction from "Create. Sliver" to "Allocate, Provision" paradigm (similar to the Get. Ticket, Redeem. Ticket model) • when trying to find compatible resources (in this case bandwidth and vlans) across multiple independent aggregates, there is value in being able to "negotiate" • we plan to incorporate this "negotiation" feature into future stitching operations. • Current Stitching implementations do not require this negotiation feature because we can intelligently utilize the various aggregate capabilities such as VLAN translation when sequencing Sliver requests.

GENI Networking Stitching Schedule • Stitching available for use by experimenters by GEC 16 (March 2013) • will include any aggregates with Proto. GENI, Insta. GENI, MAX, or ION Aggregate Managers • Will allow DCN networks to be used for stitching using standard GENI AM API • Possibly stitching to Exo. GENI racks will be available also • This will include initial implementations for the following • • RSpec Stitching Extension support by Aggregate Managers Stitching Computation Service Omni Stitching Library Stitching Topology Service (very basic implementation)

GENI Networking Stitching Schedule • After GEC 16 • • AMs using GENI AM APIv 3 for negotiation GENI Portal and Flack stitching integration Stitching with Exo. GENI and FOAM Aggregates Enhanced implementations of Stitching RSpecs and AM support, Computation Service, Topology Service, Stitching Library

Thank you

Stitching Extension Schema stitching aggregate path aggregatetype stitchingmode (chain|tree|both) scheduledservices negotiatedservices aggregatecapabilities* sequence of {node, port, link} global. Id sequence of {hop} node port link hop type (strict | loose) choices {aggregate, node, port, link} next. Hop technology specific details here http: //hpn. east. isi. edu/rspec/ext/stitch/0. 1/stitch-schema. xsd http: //hpn. east. isi. edu/rspec/ext/stitch/2/stitch-schema. xsd *v 0. 2 element note: these schemas will move to geni. net soon

GENI Network Stitching Architecture