GT3 Architecture and Functionality. Core OGSI Implementation Security Services System-Level Services...

GT3 Architecture and Functionality

GT3Architecture and Functionality

CoreOGSI ImplementationSecurity ServicesSystem-Level ServicesContainerHosting Environment

Base ServicesResource ManagementInformation ServicesData Management

User-Defined ServicesGrid Service Development Framework

Future Directions

GT3 Distribution

GT2.4 Components RLS???

GT-OGSAGrid Service

Infrastructure

The focus of this presentation

GT Grid Service Infrastructure

Security Infrastructure

System-Level Services

Base Services

User-Defined Services

Grid Service Container

Hosting Environment

Web Service Engine

OGSI Spec Implementation

GT3 Core

The Specification Defines how Entities can Create, Discover and Interact with a Grid Service

Servicedata

element

Servicedata

element

Servicedata

element

Service Implementation

GridService(required) … other interfaces …

(optional) Optional:- Service creation- Notification- Registration- Service Groups

+ application-specific interfaces

Required:- Introspection (service data)- Explicit destruction- Soft-state lifetime

GT3 Core: OGSI Specification

GT3 Core: OGSI ImplementationGT3 includes a set of primitives that fully

implement the interfaces and behaviors defined in the latest version of the OGSI Specification

The OGSI Specification defines a protocol - GT3 provides a programming model for that protocol

GT3 Core: Implementation of the GridService portType: GridServiceImpl and PersistentGridServiceImpldestroy()setServiceData()findServiceData()requestTerminationAfter()requestTerminationBefore()addOperationProvider()(See docs for complete set of methods)

Implementationof the OGSI Spec

<paramter name=“operationProviders” value=“<className>”>

Additionalfunctionality can beadded to aGrid Service usingOperationProviders

Deployment descriptor

Write service-specificlogic that alsoimplements the GT3 OperationProvider interface


Combine with one of thetwo GT3 implementationsof base GridServicefunctionality:GridServiceImpl orPersistentGridServiceImpl



An OGSI-Compliant

grid service

An OGSI-Compliant

grid service

OperationProviders are configured at deployment time or added at runtime



OPs can be designed as atomic bits of functionality to facilitate reuse

The OP approach eases the task of bringing legacy code into OGSI-Compliance

OPs allow Grid Services to be formed dynamically (in contrast to the inheritance approach)

NotificationSourceProvider

HandleResolverProvider

ServiceGroupRegistrationProvider

ServiceGroupProvider

FactoryProvider

Our NotificationSourceProvider implementation allows any Grid Service to become a sender of notification messages

A subscribe request on a NotificationSource triggers the creation of a NotificationSubscription service

A NotificationSink can receive notification msgs from NotificationSources. Sinks are not required to implement the GridService portType

Notifications can be set on SDEs

GT3 Core: OGSI Specification (cont.)

Factory portTypeFactories create servicesFactories are typically persistent

servicesFactory is an optional OGSI interface

(Grid Services can also be instantiated by other mechanisms)

This slide will become more GT3 factory implementation specific


Service group portTypesA ServiceGroup is a grid service that maintains

information about a group of other grid servicesThe classic registry model can be implemented with the

ServiceGroup portTypesA grid service can belong to more than one ServiceGroupMembers of a ServiceGroup can be heterogenous or

homogenousEach entry in a service group can be represented as its

own serviceService group portTypes are optional OGSI interfaces

This slide will become more GT3 servicegroup implementation specific


HandleResolver portTypeDefines a means for resolving a GSH (Grid Service

Handle) to a GSR (Grid Service Reference)A GSH points to a Grid Service

(GT3 uses a hostname-based GSH scheme)A GSR specifies how to communicate with the Grid Service

(GT3 currently supports SOAP over HTTP, so GSRs are in WSDL format)

Includes 0 or more Grid Service Handles (GSHs)Includes 0 or more Grid Service References (GSRs)

Service locator

This slide will become more GT3 handleResolver implementation specific

A Service Creation Scenario*Registry

* All scenarios in this presentation are offered as examples and are not prescriptive

1. From aknown registry,the clientdiscovers afactory byquerying theservice data of theregistry

Client

Client

Registry

2. The client callsthe createServiceoperation on thefactory

Factory


A Service Creation Scenario (cont.)

Client

Registry Factory

Service

3. The factorycreates aservice


2. The client callsthe createServiceoperation on thefactory


Client

Registry Factory

Service

