OGSA-Basic Services

Prof S.Ramachandram

Outline

Introduction Common Management Model Policy Architecture Security Architecture Metering and Accounting Distributed Data Access and

Replication

Network

OGSA Enabled

Storage

OGSA Enabled

Servers

OGSA Enabled

Messaging

OGSA Enabled

Directory

OGSA EnabledFile

Systems

OGSA Enabled

Database

OGSA EnabledWorkflo

w

OGSA Enabled

Security

OGSA Enabled

Web Services

OGSA – Open Grid Services Architecture

OGSI – Open Grid Services Infrastructure

Grid Data Services Grid Core

Services

Grid Program Execution Services

Domain Specific Services

OGSA Architected Services

Applications

Open Grid Services Architecture (OSGA)

Open Architecture

Enabled Hardware and Operating System Platforms

Enabled “general purpose” middleware

Support for web services on a

variety of platforms, languages and

protocols

Open architecture forinteroperability

Open and value-addedvendor implementations

Applications & systemsbuilt on standards

The OGSA Platform

OGSI

TransportProtocolHosting EnvironmentHosting Environment

Host. Env. & Protocol Bindings

OGSA Platform services: registry,authorization, monitoring, data

access, etc., etc.

More specialized &domain-specific

services

Models for resources &

other entitiesO

therm

odels

Environment-specificprofiles

Domain-specificprofiles

OGSAPlatform

GWD-R (draft-ggf-ogsa-platform-3) Editors:Open Grid Services Architecture Platform I. Foster, Argonne & U.Chicagohttp://www.ggf.org/ogsa-wg D. Gannon, Indiana U.

Network

OGSA Enabled

Storage

OGSA Enabled

Servers

OGSA Enabled

Messaging

OGSA Enabled

Directory

OGSA EnabledFile

Systems

OGSA Enabled

Database

OGSA EnabledWorkflo

w

OGSA Enabled

Security

OGSA Enabled

Web Services

OGSA – Open Grid Services Architecture

OGSI – Open Grid Services Infrastructure

Grid Data Services Grid Core

Services

Grid Program Execution Services

Domain Specific Services

Open Architecture

Enabled Hardware and Operating System Platforms

Enabled “general purpose” middleware

Support for web services on a

variety of platforms, languages and

protocols

Open architecture forinteroperability

Open and value-addedvendor implementations

Applications & systemsbuilt on standards

Web Services Evolution

OGSA Architected Services

Applications

WS-Addressing

WS-TransactionWS-Notification WS-Security

WS-Trust

Open Grid Services Architecture (OSGA)

OGSA Manageability

Management is a high-priority OGSA effort GGF Common Management Model (CMM) WG

Goal: Define standard schema and interfaces for a

manageable resource (modeled as a service) And also:

Allow existing models to be used & exposed Leverage CIM schema when applicable Define how CMM interfaces can integrate with higher-

level interfaces (e.g., provisioning)

Common Management Model

A manageable resource is a Grid service, thus Global resource names: Grid service handles State data modeling + access: SDEs Lifetime management Service Group for grouping resources Interface definition language: WSDL

Plus additional schema & operations Standard manageable resource SDE schema Interfaces for extensible lifecycle and relationship

management BaseManageableResource interface

Manageable Resource Facade

Grid Service Façade

ToManaged Resource

Manageability Interface

Domain SpecificInterface

ResourceGSH

CMM Specification

Defines three aspects of manageability An XML schema(XSD) for modeling the

resource manageability information A collection of manageability portTypes Guidelines for modeling resources

New Constructs for Resource Modeling

Defines additional data types New data types: Counter and gauge

CMM defines new data types Versions related Unit related Lifecycle characteristics

Base Manageable Port Types

GridService

Locate Relationship LifecycleModel

BaseManageableResource

ServiceGroupHandleResolver

OGSA port types

CRM port types

SDE in Base Management portType

LifeCycleModel currentLifeCycleState serviceGroupType searchProperty relatedInstance relatedType

Basic Manageability Port Types

Needed to manage the resource lifecycleModel relationship locate

Others defined From CIM schema, e.g., opererational

operations (start/stop/resume/pause) By OGSO spec, e.g. grid service,

notification By other OGSA components, e.g. policy,

logging/metering

lifecycleModel Port Type:A Container for Lifecycle States There may be multiple models, but only one for

a given resource’s port type Example: Get/set resource’s lifecycle state

down, starting, up, stopping, failed Each state has additional info, e.g.,

up state: idle, busy, degraded

Down Starting

UpStopping

Failed

Relationships & Dependencies Relationships describe existence and type of

connections between resource instances Relationships are discovered through the

