The OMII
Overview, Product and Roadmap
OMII_1

Delivering a secure, reliable, web services
infrastructure for grid applications

Easy to use, professionally tested,
Accountable
© University of Southampton omii
Presentation Contents



OMII Overview
 The Need for the OMII
 OMII Remit
 OMII at Southampton
OMII Software Product
 Product Info
 Product Timetable
 Customers
OMII Roadmap
 Standards
 Future
 Managed Programme
 Software Repository
 International involvement
© University of Southampton omii
The OMII in a nutshell





Open Middleware Infrastructure Institute
Established January 2004, initially 3 years with
£6.5m
Intention - To capitalise on existing e-science
investment and produce high-quality, reusable grid
middleware
Rationale – much e-science invest in “proof of
concept” and demonstrators – investigations into
technology and approaches
OMII should benefit from, re-use, reengineer,
existing e-science work where appropriate
© University of Southampton omii
The OMII Remit



Key Goal is to produce usable and “used” grid middleware
and services. Achieved through:
 OMII “In-house” development
 Explicit S/W Contracts
 OMII “managed programme”
Success Criteria
 Number of software downloads
 Number of deployed systems
 Key academic and e-science projects use it
 Industry uptake
Sustained through success
 UK research, JISC and DTI funding
 Industry support
© University of Southampton omii
The OMII at Southampton



Located on Southampton University Campus
– dedicated, continuous open plan offices
Currently 13 F/T staff, recruiting additional 4
to 6
Additional continuous space allocated in
December
© University of Southampton omii
OMII_1 Product Overview


OMII_1 is a secure infrastructure that enables collaboration
between users (clients) and providers of resource and applications
Target Audience



Grid resource users: User requesting services/resources through a
command line interface or through application
Service providers: Exposes resources or applications to known
clients/users
Application developers: Web-service developers who want to provide
distributed, controlled and secure access to their applications
© University of Southampton omii
OMII_1 Product Overview (2)


Security
 X509 Authentication (AAA) with HTTPS message security
 Authorisation through account based system at service providers
(AAA)
 Accounting (AAA) for resource/service use maintained by service
provider and visible to client. Accounting can influence
Authorisation
Client/Service-provider Interaction
 Client submits resource request to service provider(s)
 Service provider(s) respond with a “quote” for job if the resource
provider can meet required constraints and client account has
sufficient credit
 Client selects a provider and submits job
 Client account is debited with estimated resources used for job
 On job completion client account is updated to actual resources
used
© University of Southampton omii
OMII_1 Product Components –
(1)


4 packages
Package 1 - Client download





Command line client and Java library to interact with
any OMII_1 service provider
< 10 minutes to install and interact with servers at
OMII
Example client application program
Supported on Windows and SUSE9 Linux
No additional download for Grid “Users”
© University of Southampton omii
OMII_1 Product Components –
(2)

Package 2 - OMII_1 Base and Extensions







Server base providing Tomcat, Axis and WS-Security
< 10 minutes for complete install
Supported on SUSE9 Linux
Package 3 - OMII_1 Services
 Initial basic services (Accounting service, resource Allocation
Service, Data movement service, Job Submission service)
 Installed on Base and Extensions (SUSE9 Linux)
Package 4 - OMII_1 Applications
 Sample application to demonstrate service provision
 Installed on OMII_1 Services
 Supported on Windows and SUSE9 Linux
Service Providers require Packages 2 and 3
Application developers require all packages
© University of Southampton omii
OMII_1 Associated Products



OGSA-DAI
Condor Interface
PBS Interface
© University of Southampton omii
OMII_1 Product License


All OMII code distributed using BSD license
Includes licensed components (Apache
license and LGPL)
© University of Southampton omii
OMII_1 Release Timetable
Private prerelease
OMII_1
Public prerelease
OMII_1
Official
OMII_1
release
Developers
refresh
October 4th
2004
October 25th
2004
December 6th
2004
End Jan
2005


Pre-releases targeted at early adopters to grid enable services
Little change from OMII_1 pre-release to official release


improved documentation, testing, platform support
Developers Refresh



Refresh base and services
Update WS-Security in line with WS-I
Re-factor extensions to base to allow selective install of services
© University of Southampton omii
OMII_1 Customers

Target E-science projects just starting




Existing E-science projects









