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. Server Example Object Based Architecture Unicore Gateway Unicore Client Network Job Supervisor Resource Database User Database Server Resource Broker Firewall

5. Internals: AJO

6. Typical SOA Example Management Policies for Web Services Web Services Description Common Web Services NotificationCollection Agreement Mediation MetaData Exch Policy Server Service Agreements Endpoint PolicyInterface ServiceAddressingSecurityProcess Reliable MsgProperty Agreement TransactionCoordination Resource Models Manageability Capabilities Descriptions Manageable Resources Management Services Service Level Managers Utility Business Services Rating Policy Decision Point Policy Enforcement Point Reserve/Allocate Job Manageable Resource Job / Scheduling uses Metering Metric Mediation Metrics Job Provisioning Resource

7. Another Typical SOA Example SYSTEMS MANAGEMENT UTILITY COMPUTING GRID COMPUTING Core Services Base Profile WS-Addressing Privacy WS-Base Notification CIM/JSIM WSRF-RAP WSDM WS-Security Naming OGSA-EMSOGSA Self Mgmt GFD-C.16 GGF-UR Data Model HTTP(S)/SOAP Discovery SAML/XACML WSDL WSRF-RL Trust WS-DAI VO Management Information Distributed query processing ASP Data Centre Use Cases & Applications CollaborationMulti MediaPersistent Archive Data Transport WSRF-RP X.509

8. NextGRID Attempts service provider service User SLA Configuration Policy Monitoring Policy Event Business layer Technology layer NextGRID Service SLA SLA? SLA

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. Registry Functional SLA Management Trust and Security Naming and Addressing Orchestration Register Discover Resolve Mint Administer policy Monitor/ Control Get tokens Negotiate SLA Invoke Get token assertions Register / Discover Get token assertions Get token assertions Get token assertions NextGRID Interactions

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