Multi Domain Service Architecture for Heterogonous Networks A view from GÉANT 3 - SA2: Task 1 Brian Bach Mortensen, NORDUnet 2nd TERENA E2E Workshop on Provisioning E2E services & On-demand Infrastructure Services Provisioning WorkshopSeptember Amsterdam December - 2009
Outline OPNs, BoD and multi domain challenges Management of Connectivity Service in GN3 Service Access Hierachy Joined Service Catalogue Service Architecture SLA/OLA dependencies Wavelength/OPN service definitions BoD service Definition Examples from other NRENs General thoughts on BoD services Q&A
LHC OPN based on multi-domain E2E links Figure is modification of work from R. Sabatino
Challenges in OPNs and λ s Services provided jointly by independent organizations Technological differences Organizational differences Targets and challenges Joint service should hide internal differences Support structure (service desk, monitoring) provided by many organizations Figure is from A. Sevasti, TNC 2008
Bandwidth-on-Demand Services in Europe Build a joint BoD service in Europe Not only by DANTE, But also with NRENs AutoBAHN tool enables automated technology stitching Figures are from A. Sevasti, TNC 2008
Motivation: Overall management of GN3 services DANTE and NRENs offer joint network connectivity services such as Static OPN service based on dedicated wavelengths Currently aiming for BoD service (e.g. interesting for e-vlbi project) Open issues How to manage the overall offer of joint services by DANTE and NRENs Which services are really made available as production services? What kinds of information are needed for a service? How can a service template look like? How to organize collaboration in the service provisioning? How to address joint processes (seems even more challenging than technological issues)?
Service Access Hierachy End user End user End user End user End user End user End user Educ./ Research Insti. Regional network Educ./ Research Insti. Educ./ Research Insti. NRENs NRENs External partners Joined Service Provider - Common Service Catalogue GÉANT
Sorry for spamming you.. Customers and service dependencies Customer A Requirements Requirements Customer B Requirements Requirements Customer C Requirements Requirements Service desc. IP Service desc. wavelength Service desc. BoD IP SLA Wavelength SLA BoD SLA I-SHARe (tool) perfsonar (tool) Network Interfaces (resource) Network Protocols (resource) Joined provider infrastructure
Sorry for spamming you.. Infrastructure and supporting services ishare (tool) perfsonar (tool) Network Interfaces (resource) Network Protocols (resource) Joined provider infrastructure OLA OLA Supporting Service Supporting Service Supporting Service Supporting Service OLA OLA Federated Provider Internal groups FederatedS upport Team FederatedS upport Team Support TeamSupport Team Individual NRENs or DANTE
SLA/OLA dependencies
Where are the networks?
Wavelength service and OPN service Team have started working on defining these services Range is from single multi-domain E2E links up to complete OPN solutions for projects Joint offer of NRENs and DANTE Contrast to (single domain) Geant Plus and Lambda Streamline current individual solutions (LHC OPN) to systematic service offer
BoD service Provide a layer 2 ethernet service for customers with highly dynamic bandwidth demand Documented service architecture that ensures scalability across campuses/research institutions, NRENs/GN3 and international Simple end user interface with production level quality code Clear description of what is needed and what is required To receive the service (Customers) To provide the service (Unified Provider)
BoD service examples National LampdaRail offers dynamic ethernet service (FrameNet)
BoD service examples
BoD service examples
BoD service examples
BoD service examples
BoD service examples SURFnet offers dynamic ligthpath service since end of 2008 Internet 2 ION service launched this year Sinet3 offers BoD in Japan (www.sinet.ad.jp) Surveys from GÉANT3 SA2T1 shows that a significant amount of european NRENs are running or planning experiments with BoD Other international networks may offer the same service
BoD service thoughts Shall BW guarantees be strict or not? Too hard QoS requirements may make it hard to provisioning the paths E.g. circuit or packet based? Possibly narrowing the underlying transport technology if too many options or too hard constraints Scheduled BW allocations Blocks a resource even if it may be canceled before actual use Incite the users to terminate line when not used or when known it wont be!
BoD service thoughts 2 Coorporation on global scale increases the potential end users and applications without significant cost additions Requires that the service have well defined trust models A trust B, B trust C A trust C Well defined/standardised boundaries between networks SLA and technicalities Hide the complexity for users! Needs to be brain dead easy to use!!
Q&A Thank you Additional questions may be send to brian@nordu.net
Who are SA2 SA2 - Activity Leader Ann Harding - Switch Task 1 Service Development (12.8 FTE) Task 2 Operations & Co-ordination (16.8 FTE) Task 4 Security (20.8 FTE) Task 3 Performance & Monitoring Tools (52.2 FTE) Task 5 Workflow Tools (50 FTE) QuickTime and a TIFF (Uncompressed) decompressor are needed to see this picture. QuickTime and a TIFF (Uncompressed) decompressor are needed to see this picture. QuickTime and a TIFF (Uncompressed) decompressor are needed to see this picture. Brian Bach Mortensen NORDUnet Emma Apted DANTE Maurizio Molina DANTE Szymon Trocha PSNC Marcin Wolski PSNC
Business Cases process flow User requirements Business Objective /Benefits Value Proposition Cost Risk Commitments Success factors Propose to PMT/PB dispose Develop Yearly Portfolio Review Deployment