connect • communicate • collaborate

BUILDING A BETTER NETWORK BY ASSEMBLING THE SERVICE JIGSAW:The GEMBus

Diego R. Lopez, RedIRISTNC2009, Málaga, June 2009

connect • communicate • collaborate

Yesterday, Saith We…It’s the Services, Stupid!

Big pipes are only half of the equationApplications fill the pipesApplications require servicesServices keep the NREN competitive edge

Services require managementCentral/Shared/Distributed/P2P/...

Services require developmentSoftware lifecycle

Services require deploymentCouplingComposition

connect • communicate • collaborate

Middleware and Services

Any conceivable networked service needs some basic services to runAccess controlLocationAccountingMessage passing. . .<Put your desperate need here>

If the network is going to offer such services the basic services must be part of the network core infrastructureCore middleware services, that isApplications are users as well

Seamless integration: Plug-and-play. Plug-and-be-playedFoster the role of prosumers

connect • communicate • collaborate

Core Services in GN[\d]

GN2 saw the first attempt to offer these core services as part of a multi-domain network infrastructure

Not perfect, but many lessons learnedActual services and working examplesTaking advantage of previous collaborative initiatives

GN3 is continuing this trailEnhancing those already deployed or pilotedAddressing more core servicesProviding dynamic integration and invocationConsidering SLAs as part of the processBetter development and deployment cyclesA service integration model: the multi-domain ESB

Keep the NREN competitive edge

connect • communicate • collaborate

Composable Network ServicesThe GEMBus Promise

A framework to define, discover, access, and combine network servicesFrom the infrastructure up to application elementsFederated, multi-domain ESBAble to integrate any service within the GÉANT infrastructureFlexible negotiation of service provision capabilities

Addressed toNREN staffe-Science service providersand users!!

Collaborative architectureOpen to collaboration beyond the academic communityProsumer-oriented

– Plug-and-play plus Plug-and-be-played

connect • communicate • collaborate

A Couple of Archetypal Use Cases

connect • communicate • collaborate

Building by Composition

Interface descriptions

Compositional procedures and orchestration

Standard interfaces and support for policy agreements

connect • communicate • collaborate

Service Interfaces

α-interfacesDirectly usable by applications

β-interfacesGovern systems and resources

γ-interfacesAbstract access to resources

δ-interfacesActual control over the resourcesSource: MANA Position Paper, 2009

connect • communicate • collaborate

What Service Interfaces

GEMBus will provide a set of α-interfaces

Plus the corresponding orchestration systems

Specify how β-interfaces have to be published and registered

From individual GÉANT (and external) services

γ-interfaces for core services

Those required for direct integration supportUsable by individual services

Source: MANA Position Paper, 2009

connect • communicate • collaborate

Core (Federated!) Services

DirectoryRegister new services and discover those available

MessagingOffer a common base for routing and (possibly) transforming requests and responses

LoggingCollect events and allow their correlation in a coherent manner

SecurityEstablish the rights of a certain request and/or prepare the credentials for it

OrchestrationDefine how and when individual services are called inside a composed one.

connect • communicate • collaborate

Integrating/Federating Services

Services to be provided by other GN3 activities and other projectsMost of current GÉANT (prototype) services are already well suited

AutoBAHN, cNIS, eduGAIN, PerfSONAR, …Seamless integration framework

Standard wrappers Simple registration proceduresOptional reflection interfaces

Available throughService endpoints Generic API(s)Composition portal(s)

Work needed in capabilities description and semantic information to allow composition and matching

connect • communicate • collaborate

Compositional Styles

Lightweight SOARESTComposition based on the mash-up paradigmWeb 2.0

Heavyweight SOASOAPComposition based on formal languagesSemantic Web

Bundle platformsSoftware components kept in repositoriesLoaded an instantiated by the application using themOSGi

At least, the two first will be addressed

connect • communicate • collaborate

The Timeframe

Shape it in the first yearIdentify initial use casesDefine core servicesDetermine supporting framework(s)

Make it evolve along the coming yearsRefine use casesIdentify framework enhancementsImplement and validateDemonstrate use cases

And move into service when mature

connect • communicate • collaborate

Future Internet: Changing Paradigms

Source: Joao da Silva (European Comission)ICT MobileSummit 2008 Opening Address.

connect • communicate • collaborate

In the Context of Future Internet Initiatives

In the terms used by the Future Internet publications, GEMBus will become a Service Delivery Platform

Part of the proposed Global Service Delivery PlatformIntended to be aligned with industry initiatives

IPSphere/TMF Service Delivery FrameworkGeneral SOA interoperability

Usable for:Architecture validationInitial service deploymentIntegration of initiatives and communitiesDirect experimentation

Keep the academic networking leading edge