Ischia, Italy - 9-21 July 20061 Session 2 Monday 10 th July Malcolm Atkinson.

Slides:



Advertisements
Similar presentations
Fujitsu Laboratories of Europe © 2004 What is a (Grid) Resource? Dr. David Snelling Fujitsu Laboratories of Europe W3C TAG - Edinburgh September 20, 2005.
Advertisements

Abstraction Layers Why do we need them? –Protection against change Where in the hourglass do we put them? –Computer Scientist perspective Expose low-level.
Research Councils ICT Conference Welcome Malcolm Atkinson Director 17 th May 2004.
Performance Testing - Kanwalpreet Singh.
Research Issues in Web Services CS 4244 Lecture Zaki Malik Department of Computer Science Virginia Tech
The Open Grid Services Architecture, Version 1.0 I. Foster, H. Kishimoto, A. Savva, D. Berry, A. Djaoui, A. Grimshaw, B. Horn, F. Maciel, F. Siebenlist,
Agreement-based Distributed Resource Management Alain Andrieux Karl Czajkowski.
Internet Technologies (Grid Computing (OGSA, WSRF) )
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 12 Slide 1 Distributed Systems Design 2.
4.1.5 System Management Background What is in System Management Resource control and scheduling Booting, reconfiguration, defining limits for resource.
1 On Death, Taxes, & the Convergence of Peer-to-Peer & Grid Computing Adriana Iamnitchi Duke University “Our Constitution is in actual operation; everything.
Connect. Communicate. Collaborate Click to edit Master title style MODULE 1: perfSONAR TECHNICAL OVERVIEW.
1 Software & Grid Middleware for Tier 2 Centers Rob Gardner Indiana University DOE/NSF Review of U.S. ATLAS and CMS Computing Projects Brookhaven National.
The OGSA Vision for Service Oriented Architectures Dave Berry Research Manager, NeSC Co-chair, GGF OGSA Data WG European Grid Technology Days 2005 Concertation.
1 Introduction to XML. XML eXtensible implies that users define tag content Markup implies it is a coded document Language implies it is a metalanguage.
Distributed components
CIM2564 Introduction to Development Frameworks 1 Overview of a Development Framework Topic 1.
Grid Architecture: Representing NextGRID David Snelling Fujitsu Labs Europe.
Latest techniques and Applications in Interprocess Communication and Coordination Xiaoou Zhang.
OGF Standards Activity Steven Newhouse. © myOGF Part of the Standards Council Area Directror for Applications Working Groups Co-chair: Basic Execution.
NextGRID & OGSA Data Architectures: Example Scenarios Stephen Davey, NeSC, UK ISSGC06 Summer School, Ischia, Italy 12 th July 2006.
OCT1 Principles From Chapter One of “Distributed Systems Concepts and Design”
Ch 12 Distributed Systems Architectures
Web-based Portal for Discovery, Retrieval and Visualization of Earth Science Datasets in Grid Environment Zhenping (Jane) Liu.
Tanenbaum & Van Steen, Distributed Systems: Principles and Paradigms, 2e, (c) 2007 Prentice-Hall, Inc. All rights reserved DISTRIBUTED SYSTEMS.
Software Engineering Muhammad Fahad Khan
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 18 Slide 1 Software Reuse.
1 Autonomic Computing An Introduction Guenter Kickinger.
©Ian Sommerville 2006Software Engineering, 8th edition. Chapter 12 Slide 1 Distributed Systems Architectures.
An Answer to the EC Expert Group on CLOUD Computing Keith G Jeffery Scientific Coordinator.
Version 4.0. Objectives Describe how networks impact our daily lives. Describe the role of data networking in the human network. Identify the key components.
Managing Service Metadata as Context The 2005 Istanbul International Computational Science & Engineering Conference (ICCSE2005) Mehmet S. Aktas
OPEN GRID SERVICES ARCHITECTURE AND GLOBUS TOOLKIT 4
DISTRIBUTED COMPUTING
GT Components. Globus Toolkit A “toolkit” of services and packages for creating the basic grid computing infrastructure Higher level tools added to this.
Distributed Systems: Concepts and Design Chapter 1 Pages
Grid – Path to Pervasive Adoption Mark Linesch Chairman, Global Grid Forum Hewlett Packard Corporation.
Unit – I CLIENT / SERVER ARCHITECTURE. Unit Structure  Evolution of Client/Server Architecture  Client/Server Model  Characteristics of Client/Server.
Linked-data and the Internet of Things Payam Barnaghi Centre for Communication Systems Research University of Surrey March 2012.
Architectures of distributed systems Fundamental Models
The roots of innovation Future and Emerging Technologies (FET) Future and Emerging Technologies (FET) The roots of innovation Proactive initiative on:
Advanced Computer Networks Topic 2: Characterization of Distributed Systems.
Copyright © 2002 Intel Corporation. Intel Labs Towards Balanced Computing Weaving Peer-to-Peer Technologies into the Fabric of Computing over the Net Presented.
SCALABLE EVOLUTION OF HIGHLY AVAILABLE SYSTEMS BY ABHISHEK ASOKAN 8/6/2004.
Middleware for Grid Computing and the relationship to Middleware at large ECE 1770 : Middleware Systems By: Sepehr (Sep) Seyedi Date: Thurs. January 23,
 Apache Airavata Architecture Overview Shameera Rathnayaka Graduate Assistant Science Gateways Group Indiana University 07/27/2015.