EPSRC projects in discussion – Integrative Biology, GOLD
BBSRC project possibilities – ComparaGRID, GridQTL, e-Fungi, ISPIDER,
etc
NERC, MRC, etc…
Follow-on e-science projects
MyGrid
Nerc DataGrid
E-materials project
ServerGrid project
Astrogrid – already use web services and OGSA-DAI
Projects requiring a ready to use grid infrastructure including
documentation, training courses, support
Industrial Partners
Managed programme partners
© University of Southampton omii
OMII Roadmap - Position
statement

Committed to WS-I+





WS-I basic profile (SOAP, WSDL, UDDI)
WS-I basic security profile (WS-Security)
WS-Addressing, BPEL+, WS-Reliable
Messaging/WS-Reliability
Plans and timescales to deliver WS-I+
OMII intends to adopt WSRF as and when
standardised and stable
© University of Southampton omii
OMII Product Roadmap 2005

April 2005: 2nd OMII Distribution



Include WS-Addressing
Interoperability with GT4
New services
© University of Southampton omii
OMII Service Sets Roadmap



In priority order, not
delivery order
Delivery dependent on
managed programme
Basic Service Set




Job Submit
File movement
Database Access
Authorisation

Service Set 1
 Workflow
 Registry
 Logging
 Accounting
 Session Management

Service Set 2
 Notification
 Reliable Messaging
 File management services
(provenance, metadata,
replica)
© University of Southampton omii
Delivering OMII service sets




All OMII distributions will contain the basic
service set.
Basic Service set will be revised & updated
between distributions
Delivery of service sets 1 and 2 are post April
2005, although some services from service
set 1 will be in OMII Distribution 2
Service sets are subject to modification
© University of Southampton omii
Managed Programme funding


2/3rds managed programme funding spent
Projects funded:









OGSA-DAI (Database service)
JDML (Job submit service)
BPEL (Workflow service)
Grimoires (Registry service)
FIRMS (Reliable messaging)
FINS (Notification)
GeodiseLab (Matlab toolbox)
WSRF:lite integration
Basic Service Set
Service Sets 1 & 2
Further contracts placed/calls in the next 6 months to
address gaps
© University of Southampton omii
Managed programme status


All projects required to engage 3 test communities
and use OMII distribution from outset
Work negotiations complete



Grid SAM and Geodise started 1st September
All others started in October
Official kick-off meeting 21st October in
Southampton


Introduction/discussion on OMII distribution and integration
of managed programme output
Standards, Documentation, OMII security,…
© University of Southampton omii
External Contributions to OMII

Major source through contracts and managed
programme



Primarily contributing to essential elements of OMII
distributions
Managed programme required to liaise with other
middleware bodies (e.g., EGEE, Globus)
Additional source from repository contributions



Primarily end user services from e-science projects
Generic service useful to others tested with OMII
distribution that are optional to install
Talk to OMII – we can help publicise your services and
assist where appropriate with input to the repository
© University of Southampton omii
International Relationships with
other infrastructure providers-NMI

Visited Condor group in June – identified 3 phases
in collaboration




OMII to use same test harness as NMI
Link the OMII and NMI testing infrastructures
Work with NMI to develop distributed testing framework
Status



Regular conference calls
A non-interactive version of the OMII distribution is being
integrated into the NMI build system
Demonstration of OMII build in NMI scheduled for SC2004
© University of Southampton omii
International Infrastructure
Relationships (2)

EGEE



Specific integration with managed programme projects
(Registry, Grid SAM)
Further integration and interoperability to be investigated
Q4 2004
Globus


Visited Globus June - discussed integration possibilites
 Security – possible re-use of SAML/PERMIS infrastructure
from GT4 – common core with EGEE/GT4
 Integration of GRIDFTP (dependent on delegation service)
Joint requirements gathering
© University of Southampton omii
International Relationships with
Standards Organisations (3)

GGF



EGA


Indirect through managed programme – JSDL
working group, GRID SAM; SAGA working group,
Geodise Lab
Requirements gathering presented last GGF
Member through core programme – no active
communication
Oasis member
© University of Southampton omii
OMII International Profile

We are expected to engage with the community


OMII will take the lead on infrastructure integration



standards, specifications, working with other people who
are trying to achieve the same goal.
OMII is working directly with NMI on Testing
Globus and EGEE on integration at the level where
services can be invoked across infrastructures
The OMII success measure = customers
© University of Southampton omii