relationship port type and its relatedResource service data element

Relationship port type allows a view of relationships as they are known by the resources at each end of the relationship

Set of predefined relationship types Hosts, Contains, Federates, Aggregates, Uses,

Implements

Locate Port Type Provided to help in the location of manageable

resources of a given type Contains two service data elements

serviceGroupType, port type that provides the ServiceGroup function for manageable resources of this type

searchProperty, zero or more service data elements that are likely to be used for searching for a manageable resource, and are thus worth caching in the manageable resource registry

Service Domains

High-level abstraction model to describe the behaviors, attributes, operations, and interfaces to allow a collection of services to function as a single unit.

Service Domains

Service Orchestration Engine

Service dispatch

Service Registry

Policy

Private registries

Incoming message

Outgoing Message/events

Provided Services

Service Domains: Components

Service Registration and Collection Service Routing and Selection Service interoperation and

transformation Flexible service composition Automatic service orchestration Note:Uses OGSI ServiceCollection port

Type.

Service Domains: behaviours

Filter Selection Topology Enumeration Discovery Policy

Policy Architecture

Provides a framework for creating, managing, validating, distributing, transforming, resolving, and enforcing policies in distributed environment.

Policy Architecture

PolicySet PolicyRule PolicyGroup PolicyCondition PolicyAction

Levels of Policy Abstractions

Business Level Domain Level Device Level

Security Architecture

Integrate(Extensible architecture)

Interoperate Trust

OGSA ArchitectureSecurity Components

Bindings Security(transport, protocol, message security)

Credential and Identity Translation

(Single SignOn)

User Management

Key Management

Intrusion Detection

Service/End-point Policy

Audit &Non-repudiation

Anti-virus Management

Se

cure

Lo

gg

ing

Tru

st M

od

el

AuthorizationPolicy

Privacy Policy

Secure Conversations

Policy Expression and Exchange

Policy Management(authorization,

privacy, federation, etc)

MappingRules

Access ControlEnforcement

Metering and Accounting

OGSA proposes utilization CMM for metering and accounting

Metering Resource Consumption

At what granularity do services report resource consumption?

How do they report it? How are services metered?

Billing

Con

trac

t Ser

vice

Accounts

Rate Packages

ASPIC CBI

ASPIC CBI

Resource Instrumentation

Metering Handler

Logging Service

Rating

Meter event adaption

Billable Record Listener

Aggregation and Correlation

Usage Information

Accounting

Common Distributed Logging

Viewed as messaging application Can be

Informational Trace Error debug

Separates implementation from service

Common Distributed Logging

Faculties to be provided Decoupling Transformation and common representation Filtering and aggregation Configurable consistency Consumption patterns Secure logging

Distributed Data Access an Replication

Data Access Service Data Replication

Group services for clustering and failure Utility Computing for Dynamic Provisioning Policy Services for QOS requirements Metering and Accounting High-level services such as workload

management and disaster recovery servicesWorking group called OGSA-DAIS is formed to look

into these aspects of data management.

DBMSDBMS

DB

Logical OGSI Grid Resources

Data Resource ManagerData Resource Manager

Data ResourceData Resource

Data Activity SessionData Activity Session

Data RequestData Request

Data SetData SetResult Set

External Data Resource Manager

External Data Resource

External Data Set

Figure 10.12: The external resources and Logical resources of database management system

bind

Data resources manager

(DRM)

Data resources manager

(DRM)

EDRM

EDRM

External data resource manager(EDRM)

External data resource manager(EDRM)

bind

Figure10.13: Conceptual model for data resource manager grid service

EDRM EDRMEDR

EDR

EDRMAEDRM

Data Resources Manager

(DRM)

Data Resource

(DR)

bind

bind

Figure10.14: A Logical data resource

EDRM

Data resource(DR)

Data set(DS)

Data resource manager

(DRM)

EDR

EDR

bind

bind view

EDRM

Figure10.15: A logical data set

OGSIGrid Service

OGSI Service Group

OGSIFactory

Resource Manageable

Interface

Standards not defined by DAIS

Standards not defined by DAIS

General across all types of data access DAIS

defined

General across all types of data access DAIS

defined

Specific to a type of Data access DAIS

defined

Specific to a type of Data access DAIS

defined

Extensions notDefined by DAIS

Extensions notDefined by DAIS

Data Set Data Resource Manager

XMLDataSet

ADODataSET

XML Data Set

File Stream

Binary Stream

Data Object

Oracle Data Resources Manager

DB2DataResourcesManger

Figure10.16 : A logical port Type functionality separation

Grid Principles – OGSA and ?

?