1 Computing Challenges for the Square Kilometre Array Mathai Joseph & Harrick Vin Tata Research Development & Design Centre Pune, India CHEP Mumbai 16.
SEEK Welcome Malcolm Atkinson Director 12 th May 2004.
Chapter 5 McGraw-Hill/Irwin Copyright © 2011 by The McGraw-Hill Companies, Inc. All rights reserved.
NA-MIC National Alliance for Medical Image Computing UCSD: Engineering Core 2 Portal and Grid Infrastructure.
Cracow Grid Workshop ‘06 17 October 2006 Execution Management and SLA Enforcement in Akogrimo Antonios Litke Antonios Litke, Kleopatra Konstanteli, Vassiliki.
Securely Synchronize and Share Enterprise Files across Desktops, Web, and Mobile with EasiShare on the Powerful Microsoft Azure Cloud Platform MICROSOFT.
GRID Overview Internet2 Member Meeting Spring 2003 Sandra Redman Information Technology and Systems Center and Information Technology Research Center National.
31 March 2009 MMI OntDev 1 Autonomous Mission Operations for Sensor Webs Al Underbrink, Sentar, Inc.
OGSA-Basic Services Prof S.Ramachandram. Outline  Introduction  Common Management Model  Policy Architecture  Security Architecture  Metering and.
7. Grid Computing Systems and Resource Management
© 2004 IBM Corporation ICSOC2004 Panel Discussion: Grid Systems: What is needed from web service standards? Jeffrey Frey IBM.
GRID ANATOMY Advanced Computing Concepts – Dr. Emmanuel Pilli.
INTRODUCTION TO GRID & CLOUD COMPUTING U. Jhashuva 1 Asst. Professor Dept. of CSE.
A Semi-Automated Digital Preservation System based on Semantic Web Services Jane Hunter Sharmin Choudhury DSTC PTY LTD, Brisbane, Australia Slides by Ananta.
Grid Services for Digital Archive Tao-Sheng Chen Academia Sinica Computing Centre
Service Oriented Architecture (SOA) Prof. Wenwen Li School of Geographical Sciences and Urban Planning 5644 Coor Hall
Chapter 1 Characterization of Distributed Systems
SuperComputing 2003 “The Great Academia / Industry Grid Debate” ?
Distributed Systems Bina Ramamurthy 11/30/2018 B.Ramamurthy.
Service Oriented Architecture (SOA)
The Anatomy and The Physiology of the Grid
The Anatomy and The Physiology of the Grid
Introduction To Distributed Systems
Presentation transcript:

