The Open Grid Services Architecture, Version 1.0

1
The Open Grid Services Architecture, Version 1.0
2
Index

• Abstract
• Introduction
• Requirements
• Capabilities
• Overview
• OGSA Framework
• Infrastructure Services
• Execution Management Services

3
Abstract

• Produced by GGF (Global Grid Forum)
• Provide first version
• Capabilities
• Execution Management
• Data
• Resource Management
• Security
• Self_management
• Information

4
Introduction

• Grid system and application aim
• Integrate, virtualize and manage resources and
  services
• With in distributed, heterogeneous, dynamic
  virtual organizations
• Issues as
• How do I establish identity and negotiate
  authentication?
• How is policy expressed and negotiated?
• How do I discover services?
• How do I negotiate and monitor service level
  agreements?
• How do I organize service collections
  hierarchically so as to deliver reliable and
  scalable service semantics?
• How do I integrate data resources into
  computations?
• How do I monitor and manage collections of
  services?

5
Introduction (cont.)

• Chapter 2 is abstract definition of the set of
  requirements
• Chapter 3 translate the requirements of Chapter 2
  into a coherent set of capabilities
• Execution Management, Data, Resource Management,
  Security, Self-Management and Information
  services

6
Requirements

• Table 1 The OGSA use cases
• Using these case, summarize our finding in the
  following sections.
• Interoperability and Support for Dynamic and
  Heterogeneous Environments
• Resource Sharing Across Organizations
• Optimization
• Quality of Service (QOS) Assurance
• Job Execution
• Data Services
• Security
• Administrative Cost Reduction
• Scalability
• Availability
• Ease of Use and Extensibility

7
Requirement Intero Resource Sharing

• Intero
• Divers, heterogeneous, and distributed resource
  and services
• Support heterogeneous systems leads to
  requirements
• Resource virtualization
• Common management capabilities
• Resource discovery and query
• Standard protocols and schemas
• Resource Sharing Across Organizations
• OSGAs purpose is to support resource sharing and
  utilization
• Resource sharing requirements include
• Global name space
• Metadata services
• Site autonomy
• Resource usage data

8
Requirement Optimization QOS Assurance

• Optimization
• Demand-side optimization must be able to manage
  various types of workload
• Demand-side optimizations foundation is changing
  resource allocation and provisioning resource
  (monitoring and logging)
• QOS Assurance
• QoS assurance requirements include
• Service level agreement
• Service level attainment
• Migration

9
Requirement Job Execution Data Services

• Job Execution
• Must provide manageability for execution jobs
  throughout their LIFETIME (for heterogeneous
  resources)
• Required
• Support for various job types
• Job management
• Scheduling
• Resource provisioning
• Data Services
• Efficient access and movement data and data
  sharing is important
• Required
• Data access
• Data consistency
• Data persistency
• Data integration
• Data location management

10
Requirement Security Administrative Cost
Reduction

• Security
• Requirement
• Authentication and authorization
• Multiple security infrastructures
• Perimeter security solutions
• Isolation
• Delegation
• Security policy exchange
• Intrusion detection, protection, and secure
  logging
• Administrative Cost Reduction
• Policy-based management
• Application contents management (mechanisms)
• Problem determination (mechanisms)

11
Requirement Scalability Availability Ease
of Use

• Scalability
• Management architecture needs to scale to
  potentially thousands of resources of a widely
  varied nature
• High-throughput computing mechanisms are required
• Availabiliity
• Disaster recovery mechanisms
• Fault management mechanisms
• Ease of Use and Extensibility

12
Capabilities Index

• Overview
• OGSA Framework
• Infrastructure Services
• Execution management Services
• Objectives
• Approach
• EMS services
• Resources
• Job management
• Selection Services
• Interactions with the rest of OGSA
• Example Scenarios

13
Capabilities Overview

• Facilitate the seamless use and management of
  distrbuted, heterogeneous resources. (OGSA)
• Figure 1 show logical, abstract, semi-layered
  representation
• The first tier
• Base resource
• Physical or logical artifacts
• Locally
• The second tier
• Higher level of virtualization
• Logical abstraction
• Relatively invariant and standard
• Management resource (The first tier)

14
Capabilities Overview (cont.)
15
Capabilities Overview (cont.)

• The third tier
• Logical representation
• Application
• Other entities that use the OGSA capabilities to
  realize user oriented functions and processes
• Outside OGSA
• But drive the definition of the architecture from
  the use cases that the infrastructure should
  support

16
Capabilities OGSA Framework

• Logical middle layer (in Figure 1)
• OGSA services framework is shown in Figure 2, 3
• Cylinders represent individual services
• A few important points
• Important motivation for OGSA is the composition
  paradigm or building block approach
• Adaptability, flexibility and robustness
• OGSA represents the services
• Semantic/behavior and interaction of these
  services
• Software architecture is outside the OGSA working
  group
• The architecture is not layered (not
  object-oriented)
• Services are loosely coupled peers other services

17
Capabilities OGSA Framework (cont.)
18
Capabilities OGSA Framework (cont.)
19
Capabilities Infrastructure Services

• The Primary assumption is WS-Architecture
• So using WSDL, SOAP (XML)
• Web Service framework is not designing for Grid
  system
• So want to extension
• Building blocks the interfaces and behaviros
  defined by the WSRF, the refactoring of the OGSI
• Web Service Resource Framework (WSRF)
• Approach to modeling , accessing, and managing
  state and to expressing faults.
• Open Grid Services Infrastructure (OGSI)

20
Capabilities Execution Management Services (EMS)

• EMS addresses problems with executing units of
  work , including their placement , "provisioning,
  " and lifetime management.
• Objectives
• These problems include
• Finding execution candidate locations
• Selecting execution location
• Preparing for execution
• Initiating the execution
• Managing the execution

21
Capabilities Execution Management Services
(cont.)
22
Capabilities Execution Management Services
(cont.)

• Approach
• Figure 4 illustrates a generic framework.
• EMS services enable applications to have
  coordinated access to underlying resources
• EMS services are the key to making resources
  easily accessible to end-users
• First, not all services will be used all of the
  time.
• Second, it is not our objective in this document
  to completely define the services
• Third, we want to emphasize that these
  definitions and services will be applicable to
  general Web service execution
• Finally, we assume the existence of a resource
  handle.

23
Capabilities EMS Services Resources

• EMS Services
• Resources
• Model processing, storage, executables, resource
  management, and provisioning
• Job management and monitoring services
• Resource selection services
• Collectively decide where to execute a unit of
  work
• Resources
• Service Container
• To use reservation services, logging services,
  information services, job management services,
  and provisioning services
• Persistent State Handle Service (PSHS)
• To keep track of the location of persistent
  state.
• Has method to get a resource handle to
  persistent state
• Is not a data service.
• (? Metadata?)

24
Capabilities Job management Selection services

• Job management
• Job
• Is the smallest unit that is managed
• Named by resource handle
• keeps track of execution state
• Job manager
• Executing a job , set of jobs, from start to
  finish
• Selection Services
• Execution Planning Services (EPS)
• Is a service that builds mapping called
  schedules between jobs and resources
• Candidate Set Generator (CSG)
• Where is it possible to execute?
• Reservation Services

25
Capabilities Interactions with the rest of OGSA

• Interactions with the rest of OGSA
• details the interactions between the EMS and
  other parts of OGSA.
• Deployment Configuration Service
• Naming
• Information Service
• Attribute metadata about resources.
• Monitoring
• Fault-Detection and Recovery Services
• Auditing, billing and logging services
• Using logging file but billing is another problem
• Accounting

26
Capabilities Example Scenarios