4. The factoryreturns a locator tothe newly createdservice


2. The client callsthe createServiceoperation on thefactory 3. The

factorycreates aservice


Client

Registry Factory

Service5. The client and service interact


2. The client callsthe createServiceoperation on thefactory 3. The

factorycreates aservice 4. The factory

returns a locator tothe newly createdservice


Client

A Service Group Scenario

a yeepservice

a murp service

a bloopservice

1. The client callsthe add operation, providing a locatorto the bloop service as input

ServiceGroup

RegistrationI plan to rework this scenario to make the services registerthemselves rather than the client registering them. Theservices will then perform lifetime mgmt on the service groupentries

Client

a yeepservice

a murp service

a bloopservice bloop SG

Entry

1. The client callsthe add operation, providing a locatorto the bloop service as input

2. The ServiceGroup creates an SG Entry.The purposeof the Entryis to representthe bloopservice insidethe collection

A Service Group Scenario (cont.)

ServiceGroup


Client

a yeepservice

a murp service

a bloopservice

3. Entries for themurp and yeepservices are addedin the same manner

bloop SG Entry

murp SG Entry

yeep SG Entry


ServiceGroup


Client

a yeepservice

a murp service

a bloopservice

murp SG Entry

yeep SG Entry

The lifetime on the bloopSG Entry terminates


ServiceGroup


Client

ServiceGroup

Registration

a yeepservice

a bloopservice

murp SG Entry

yeep SG Entry

The murpserviceterminates


I plan to rework this scenario to make the services registerthemselves rather than the client registering them. Theservices will then perform lifetime mgmt on the service groupentries

NotificationSink

A Notification Scenario

1. NotificationSink callsthe subscribe operationon NotificationSource

NotificationSource

NotificationSink

NotificationSource

NotificationSubscription

2.NotificationSource creates a subscription service


A Notification Scenario (cont.)

NotificationSink

NotificationSource


3. Notification Source returns a locator to the subscription service

1. NotificationSink callsthe subscribe operationon NotificationSource 2.Notification

Source creates a subscription service


NotificationSink

NotificationSource

NotificationSubscription4.b The NotificationSink and

Subscription service interactto perform lifetimemanagement

4.a deliverNotificationstream continuesfor the lifetime ofNotificationSubscription

1. NotificationSink callsthe subscribe operationon NotificationSource 2.Notification

Source creates a subscription service



NotificationSink

NotificationSource



subscribe2.NotificationSource creates a subscription service


4.b The NotificationSink and Subscription service interactto perform lifetimemanagement

4.a deliverNotificationstream continuesfor the lifetime ofNotificationSubscription

The sole mandatedcardinality: 1 to 1


GT-OGSA Grid Service Infrastructure

OGSI Spec Implementation Security Infrastructure


Base Services



Hosting Environment

Web Service Engine

GT3 Core: Security Infrastructure Transport Layer Security/Secure Socket

Layer (TLS/SSL)– To be deprecated

SOAP Layer Security– Based on WS-Security, XML Encryption,

XML Signature GT3 uses X.509 identity certificates for

authentication It also uses X.509 Proxy certificates to

support delegation and single sign-on, updated to conform to latest IETF/GGF draft

Need more info on how to use GT3 security




Base Services



Hosting Environment

Web Service Engine

GT3 Core: System Level ServicesGeneral-purpose services that facilitate the use

of Grid Services in production environmentsThe 3.0 distribution includes the following

System-Level services:An Administration ServiceA Logging ServiceA Management Service




Base Services



Hosting Environment

Web Service Engine

GT3 Core: Grid Service ContainerIncludes the OGSI Implementation, security

infrastructure and system-level services, plus:Service activation, deactivation, construction,

destruction, etc.Service data element placeholders that allow

you to dynamically fetch service data values at query time

Evaluator framework (supporting ByXPath and ByName notifications and queries)

Interceptor/callback framework (allows one to intercept certain service lifecycle events)

Interface Layer

Transport Layer

Implementation Layer

Layers in the Web Services Model

OGSI Spec is here

Transport/BindingLayer (GT3 supportsSOAP over HTTP)

Container is here




Base Services



Hosting Environment

Web Service Engine

GT3 Core: Hosting EnvironmentGT3 currently offers support for four Java

Hosting Environments:

EmbeddedStandaloneServletEJB

GT3 Core: Virtual Hosting Environment FrameworkVirtual Hosting allows grid services to be

distributed across several remote containers