Ischia, Italy July Session 2 Monday 10 th July Malcolm Atkinson

Ischia, Italy July 20062

3 Principles of Distributed Computing Issues you can’t avoid –Lack of Complete Knowledge (LOCK) –Latency –Heterogeneity –Autonomy –Unreliability –Change A Challenging goal –balance technical feasibility –against virtual homogeneity, stability and reliability Appropriate balance between usability and productivity –while remaining affordable, manageable and maintainable This is NOT easy

Ischia, Italy July Lack of Complete Knowledge Technical origins of LoCK –Dynamics of systems involve very large state spaces Can’t track or explore or all the states –Latency prevents up-to-date knowledge being available By the time a notification of a state change arrives the state may have changed again –Failures inhibit information propagation –Unanticipated failure modes

Ischia, Italy July Lack of Complete Knowledge 2 Human origins of LoCK –lack of understanding –Incomplete simplified models –Intractable models –Poor & incomplete descriptions –Erroneous descriptions Socio-Economic effects generate LoCK –Autonomous owners do not choose to reveal all About their services, resources and performance –Intermediaries aggregate & simplify

Ischia, Italy July LoCK Counter Strategies Improve the quality of the available knowledge –Better static information –Better information collection & dissemination Improve quality of the Distributed System Models –Prove invariants that algorithms can exploit –Test axioms with real systems Build algorithms that behave reasonably well –When they have incomplete knowledge

Ischia, Italy July Latency It is always going to be there –Consequence of signal transmission times –Consequence of messages / packets in queues –Consequence of message processing time –Errors cause retries It gets worse –Geographic scale increases latency –System complexity increases number of queues –System scale & complexity increase processing time Think about –How many operations a system can do while a message it sent reaches its destination, a reply is formed and the reply travels back

Ischia, Italy July Latency Counter Strategies Design algorithms that require fewer round trips –This is THE complexity measure! –Batching requests and responses Shorten distance to get information –Caching But may be stale data! –Move data to computation But be smart about which data when –Move computation to data Succinct computation & volumes of data But safety and privacy issues arise

Ischia, Italy July Heterogeneity Hardware variation –Different computer architectures Big endians v little endians Number representation Address length Performance –Different Storage systems Architectures Technologies Available operations –Different Instrument systems Accepting different control inputs Generating different output data streams Some of the variation is wanted and exploited

Ischia, Italy July Heterogeneity 2 Operating System variation –Different O/S architectures Unix families & versions Windows families and versions Specialised O/S, e.g. for Instruments & Mobile devices Implementation system variation –Programming languages –Scripting languages –Workflow systems –Data models –Description languages –Many implementations of same functionality Some of the variation is just makes work

Ischia, Italy July Heterogeneity Counter Measures Invest in virtual Homogeneity –Agree standards (formally or de facto) –Introduce intermediate code That hides unwanted variation Presenting it in standard form –But this has high cost Developing the standard Developing the intermediate code Executing the intermediate code –It may hide variations some want Provide direct access to facilities as well But this may inhibit optimisation & automation May be work in progress

Ischia, Italy July Heterogeneity Counter Measures 2 Automatically manage diversity –Manual agreement and construction of virtual homogeneity will not scale & compose –Develop abstract and higher level models –Describe each component –Generate the adaptations as needed from these descriptions Not yet achievable for the general & complete systems –Relevant for specific domains

Ischia, Italy July Autonomy and Change Necessary –To persuade organisations & individuals to engage They need to control their own facilities They have best knowledge to develop their services Their business opportunity –Because coordinated change is unachievable Systems & workloads are busy Service commitments must be met Large-scale scheduling of work is very hard –To correct errors –To plug vulnerabilities

