R-GMA: EDG 2.1

11
WP3 R-GMA: EDG 2.1 Steve Fisher / RAL 16/4/2003 <s.m.fisher@ rl .ac. uk >

description

R-GMA: EDG 2.1. Steve Fisher / RAL 16/4/2003 . Programme till Dec 31. Functionality Not much to do here Resilience and Scalability Significant work to keep everyone happy Security Essential for some areas of use Performance Optimisation Nothing done here yet - PowerPoint PPT Presentation

Transcript of R-GMA: EDG 2.1

Page 1: R-GMA:  EDG 2.1

WP3

R-GMA: EDG 2.1

Steve Fisher / RAL16/4/2003

<[email protected]>

Page 2: R-GMA:  EDG 2.1

Steve Fisher/RAL -16/4/2003R-GMA EDG 2.1 2

WP3Programme till Dec 31

• Functionality– Not much to do here

• Resilience and Scalability– Significant work to keep everyone happy

• Security– Essential for some areas of use

• Performance Optimisation– Nothing done here yet

• OGSA Compliant Implementation– Essential for long life

Page 3: R-GMA:  EDG 2.1

Steve Fisher/RAL -16/4/2003R-GMA EDG 2.1 3

WP3Functionality - Nagios

• Looking to include Nagios as a presentation tool.

• Will write a Nagios plug-in to instantiate an Archiver and use that information to populate Nagios displays

• Can also benefit from Nagios alert mechanism

• Will have different configurations for Site, Country, whole Grid etc.

• Expect to see this completed by Dec 31

Page 4: R-GMA:  EDG 2.1

Steve Fisher/RAL -16/4/2003R-GMA EDG 2.1 4

WP3Functionality - mediator

• Queries posed against a virtual data base• The Mediator must:

– find the right Producers– combine information from them

• Can now merge information from several producers

• The final mediator will take “any” SQL statement and do the right thing– How far can we get by end of project?

Page 5: R-GMA:  EDG 2.1

Steve Fisher/RAL -16/4/2003R-GMA EDG 2.1 5

WP3Resilience - Registry

• Will have one logical registry and schema per VO

• Each logical registry will have multiple physical “copies”

• Each entry in registry has 3 possible states

• Transmit new records and deleted records and checksum after records deleted locally

• Self healing even supports new registry instances

• Consumer uses any instance

• Fail over mechanism not yet implemented

• Schema more tricky

Producer1

Producer2

Registry2

Info mastered by Registry2

Copy of info from Registry1

Copy of info from Registry3

Registry3

Info mastered by Registry3

Copy of info from Registry1

Copy of info from Registry2

Registry1

Info mastered by Registry1

Copy of info from Registry2

Copy of info from Registry3

Page 6: R-GMA:  EDG 2.1

Steve Fisher/RAL -16/4/2003R-GMA EDG 2.1 6

WP3Resilience Testing• Taking 7 components

– Schema– 2 registry instances– Producer API– Consumer API– Producer Servlet with other APIs– Consumer Servlet with other APIs

• Consider each component in turn– Break the network and bring it back– Close the component down and bring it back– Crash the component and bring it back

• Will also consider real life scenarios

Page 7: R-GMA:  EDG 2.1

Steve Fisher/RAL -16/4/2003R-GMA EDG 2.1 7

WP3Security• Adding edg-security for authentication

– Gives secure socket factory for https

• Plan to use VOMS• Still designing authorisation scheme

Page 8: R-GMA:  EDG 2.1

Steve Fisher/RAL -16/4/2003R-GMA EDG 2.1 8

WP3Performance• By design:

– Very flexible - to avoid bottlenecks– Powerful queries allow a single query to be made

• We need to use the right tools to measure and improve performance– NetLogger to get an idea of time delays through

system– Java profiling tools to understand the details

Page 9: R-GMA:  EDG 2.1

Steve Fisher/RAL -16/4/2003R-GMA EDG 2.1 9

WP3OGSIfication• Have recently started the migration to web

and grid services– Apache axis– WSDL generated APIs– Will provide a wrapper for backwards compatibility

Page 10: R-GMA:  EDG 2.1

Steve Fisher/RAL -16/4/2003R-GMA EDG 2.1 10

WP3Programme till Dec 31

• Functionality– Enhanced Mediator– Nagios Integration

• Resilience and Scalability– Consider all failure modes– Complete Registry and Schema replication

• Security– Authorisation

• Performance Optimisation• OGSA Compliant Implementation

– GT3 inter-operability– Wrappers for backwards compatibility

Page 11: R-GMA:  EDG 2.1

Steve Fisher/RAL -16/4/2003R-GMA EDG 2.1 11

WP3

What we don’t expect to do/complete

• Port to other flavours of Unix• Port to Windows• Complete the mediator to cope with any SQL

query– This is a BIG job

• Complete the OGSIfication– OGSA will be changing under our feet

• Complete authorisation scheme