Useful in implementing solutions for problems common to distributed computingLoad balancingUser account sandboxing

A GT3 Service Creation Scenario Illustrating Redirection in Virtual Hosting

Client

Registry

Router

HE Starter

1. Froma knownregistry, the client retrievesa factorylocator

NOT FINISHED:Need to add virtual factory, virtual service and actual factory


Client

Registry

Router1. Froma knownregistry, the client retrievesa factorylocator

HE Starter2. The routerintercepts thecreateServicecall on thefactory



Client

Registry

Router1. Froma knownregistry, the client retrievesa factorylocator

2. The routerintercepts thecreateServicecall on thefactory

HE Starter

3. The router passes the createServicerequest to the Host Env Starter



Client

Registry

Router

Service



HE Starter


4.The HEStarter createsa new Host Envas well as the service



Client

Registry

Router

Service



HE Starter


4.The HEStarter createsa new Host Envas well as the service

5. The router returnsa service locator



Client

Registry

Router

Service



HE Starter

6. Using the service locator, the router redirectssubsequent client-service interactions


4.The HEStarter createsa new Host Env

5. The router returnsa service locator

4.1.TheRouterRedirectsThe createserviceCall to theFactory in the new HE

Virtual Factory

Factory

Virtual Service


GT3 Base Services




Base Services



Hosting Environment

Web Service Engine

MMJFS

GT3 Base: Resource ManagementGRAM Architecture rendered in OGSAThe MMJFS runs as an unprivileged user, with

a small highly-constrained setuid executable behind it

Individual user environments are created using Virtual Hosting

MJS

MJSMJS

MJSUser 1

User 2

User 3

Master User

MJSMJS

MMJFS: Master Managed Job FactoryServiceMJS: Managed JobService

User Hosting Env

Client

GRAM Job Submission Scenario

IndexService

1. From an index service,the clientchooses an MMJFS

Client


IndexService 2. The client calls the

createServiceoperation on the factoryand supplies RSL

MMJFS


Client


IndexService MMJFS

MJS

3. The factorycreates aManaged JobService


2. The client calls thecreateServiceoperation on the factoryand supplies RSL

Client


IndexService MMJFS

MJS

4. The factoryreturns a locator


2. The client calls thecreateServiceoperation on the factoryand supplies RSL 3. The factory

creates aManaged JobService

Client


IndexService MMJFS

MJS5. The client subscribes tothe MJS’ status SDE and retrieves output


2. The client calls thecreateServiceoperation on the factoryand supplies RSL 3. The factory

creates aManaged JobService 4. The factory

returns a locator

GT3 Base: Information ServicesIndex Service as Caching Aggregator

Caches service data from other grid servicesIndex Service as Provider Framework

Serves as a host for service data providers that live outside of a grid service to publish data

Need more content for Info Services

GT3 Base: Reliable File TransferReliably performs a third party transfer between two

GridFTP serversOGSI-compliant service exposing GridFTP control channel

functionalityRecoverable Grid Service

Automatically restarts interrupted transfers from the last checkpoint

Progress and Restart Monitoring

GridFTP Server 1

GridFTP Server 2

RFT

JDBC




Base Services



Hosting Environment

Web Service Engine

GT3 User-Defined ServicesGT3 can be viewed as a Grid Service

Development Kit that includes:Primitives, apis, tools and runtime services

designed to ease the task of building OGSI-Compliant Services

Primitives for provisioning securityBase services that provide an infrastructure

with which to build higher-level services

GT3 User-Defined Services (cont.)

ANT

User source files

GT3 Build Files

User Build File

Grid Serviceexecutable files

(Diagram inspired by Borja Sotomayor’sexcellent tutorial on GT3)

http://gtr.globus.org http://gtr.nesc.ac.uk

Designed to facilitatecode reuse

Appropriate forpublishing OperationProvidersand GridServices

Low barrier to publish Licensing term set by

contributors

GT3 DocumentationThe GT3 distribution comes with a set of

sample code Doc overview here

GT3 SamplesThe GT3 distribution comes with a set of

sample code

List of samples

Future Directions of GTStandardization of container modelDevelopment of lightweight container/apiAdding rich support for queriesFurther refinements of Base Service designsPushing on standardizing at a higher level

than OGSI

GT3 Architecture and Functionality. Core OGSI Implementation Security Services System-Level Services...

Documents

Transcript of GT3 Architecture and Functionality. Core OGSI Implementation Security Services System-Level Services...