Ischia, Italy July Autonomy and Change 2 What changes – local decisions –The underlying technology delivering a service –The operations available from a service –The semantics of the operations –Policy changes, e.g. authorisation rules, costs, … What changes – corporate decisions –Some agreed standard is changed E.g. a new version of a protocol is introduced

Ischia, Italy July Autonomy and change Counter Measures Users & other providers expect stability Agree some standards that are rarely changed –As a platform & framework –As a means of communicating change Introduce change-absorbing technology –Mark the protocols and services with version information –Transform between protocols when changes occur –Anneal the change out of the system Develop algorithms tolerant to change –Revalidate dependencies where they may change –Handle failures due to change

Ischia, Italy July Unreliability Failures are inevitable –Equipment, software & operations errors –Network outages, Power outages, … Their effects must be localised –Cannot afford total system outages This is not easy –Each error may occur when system is in any state –The system is an unknown composition of subsystems –Errors often occur while other errors are still active –Errors often occur during error recovery actions –Errors may be caused by deliberate attack –Attackers may continue their attack

Ischia, Italy July Unreliability Counter Measures Requires much R&D Continuous arms race as scale of Grids grow Ideal of a continuously available stable service –Not achievable – recognise that drops in response and local failures must be dealt with Design resilient architectures Design resilient algorithms Improve reliability of each component Distribute the responsibility –For failure detection –For recovery action

Ischia, Italy July

Ischia, Italy July Three Components Registries Service Consumers Services Register an available service Send name & description

Ischia, Italy July Three Components Registries Service Consumers Services Request a service Send a description

Ischia, Italy July Three Components Registries Service Consumers Services Request service operation

Ischia, Italy July Three Components Registries Service Consumers Services Return result or Error

Ischia, Italy July Composed behaviour Services are themselves consumers –They may compose and wrap other services The registry is itself a consumer A federation of registries may deal with registry services reliability & performance Observer services may report on quality of services and help with diagnostics Agreements between services may be set up –Service-Level Agreements –Permitting sustained interaction

Ischia, Italy July Composed behaviour Services are themselves consumers –They may compose and wrap other services The registry is itself a consumer A federation of registries may deal with registry services reliability & performance Observer services may report on quality of services and help with diagnostics Agreements between services may be set up –Service-Level Agreements –Permitting sustained interaction

Ischia, Italy July

Ischia, Italy July The Open Grid Services Architecture An open, service-oriented architecture (SOA) −Resources as first-class entities −Dynamic service/resource creation and destruction Built on a Web services infrastructure Resource virtualization at the core Build grids from small number of standards-based components −Replaceable, coarse-grained −e.g. brokers Customizable −Support for dynamic, domain-specific content… −…within the same standardized framework Hiro Kishimoto: Keynote GGF17

Ischia, Italy July Logical view of capabilities Relatively coarse-grained functions Reusable and composable behaviors Encapsulation of complex operations Naturally extendable framework Platform-neutral −machine and OS Why Use an SOA? Hiro Kishimoto: Keynote GGF17

Ischia, Italy July SOA & Web Services: Key Benefits SOA Flexible −Locate services on any server −Relocate as necessary −Prospective clients find services using registries Scalable −Add & remove services as demand varies Replaceable −Update implementations without disruption to users Fault-tolerant −On failure, clients query registry for alternate services SOA Flexible −Locate services on any server −Relocate as necessary −Prospective clients find services using registries Scalable −Add & remove services as demand varies Replaceable −Update implementations without disruption to users Fault-tolerant −On failure, clients query registry for alternate services Web Services Interoperable −Growing number of industry standards Strong industry support Reduce time-to-value −Harness robust development tools for Web services −Decrease learning & implementation time Embrace and extend −Leverage effort in developing and driving consensus on standards −Focus limited resources on augmenting & adding standards as needed Web Services Interoperable −Growing number of industry standards Strong industry support Reduce time-to-value −Harness robust development tools for Web services −Decrease learning & implementation time Embrace and extend −Leverage effort in developing and driving consensus on standards −Focus limited resources on augmenting & adding standards as needed Hiro Kishimoto: Keynote GGF17

