Cluster / Grid with Web and Semantic Services - PowerPoint PPT Presentation

cluster grid with web and semantic services n.
Download
Skip this Video
Loading SlideShow in 5 Seconds..
Cluster / Grid with Web and Semantic Services PowerPoint Presentation
Download Presentation
Cluster / Grid with Web and Semantic Services

play fullscreen
1 / 111
Cluster / Grid with Web and Semantic Services
181 Views
Download Presentation
Download Presentation

Cluster / Grid with Web and Semantic Services

- - - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript

  1. Cluster / Grid with Web and Semantic Services Dr G Sudha Sadasivam Professor, CSE PSG College of Technology Coimbatore- 641 004

  2. Agenda • Web Services • SOA • Semantics • Grid Architecture • 3rd Generation Grid Architecture • Semantic Grid • Cluster Architecture- Hadoop • Amazon Web Services • Work at Grid and Cloud Computing Lab - PSGCT ORGANISING A BIRTHDAY PARTY????

  3. PRODUCTS AND SERVICES – A TRADITIONAL WAY OF DISCOVERING AND ACCESSING

  4. INFORMATION SERVICES

  5. 1. Web Service • A service is a set of actions that form a coherent whole from the point of view of service providers and service requesters - Arranging for a birthday party. • Web services provide a standard means of interoperating between different software applications, running on a variety of platforms and/or frameworks in a transparent and loosely coupled manner • A Web service is a software system designed • to support interoperable machine-to-machine interaction • has an interface described in a machine-processable format (WSDL). • communication using standard SOAP-messages, on HTTP • with an XML serialization in conjunction with other Web-related std. • UDDI registry • identified by URI • Web service is an entity that can be: • Described (using WSDL) • Published • Discovered • Invoked by a client • W3C technology standardization process

  6. Web Service Interactions

  7. COMPONENTS • A Web service is an abstract notion that is implemented by a concrete agent. • Elements • The provider entity is the person or organization that provides an appropriate agent to implement a particular service. • A requester entity is a person or organization that wishes to make use of a provider entity's Web service. • Registry – to register the services • Web Service Discovery: • Before message exchange, the requester entity and the provider entity must first agree on both the semantics and the mechanics of the message exchange • The service description (WSD) (message formats, datatypes, transport protocols, and transport serialization formats) represents a contract governing the mechanics of interacting with a particular service. • The semantics represents a contract governing the meaning (consequence and purpose) of that interaction.

  8. 2. SOA • Aim: Alignment of Business needs with IT • Architectural style of building enterprise solutions based on services • SOA is a blueprint that governs creation, deployment, execution and management of reusable business services. • WSA is an instance of SOA (Architecture – independent of tech.) • Services provide independent, loosely coupled, transparent, composable invocation of tasks in a standard way. • SOA separates functions into distinct units (services), which can be distributed over a network and can be combined and reused to create business applications. These services communicate with each other by passing data from one service to another, or by coordinating an activity between two or more services. • Guiding principles – Reusability, Open standards • Services (identification, categorization, monitoring and tracking)

  9. Alignment of Business needs with IT

  10. services services

  11. Human-mediated service Self- service System-system delivery service SO business delivers services to its customers SOA is a blueprint that governs creation, deployment, execution and management of reusable business services It aligns Business and Technology Service Oriented architecture contract contract contract New system Composite system Legacy system • Services created using an SOA and provided by an organisation’s IT should directly support the services that the organisation provides to its customers. (BP – IT)

  12. SOA roles • Business Role: SOA is viewed as a set of services that a business wants to expose to customers and clients. • Architectural Role: SOA is an architectural style which requires a service provider, requestor and a service description. It provides services that fosters modularity, encapsulation, loose coupling, separation of concerns, reuse, composable and single implementation. • Implementation Role: SOA is a complete programming model (process) with standards, tools, methods and techniques, technologies.

  13. Model and Capture business processes and policies Integrate the services using ESB and orchestrate the services into BP SOA Develop, connect and bind services to build composite applications Apply runtime policies to services and govern them Deploy composite applications and to perform service level management SOA suite Activity monitoring to gain real-time information on BP

  14. Service • A service is a manager entity that consists of a collection of components that work together to deliver the business function (currency conversion/airline reservations) • A service maps to a business function but a component maps to business entities and the business rules that operate on them. • Bank teller application • components - loan component, savings bank component (with withdrawal / deposit), account manager (to create new accounts). • Service - the interfaces of all components (group) can be composed and exposed as services - creation of new accounts, withdrawal and deposit services and loan service.

  15. SUPPORTS SERVICES BUSINESS GOALS HAS SERVICE DESCRIPTION COMBINED DYNAMIC RECONFIGURATION CHOREOGRAPHY

  16. Service layer – collection of units of work (interfaces) Processing logic Component layer – operations that are units of work. SLA Object layer / legacy – Messages for communication (Operational) UI, Business processes, Service Layer, Component Layer, Object Layer PRESENTATION – portal for aggregation of contents to users Business Process Layer Automation logic Orchestration of services.

  17. Terms in SOA • Services • Service provider • Service consumer (or Service requestor • Service locator or service registry • Service broker – passes service requests to one or more service providers.

  18. CREATION OF SERVICES FROM EXISTING / new COMPONENTS Expose COMBINE EXISTING SERVICES Business Drivers USE SERVICES Incremental Iterative Consume Compose SOA LIFE CYCLE Consumer view : Service identification Service Categorisation Service exposure Choreography QoS Provider view : Component identification Component Specification Service realisation Service management Standards Implementation

  19. Advantages • standardisation • Faster time to market • Operational efficiency and adaptability • Agility to collaborate • Continuous improvement • Aligns business to IT • Ease of introducing new technologies • Return of Investment (ROI) • Vendor diversity • Services – encap, loose coupling, contract, reuse, composability, autonomous, dynamic, higher granularity

  20. Business Process Service Registry Policy Security Transaction Management Service Service Description Service Communication Protocol (ESB) Transport layer SERVICE ORIENTED ARCHITECTURE

  21. Problems in Web services (Point – Point) • Service consumers need to be modified whenever the service provider interface changes. (dynamic) • Every consumer should have a suitable protocol adapter for each provider it is connected to. (interoperability) ESB • ESB acts as a mediator that transforms, routes, notifies and augments information. • It provides virtualization of the enterprise resources. • The Enterprise Service Bus is an enterprise-class messaging bus. • It has the following facilities: • messaging infrastructure • message transformation facility between consumer and provider • Content-based routing between service consumers and providers. • Capability to convert transport protocols between consumer and provider.

  22. Business Process (BPEL) Service Registry (UDDI) Policy (WSPolicy) Security (WSSecurity) Transaction (WSTransaction) Management (WSManageability) Service Service Description (XML, WSDL) Service Communication Protocol (SOAP) Transport layer (HTTP, JMS, SMTP) SOA based Web services

  23. Responders SAHANA PRESENTATION / UI Office Systems Laptop/PDA/Cell Web Client Wired Mobile Internet Channel Access Match Shelter SMS Person Org Camp Requests Place Alerts Family Services Person Aids Search Vol Search Match BUSINESS PROCESSES Missing person Org Reg Camps Reg Request Mgmt Shelter Reg Mobile BUSINESS SERVICES OFFERRED BY SERVER GRID Search procedures DDoS and Load Balancing

  24. Missing person’s registry with efficient search • Organisation registry with efficient match and volunteer coordination • Camps registry • Request management registry with inventory management and optimisation – search • Shelter registry • Messaging alerts • Damages registry • Grid management module to manage coordination efforts among districts and relief organisations • Bulletin board – user area

  25. SOA – screen shots1. Organisation Registry • New Organization Registration with the System • Maintaining details about each organization with unique ID • Updating Organization’s services

  26. DESCRIPTION • When a Organization wants to provide service it must provide the Organization name, city, branch to the system • By Default, every Organization that registers for the first time has to provide a single service • On successful registration, an automatically generated Organization Id will be displayed to the Organization authority • To update the service provided, both Organization ID and password are validated • The various services are displayed in the form and from which Service provider have to select their additional service

  27. REGISTRATION SYSTEM SERVICE PROVIDER NEW ORGANIZATION REGISTRATION: ORG NAME CITY BRANCH SERVICE ORGANIZATION DB UPDATION ORGANIZATION ID

  28. SERVICE PROVIDER REGISTRATION SYSTEM ORGANIZATION’S SERVICE UPDATION ORG ID AND PASSWORD RECORD RETRIVAL AND VALIDATION VALIDATION RESULT SERVICES LIST SELECTED SERVICE SERVICE UPDATION SERVICE INFROMATION UPDATED FORM

  29. BUSINESS PROCESSES • Service Provider registers to the system • Service provider login validation • Services updating FORMS 3 X Forms • LOGIN XFORM • ORGANIZATION DETAILS XFORM • SERVICE UPDATED XFORM

  30. BUSINESS PROCESS

  31. LOG IN X FORM

  32. ORGANISATION DETAILS X FORM & GETTING DETAILS XML

  33. SERVICE UPDATED X FORM

  34. SERVICE SELECTION XFORM

  35. DATABASE RELATIONSHIPS

  36. GRID Heterogeneous systems, HTC VO – trust groups, dynamic, cross organisational Geographically dispersed Resource sharing Scientific, distribution of work among all resources CLOUD Heterogeneous systems , HPC On demand resource provisioning over Internet Data centric with grid backbone, utility value Elastic , Business, full utilization of resources High Throughput Computing Distributed Computing, loosely coupled Disparate Autonomous heterogenous systems Computation intensive – Sharing , single adm High Performance Computing Tightly coupled, fine grain parallelism Homogenous Systems high computing power, short period Low latency communication P2P Mainly for file sharing Geographically dispersed peers Autonomous nodes Decentralised Clusters Resource sharing Close to each other, Usually homogenous Centralised control, cooperative working Shared Memory Computing Parallel systems, multicore Divide and conquer synchronization Tightly Coupled Virtualisation System integration Virtualisation Viewing a single system as multiple resources Web Services Application integration Separation of concerns Data integration, interop Multi tenancy Sharing a resource among multiple clients

  37. Some Characteristics of Grids Numerousresources Owned by multiple organizations & individuals Connected by heterogeneous, multi-level networks Different security requirements & policies Different resource management policies Geographically separated Unreliable resources and environments Resources are heterogeneous

  38. write (code) to solve problem “compile” against middleware submit to Grid security advertise Stage data accounting Deploy toresources Selectresources Steering andvisualisation Stages to using the Grid – Classical View middleware

  39. Technical capabilities Resource modeling Monitoring and notification Allocation Provisioning, life-cycle management, and decommissioning Accounting and auditing security

  40. G2 Fabric layer: Provides the resources for shared access Connectivity layer: Core communication and authentication protocols Resource layer: Protocols for secure negotiations, initiation, monitoring control, accounting on individual resources. Collective Layer: Protocols and services to capture interactions among a collection of resources. Application Layer: User applications that operate within VO environment.

  41. G3- Services - OGSA • Service based infrastructure for grid • Grid aims to integrate, virtualize, and manage resources and services within distributed, heterogeneous, dynamic “virtual organizations” • Standardization is critical to create interoperable, portable, secure robust, scalable and reusable components and systems • Goal is to standardize grid services by specifying set of standard interfaces. • Aims to develop a common , standard and open architecture for grid based applications. • Service-oriented architecture, based the Open Grid Services Architecture (OGSA), addresses this need for standardization by defining a set of core capabilities and behaviors that address key concerns in Grid systems. • OGSA is based on Grid Service ( extension of web service) .

  42. OGSA realizes the logical middle layer in terms of services, the interfacesthese services expose, the individual and collective stateof resources belonging to these services, and the interactionbetween these services within a service-oriented architecture (SOA). • The architecture is not layered, • Services are loosely coupled peers that, either work single or part of an interacting group of services,

  43. OGSI • Requirements not met in Web services were implemented as Grid services confirming to OGSI specifications • OGSI specification defines • How grid service instances are named and referenced • How the interfaces and behaviors are common to all Grid services • How to specify additional interfaces, behaviors and extensions • GWSDL (Grid WSDL) • Introduces Service Data Elements (SDEs) • portType inheritance • Grid Service Handle (GSH) • Grid Service Reference (GSR) • Factory • Handle resolver • Notification • Service groups (light-weight registries)

  44. Service relationships

  45. Grid vs Web services • Web Services • Messages exchange • Documents • No notion of “pointer” • Service orientation? • Grid Services • The architecture encourages everything to be exposed through an interface rather than being sent as a document • GSH is the “pointer” • Object orientation? (CORBA?) • 2-level naming scheme – GSH and GSR • SDE – Web services static discovery vs SDE – dynamic • Instantiation and life cycle management - factory

  46. STATEFUL WEBSERVICE

  47. 1 2. CREATE 3