Multi-domain resso urces and service operation (GN3-JRA ti (GN3 - - PowerPoint PPT Presentation

Multi-domain resso ti (GN3 JRA

• peration (GN3-JRA

Tangui Coulouarn, Forsknings 3rd E2E Workshop on Applicat

29-30 November 2010, Prague

urces and service A2/SA2 d t ) A2/SA2 update)

net/UNI-C tions and Services

connect • communicate • collaborate

Outline

Géant Service Activity 2 deals y while the Joint Research Activ Network Service Research. (1) Multi-domain connectivity concepts concepts (2) Wavelength service updat ( ) g p (3) Bandwidth on Demand se s with connectivity services y vity 2 is about Multi-domain services objective and key te ervice update

connect • communicate • collaborate

Multi-Domain Connectivit Objective Objective

To enable connectivity betwe y NREN domains as if they wer Offered locally by NRENs D t i i ti i l l Deterministic service level Data and control plane QoS

– QoS

Management

– Responsibilities

Responsibilities Operations and procedure

– Commissioning/ decom

g

ty Services

en users located in different re located in the same building es mmissioning /change request

connect • communicate • collaborate

g g q

Services to deal with unc

Technologies and ad-hoc solutions alre However, today, it takes time to establis because there is a high level of uncerta Feasibility Technical parameters Security Procedures Cost sharing Administration, etc. The whole point is to provide predictab the services. Services rather than a technologies in o

certainty

eady exist. sh multi-domain e2e connections ainty on a number of parameters: bility as well as speed in the delivery of

• rder to deal with all these aspects.

connect • communicate • collaborate

Services, not only tools

This predictability implies agreements Tools have been developed as well but

• agnostic. Participants in the service ”ju

Provide a better service to end-users Faster More cost-effective

For example, we (gu)estimate that t For example, we (gu)estimate that t

• f the wavelength service is already

international connections.

t the service is largely technology ust” need to respect agreements. s:

the investment necessary to be part the investment necessary to be part y covered after one or two

connect • communicate • collaborate

GÉANT Service Area

Services provided jointly by indepen Technological differences O i ti l diff Organizational differences Targets and challenges Joint services should hide intern Support structure (service desk

• rganizations

ndent organizations nal differences , monitoring) provided by

connect • communicate • collaborate

SLA/OLA dependencies

connect • communicate • collaborate

2- Wavelength Service

A static connectivity service offering the future?) Point-to-Point BW 1-40Gb/s (depending on S BW 1 40Gb/s (depending on S Deterministic delay behaviour

– Low Jitter

Bit t t

– Bit transparent – Bit ordering maintained

traffic isolation High availability end-to-end Typically interesting for users with l Typically interesting for users with l bandwidth demand between fixed S Large scale science projects/in g SDH, Ethernet interfaces (OTN in DP combination) DP combination)

• ng term use cases and high
• ng term use cases and high

SDPs nstitutions

connect • communicate • collaborate

Wavelength Service Build

Participating NRENs have access t service Standard POPs Interfaces/rates possible at the Interfaces/rates possible at the Pricing model between standar Lead times between standard P Et Etc. Allows the NRENs to make quick e

• f different wavelength connections

Possible paths can be further analy Reduces the ad-hoc build Provides transparency and determi Provides transparency and determi

d

to resources of other NRENs in the POPs POPs rd POPs POPs stimates on the availability and price s on user requests ysed for the user nistic lead times nistic lead times

connect • communicate • collaborate

Wavelength Service Architecture

connect • communicate • collaborate

“Vision without implemen hallucination ” hallucination...

Objective: deploy the Wavelength S selected NRENs (different for the However, these services are multi-d merrier From the non-technical point of view different things, including the cost-s This will probably be done through This will probably be done through Once again, you can use other tool service.

ntation is

Service and the BoD service in 5 e two services) by March 2011 domain services: the more the w, we are working right now on sharing model and billing mechanism. a clearing house a clearing house. s if you can respect the terms of the

connect • communicate • collaborate

Deployment of the Wavel Service Service

The five NRENs we are talking to a Dante (EU) DFN (Germany) GARR (Italy) GARR (Italy) SWITCH (Switzerland) PIONER/PSNC (Poland) Two other NRENs to be contac Status: We have a principle agreement p p g We are working on the feedbac NRENs We need to solve a few issues: We need to solve a few issues:

– Agree on the naming schem – Agree on the cost sharing m – Fill small holes in the OLAs

ength

are the one currently piloting iShare: cted very soon t ck we got when contacting these : : me model

connect • communicate • collaborate

s

Bandwidth on Demand Se

A dynamic, end-to-end Ethernet co Point-to-Point (between two SD Four tranport modes (based on

– Transport of untagged Ethe

Transport of untagged Ethe

– Transport of a specific tagg

rewrite) T t f ll Eth t f

– Transport of all Ethernet fra – Transport untagged frames

Bandwidth (Allocated capacity) MTU: Standard, Jumbo (where Path control (i e use/avoid dom Path control (i.e, use/avoid dom Relatively short-living circuits w

ervice (1)

nnectivity service DPs within the joint domain) n equipment capabilities) ernet frames ernet frames ged VLAN (with or without VLAN (t d/ t d) ames (tagged/untagged) s to specific VLAN ): 1Mbps-10Gbps (1Mbps steps), e available) mains/nodes) for diverse routing mains/nodes) for diverse routing with small lead time

connect • communicate • collaborate

Bandwidth on Demand Se

Allows users to get capacity when n NREN/institutions Setup may be controlled either via

–

Web interface

–

Web service for integration with ap

The service is developed in collabo USLHCnet for global end-to-end re USLHCnet for global end to end re Application areas:

–

LHC tier 2 communication Guaranteed BW between Tier

– Guaranteed BW between Tier –

Radio Astronomy

– For scheduled events that sen

T l di i

–

Tele medicine

– HD, 4K, 8K Video for remote s –

Grid/cloud computing for determin

ervice (2)

needed between participating

pplication software

• ration with Internet2, Esnet, Canarie,

ach. ach.

r 2 centres r 2 centres nds data to central correlator surgery assistance nistic BW guarantees

connect • communicate • collaborate

BoD Service Architecture

Request End-user A End-use Request Bandwidth on Dema Request q Joint Infrastructure and supporting services offered Joint Network infrastructure Automatic E2E path provisioning E2E Weatherm M it i suppo t g se ces o e ed by the consortium infrastructure path provisioning Monitorin

NREN NREN

Infrastructure, OLA’s, Supporting services and Support Teams operated Monitorin Network infrastructure Path provisioning

NREN

services and Support Teams operated by each individual network operator (NREN or Dante) Infrastru support s

e

er B End-user C Request and Service (BoD) SLS q ap Joint Authentication and Authorization Joint Accounting Joint Service Desk E2ECU g and Authorization Desk Accounting OLA’s ng AAI Service Desk ucture service Support Team(s)

connect • communicate • collaborate

Deployment of the BoD S

GRNET, PSNC/PIONIER, DANTE, in the pilot. We are discussing with another NR We are discussing with another NR NRENs. Currently we (or rather the NRENs Currently, we (or rather the NRENs in their network and testing. I i iti l h th i i In an initial phase, the service is co But in the longer term, we want to b g

Service

JANET are very keen in participating REN and consider going out to 2 other REN and consider going out to 2 other s) are working on the concrete set up s) are working on the concrete set-up i d tl f NOC

• nceived mostly for NOC users.

bring the service to end-users. g

connect • communicate • collaborate

Last mile issue: JRA2

JRA2 is currently investigating last the lab (among other areas for rese For example: For example: Lambda Station TeraPaths TBN gTBN Phoebus VRF This is an example of the collaborat JRA2 and SA2 in Géant JRA2 and SA2 in Géant mile solutions to bring the service to earch). tion and division of work between

connect • communicate • collaborate

Update on tools for the B AutoBAHN (1) AutoBAHN (1)

AutoBAHN is one of the tools devel (along with PerfSONAR, EduGAIN, AutoBahn Automated Bandwidth A AutoBahn Automated Bandwidth A

• Networks. It is a Bandwidth on Dem

resources in heterogeneous, multi-d immediate and advance circuit rese Characteristic of AutoBAHN: it was

BoD Service –

loped by GÉANT which can be used , Cnis) llocation across Heterogeneous llocation across Heterogeneous mand system dedicated to reserve domain environments, allowing ervations. built for a multi-domain configuration

connect • communicate • collaborate

AutoBAHN (2)

Single AutoBAHN instance deploye software components: InterDomainManager (IDM) Domain Manager (DM) Domain Manager (DM) Technology Proxy (TP) Th f ll i t d t The following components need to AutoBAHN environment: perfSONAR Lookup Service Web GUI - graphical user interf You can see an online demo here: You can see an online demo here: https://forge.geant.net/forge/display ed in a domain consists of three main b d l d f th h l be deployed once for the whole face y/autobahn/On-line+Demo

connect • communicate • collaborate

AutoBAHN (3)

connect • communicate • collaborate

Roadmap

BoD service devel

Functionality ETS mode untagged to untagged ETS mode tagged to untagged ETS mode tagged to tagged ETS mode tagged to tagged with VID swapping Path MTU selection User policies for path parameters (eg. requestting path MTU, service duration min/max etc) Transit domain policies for allowed traffic from source/destination domains Transit domain policies for number of allowed transit connection and resources in time period E2E path parameters/status presentation (basing on requested parameters) Additional estimated QoS parameters/status presentation for the E2E path (for example latency, calcula

• f availability, frame loss rate)

Billing/statistics/accounting portal for the end users Billing/statistics/accounting portal for the end users Connectivity Fault Management support status Minimum Latency Path selection Service weathermap Path restoration/switchower (checkbox) Prefered transit domains selection Authorisation rules (defining user rights to make reservation) Path constrains priority selection Advanced path constrains (for example reservation time/period vs. E2E path capacity) mandatory functionality

• ptional functionality

to be discussed

* not in automatic provisioning path tool (A ** implemented as static link parameter ma

• pment roadmap

2010 2011 2012 2013 Q3 Q4 Q1 Q2 Q3 Q4 Q1 Q2 Q3 Q4 Q1 Q2 Q3 Q4 SA2‐T5

• SA2‐T5
• *

SA2‐T5

• SA2‐T5
• *

SA2‐T5

• SA2‐T5/SA2‐T1
• SA2‐T5/SA2‐T1
• SA2‐T5/SA2‐T1
• ation

SA2‐T5/JRA

• SA2‐T5/JRA/?
• SA2 T5/JRA/?
• SA2‐T5/JRA
• SA2‐T5
• **

SA2‐T3

• SA2‐T5
• SA2‐T5
• SA2‐T5
• SA2‐T5
• connect • communicate • collaborate

AutoBahn) roadmap apping

Q&A Thank

Additional questions may be send

k you!

to: tangui.coulouarn@uni-c.dk

connect • communicate • collaborate