Multi-domain resso urces and service operation (GN3-JRA ti (GN3 JRA A2/SA2 A2/SA2 update) d t ) Tangui Coulouarn, Forsknings net/UNI-C 3rd E2E Workshop on Applicat tions and Services 29-30 November 2010, Prague connect • communicate • collaborate
Outline Géant Service Activity 2 deals y s with connectivity services y while the Joint Research Activ vity 2 is about Multi-domain Network Service Research. (1) Multi-domain connectivity services objective and key concepts concepts (2) Wavelength service updat ( ) g p te (3) Bandwidth on Demand se ervice update connect • communicate • collaborate
Multi-Domain Connectivit ty Services Objective Objective To enable connectivity betwe y en users located in different NREN domains as if they wer re located in the same building Offered locally by NRENs D t Deterministic service level i i ti i l l Data and control plane – QoS QoS Management – Responsibilities Responsibilities Operations and procedure es – Commissioning/ decom g mmissioning /change request g g q connect • communicate • collaborate
Services to deal with unc certainty Technologies and ad-hoc solutions alre eady exist. However, today, it takes time to establis sh multi-domain e2e connections because there is a high level of uncerta ainty on a number of parameters: Feasibility Technical parameters Security Procedures Cost sharing Administration, etc. The whole point is to provide predictab bility as well as speed in the delivery of the services. Services rather than a technologies in o order to deal with all these aspects. connect • communicate • collaborate
Services, not only tools This predictability implies agreements Tools have been developed as well but t the service is largely technology agnostic . Participants in the service ”ju ust” need to respect agreements. Provide a better service to end-users s : Faster More cost-effective For example, we (gu)estimate that t For example, we (gu)estimate that t the investment necessary to be part the investment necessary to be part of the wavelength service is already y covered after one or two international connections. connect • communicate • collaborate
GÉANT Service Area Services provided jointly by indepen ndent organizations Technological differences O Organizational differences i ti l diff Targets and challenges Joint services should hide intern nal differences Support structure (service desk , monitoring) provided by organizations connect • communicate • collaborate
connect • communicate • collaborate SLA/OLA dependencies
2- Wavelength Service A static connectivity service offering g SDH, Ethernet interfaces (OTN in the future?) Point-to-Point BW 1-40Gb/s (depending on S BW 1 40Gb/s (depending on S DP combination) DP combination) Deterministic delay behaviour – Low Jitter – Bit transparent Bit t t – Bit ordering maintained traffic isolation High availability end-to-end Typically interesting for users with l Typically interesting for users with l ong term use cases and high ong term use cases and high bandwidth demand between fixed S SDPs Large scale science projects/in nstitutions connect • communicate • collaborate
Wavelength Service Build d Participating NRENs have access t to resources of other NRENs in the service Standard POPs Interfaces/rates possible at the Interfaces/rates possible at the POPs POPs Pricing model between standar rd POPs Lead times between standard P POPs Etc. Et Allows the NRENs to make quick e stimates on the availability and price of different wavelength connections s on user requests Possible paths can be further analy ysed for the user Reduces the ad-hoc build Provides transparency and determi Provides transparency and determi nistic lead times nistic lead times connect • communicate • collaborate
connect • communicate • collaborate Wavelength Service Architecture
“Vision without implemen ntation is hallucination... hallucination ” Objective: deploy the Wavelength S Service and the BoD service in 5 selected NRENs (different for the e two services) by March 2011 However, these services are multi-d domain services: the more the merrier From the non-technical point of view w, we are working right now on different things, including the cost-s sharing model and billing mechanism. This will probably be done through This will probably be done through a clearing house. a clearing house Once again, you can use other tool s if you can respect the terms of the service. connect • communicate • collaborate
Deployment of the Wavel ength Service Service The five NRENs we are talking to a are the one currently piloting iShare: Dante (EU) DFN (Germany) GARR (Italy) GARR (Italy) SWITCH (Switzerland) PIONER/PSNC (Poland) Two other NRENs to be contac cted very soon Status: We have a principle agreement p p g t We are working on the feedbac ck we got when contacting these NRENs We need to solve a few issues: We need to solve a few issues: : : – Agree on the naming schem me – Agree on the cost sharing m model – Fill small holes in the OLAs s connect • communicate • collaborate
Bandwidth on Demand Se ervice (1) A dynamic, end-to-end Ethernet co nnectivity service Point-to-Point (between two SD DPs within the joint domain) Four tranport modes (based on n equipment capabilities) – Transport of untagged Ethe Transport of untagged Ethe ernet frames ernet frames – Transport of a specific tagg ged VLAN (with or without VLAN rewrite) – Transport of all Ethernet fra T t f ll Eth t f ames (tagged/untagged) (t d/ t d) – Transport untagged frames s to specific VLAN Bandwidth (Allocated capacity) ): 1Mbps-10Gbps (1Mbps steps), MTU: Standard, Jumbo (where e available) Path control (i.e, use/avoid dom Path control (i e use/avoid dom mains/nodes) for diverse routing mains/nodes) for diverse routing Relatively short-living circuits w with small lead time connect • communicate • collaborate
Bandwidth on Demand Se ervice (2) Allows users to get capacity when n needed between participating NREN/institutions Setup may be controlled either via – Web interface – Web service for integration with ap pplication software The service is developed in collabo oration with Internet2, Esnet, Canarie, USLHCnet for global end-to-end re USLHCnet for global end to end re ach. ach. Application areas: – LHC tier 2 communication – Guaranteed BW between Tier Guaranteed BW between Tier r 2 centres r 2 centres – Radio Astronomy – For scheduled events that sen nds data to central correlator – T l Tele medicine di i – HD, 4K, 8K Video for remote s surgery assistance – Grid/cloud computing for determin nistic BW guarantees connect • communicate • collaborate
BoD Service Architecture e End-user A End-use er B End-user C Request q Request q Request Request Bandwidth on Dema and Service (BoD) SLS E2E Joint Infrastructure and Joint Network Automatic E2E Joint Authentication Joint Service Weatherm ap Joint Accounting E2ECU supporting services offered suppo t g se ces o e ed infrastructure infrastructure path provisioning path provisioning and Authorization and Authorization Desk Desk M Monitorin it i g by the consortium NREN NREN NREN Network Service Desk OLA’s Path provisioning Monitorin ng AAI Accounting infrastructure Infrastructure, OLA’s, Supporting services and Support Teams operated services and Support Teams operated by each individual network operator (NREN or Dante) Infrastru ucture Support Team(s) support s service connect • communicate • collaborate
Deployment of the BoD S Service GRNET, PSNC/PIONIER, DANTE, JANET are very keen in participating in the pilot. We are discussing with another NR We are discussing with another NR REN and consider going out to 2 other REN and consider going out to 2 other NRENs. Currently we (or rather the NRENs Currently, we (or rather the NRENs s) are working on the concrete set-up s) are working on the concrete set up in their network and testing. I In an initial phase, the service is co i iti l h th i i onceived mostly for NOC users. i d tl f NOC But in the longer term, we want to b g bring the service to end-users. g connect • communicate • collaborate
Last mile issue: JRA2 JRA2 is currently investigating last mile solutions to bring the service to the lab (among other areas for rese earch). For example: For example: Lambda Station TeraPaths gTBN TBN Phoebus VRF This is an example of the collaborat tion and division of work between JRA2 and SA2 in Géant JRA2 and SA2 in Géant connect • communicate • collaborate
Update on tools for the B BoD Service – AutoBAHN (1) AutoBAHN (1) AutoBAHN is one of the tools devel loped by GÉANT which can be used (along with PerfSONAR, EduGAIN, , Cnis) AutoBahn Automated Bandwidth A AutoBahn Automated Bandwidth A llocation across Heterogeneous llocation across Heterogeneous Networks. It is a Bandwidth on Dem mand system dedicated to reserve resources in heterogeneous, multi-d domain environments, allowing immediate and advance circuit rese ervations. Characteristic of AutoBAHN: it was built for a multi-domain configuration connect • communicate • collaborate
Recommend
More recommend
