Open Grid System Architecture (OGSA)

Open Grid System Architecture (OGSA)

Azizol Abdullah

FSKTM,UPM

OGSA-DAI

• February 2002• Current partners

– EPCC, The University of Edinburgh– National e-Science Centre, The University of Edinburgh

• OGSA-DAI phase 4 funded as part of OMII-UK followon

• OMII-UK– Partners

• OMII, The University of Southampton• myGrid, The University of Manchester• OGSA-DAI, The University of Edinburgh• Funded by UK Engineering and Physical Sciences Research

Council

• OMII-UK vision– Free open source software– Consultancy– Cultivate and sustain community software

important to research• Drive its improvement and impact• Enable and improve multi-disciplinary use• Enable a sustained future for the UK e-Research

community

Challenges

• Diversity– Data resource types, vendors, middleware, schema,

meta data• Scale

– Collections, formats, volumes, geographical, political and social distance

• Ownership– On individual, group, and organisational levels

• Security– Client, service and data owners– Many levels, with many tradeoffs

Heterogeneity

• Data model• Database products

– MySQL, Oracle, DB2, SQL Server, Postgres,…– eXist, Xindice.– o Persisted or in-memory

• Query languages– SQL-92, product-specific extensions,…– XPath, XQuery, XUpdate,…

• Database schema– Country, Pays, Nation, …– Doctors.ID, Doctors.id, doctors.drID, Staff.NI, ...

Data with different schema distributed across multiple Databases within an organisation

• Transport company• Data distributed across sites

– Customer contact– Vehicle mileage– Ticket revenues– Schedule adherence

• Combine and mine the data– How bus lateness affects revenue– How bus cancellations affects complaints– Information of commercial significance

Data with different schema distributed across multiple databases within a group of strategic partners

• Public health providers– Share data on patients, illnesses and treatments

• Combine and mine the data– Early warning of infectious disease outbreaks

• Manage access to the data– Within partners – doctors, accountants, receptionists– Between partners – anonymise patient identities– Access policies according to roles and rights of

groups of users