Grid Architecture: Representing NextGRID

1
Grid Architecture Representing NextGRID

• David Snelling
• Fujitsu Labs Europe

2
Role of Architecture

• Organizing
• Knowing how the pieces fit together
• Esthetics
• Decomposition
• Concurrent development of different pieces
• Communication
• Relating the design to others for better
  understanding
• Internally to the development team
• Externally to other stakeholders

3
The Challenge of SOA

• Key Service Oriented Principles
• Compatibility
• Simple parts
• Intended for distributed systems
• Acknowledgement of boundaries
• Presentation of SOA is Fraught
• Very many small pieces
• The interactions are not (statically) defined
• Encapsulation rather than layering

4
Example Object Based Architecture
Resource Database
Resource Broker
Server
Network Job Supervisor
Unicore Gateway
Unicore Client
Server
Server
User Database
Firewall
5
Internals AJO
6
Typical SOA Example
Management
Utility Business Services
Rating
uses
Service Level Managers
Job / Scheduling
Management Services
Policy Decision Point
Metering
Metric Mediation
uses
uses
Manageable Resources
Job Provisioning Resource
Job Manageable Resource
Resource Models
Manageability Capabilities Descriptions
Reserve/Allocate
Metrics
Policy Enforcement Point
uses
Policies for Web Services
Common Web Services
Agreement Mediation
Policy Server
Notification
Collection
MetaData Exch
Transaction
Coordination
Service Agreements
Web Services Description
Policy
Interface
Reliable Msg
Property
Agreement
Endpoint
Service
Addressing
Security
Process
7
Another Typical SOA Example
SYSTEMS MANAGEMENT
UTILITY COMPUTING
GRID COMPUTING
Use Cases Applications
Distributed query processing
Data Centre
ASP
Collaboration
Multi Media
Persistent Archive
VO Management
OGSA-EMS
OGSA Self Mgmt
WS-DAI
Core Services
WSDM
Discovery
Information
WS-Base Notification
Naming
GGF-UR
Privacy
GFD-C.16
Trust
Data Model
WSRF-RL
WSRF-RP
WSRF-RAP
WS-Security
SAML/XACML
X.509
Base Profile
WS-Addressing
CIM/JSIM
HTTP(S)/SOAP
WSDL
Data Transport
8
NextGRID Attempts
9
NextGRID Approach

• Schemas
• Message, Security, SLA, Service Description
• Support Systems
• Naming and Addressing
• Trust and Security
• SLA Management
• Registry
• Functional Systems
• Data Focused
• Provenance, Transfer, Storage, Processing, Access
• Orchestrators
• Workflow and Federation

10
NextGRID Interactions
Registry
Get token assertions
Register / Discover
Register
Discover
Functional
Naming and Addressing
Orchestration
Resolve
Invoke
Mint
Get tokens
Get token assertions
Monitor/ Control
Negotiate SLA
Get token assertions
SLA Management
Trust and Security
Get token assertions
Administer policy
11
Questions

• Has anyone else felt this way?
• Is SOA really harder to model than OO?
• Could you understand the NextGRID picture?
• ???