Ischia, Italy July Virtualizing Resources Resources Web services Access Storage Sensors Applications Information Computers Resource-specific Interfaces Common Interfaces Type-specific interfaces Hiro Kishimoto: Keynote GGF17

Ischia, Italy July A Service-Oriented Grid Virtualized resources Grid middleware services Brokering Service Registry Service Data Service CPU Resource Printer Service Job-Submit Service Compute Service Notify Advertise Application Service Hiro Kishimoto: Keynote GGF17

Ischia, Italy July A Closer Look at OGSA Hiro Kishimoto: Keynote GGF17

Ischia, Italy July OGSA Capabilities Security Cross-organizational users Trust nobody Authorized access only Security Cross-organizational users Trust nobody Authorized access only Information Services Registry Notification Logging/auditing Information Services Registry Notification Logging/auditing Execution Management Job description & submission Scheduling Resource provisioning Execution Management Job description & submission Scheduling Resource provisioning Data Services Common access facilities Efficient & reliable transport Replication services Data Services Common access facilities Efficient & reliable transport Replication services Self-Management Self-configuration Self-optimization Self-healing Self-Management Self-configuration Self-optimization Self-healing Resource Management Discovery Monitoring Control Resource Management Discovery Monitoring Control OGSA OGSA “profiles” Web services foundation Hiro Kishimoto: Keynote GGF17

Ischia, Italy July CDL 3. Select from or deploy required resources Execution Management The basic problem −Execute and manage jobs/services in the grid −Select from or provision required resources The basic problem −Execute and manage jobs/services in the grid −Select from or provision required resources 2. Submit the job 1. Describe the job JSDL Job 4. Manage the job Hiro Kishimoto: Keynote GGF17

Ischia, Italy July Issues Find Describe Access Data Formats Protocols Use cases Data Move/Copy/Replicate Metadata Data Manage Common access Data Services The basic problem Manage, transfer and access distributed data services and resources The basic problem Manage, transfer and access distributed data services and resources Derived dataCatalog SensorData stream Text file Relational database Hiro Kishimoto: Keynote GGF17

Ischia, Italy July Resource Management Provides a framework to integrate resource management functions −interfaces, services, information models, etc. Enables integrated discovery, monitoring, control, etc. Provides a framework to integrate resource management functions −interfaces, services, information models, etc. Enables integrated discovery, monitoring, control, etc. High-level management services (GGF) Domain-specific capabilities OGSA Access to manageability (OASIS, DMTF) Information models (DMTF, SNIA, etc.) Resources WSDM, WS-Management WSRF/WSN, WS-Transfer/Eventing Data services Security services Execution Management services Application- specific Hiro Kishimoto: Keynote GGF17

Ischia, Italy July Information Services Execution management Resource reservation Problem determination Accounting Application monitoring Load balancing Service discovery Consumers Information Services Reliable Secure Efficient Provide management and access facilities for information about applications and resources in the grid environment Producers Asynchronous notification Retrieval Registry Logger Hiro Kishimoto: Keynote GGF17

Ischia, Italy July Specifications Landscape: April 2006 SYSTEMS MANAGEMENT UTILITY COMPUTING GRID COMPUTING Core Services Web Services Foundation WS-Addressing Privacy WS-BaseNotification 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 StandardEvolvingGapHole Warning: Volatile data! Hiro Kishimoto: Keynote GGF17

Ischia, Italy July

Ischia, Italy July Grids Many reasons motivating investment in grids –Collaboration for Global Science & Business –Resource integration & sharing New approach to large scale distributed systems –Large coordinated effort –Industry & Academia Many technical and socio-economic challenges –Work for you all Many new opportunities –Work for you all

Ischia, Italy July Summary: Take home message E-Infrastructure is arriving –Built on Grids & Web Services –Data and Information grow in importance There is a dramatic rate of change An opportunity for everyone

Ischia, Italy July