OGSA V1 Document (p19)

Workload Mgmt.

Framework

User/Job

Proxies

Environment

Mgmt.

Policies

“Supply ”“Demand ”

CMM

Resource Mgmt. Framework

Reservation

Optimizing Framework

Resource Selection

Resource – Workload

Optimal Mapping

Workload Optimization

Workload Post Balancing

Resource Provisioning

Workload Optimizing Framework

Workload Optimization

Workload Orchestration

Workload Models (History/Prediction)

Dependency management

Scheduling Resource Optimizing Framework

Capacity Management

Resource Placement

Primary Interaction

Meta - Interaction

Represents one or more OGSA services

Resource

Allocation

(or Binding)

Job

Factory

Admission Control (Resources)

Admission Control (Workload)

SLA Management (Workload)

Quality of Service (Resources)

Queuing Services

Resource

Factory

Information Provider

Selection Context (e.g. VO)

Terminology

• What is a job? Job made of multiple tasks– Task: Single unit of work– Job: Multiple tasks

• GT2: DUROC: Link tasks with barriers etc.

• GL: App=set of jobs, jobs=set of process

• COG: GridAnt (client side)

• SF: One provisioning jobs

OGSA Diagram

• Confusing:– What are all the services doing?– Allocation: Implementation of Auth policy with

required resource.– Difference between Reservation & Resource

Allocation

Duplication (P19)

• Workload Mgmt Framework– Proxies– Job factory– GL: GRMS (Job Submission)

• Resource Mgmt Framework– Information Provider (Glue Schema, class ad, JDL)

• Feed into MDS and other infor systems

– Resource factory (Provisioning?)• SmartFrog

– Reservation (Very Basic concepts, Research level)

• Workload Optimisation Framework (DRM)– Submit & monitoring & control job

• E.g. kill, suspend, signal sending

• Resource Optimisation Framework– Admission Control (gridmap, or equiv.)

• Admission Control

• Workload Optimisation/Meta-Scheduling– ICENI, GRMS, CSF

User Functionality: Capability

• Security Context (e.g. Identity) Manipulation• Submit, Control & Monitor Jobs• Monitoring/Testing of the System• Manipulating Remote File System

– e.g. GridFTP

• ‘Virtual’ File Store & meta-data manipulation– e.g. RLS, WinFS– Better the viewing of the meta-data the FS

structure becomes irrelevant

The ImplementationsWhere are the differences?

• Geodise Matlab, Jython & Python environments– Gridmap: System Control– ACL on files in VirtualFS: User Control– Job Monitoring Capability– Explicit heartbeat & health monitoring

• GT2, GT3 & GT4 command line tools– Replica & meta-data services– Authorisation services– Infrastructure Discovery & Monitoring (soft state reg.==heartbeat)

• GAT (Grid Application Toolkit) implemented by GridLab– Resource Discovery (built on top of MDS & GRMS)– Registry for jobs, files, … or any object/endpoint!– Monitor all of the above objects.– Reservation API

• ICENI– Scheduling, performance & reservation support/implementation

What is being used beyond WS-I (/5)

• WS-Security [Username/PW/X509] (5)• WS-Addressing (3.5)• WS-Trust (2.5)• WS-SecureConversation (2.5)• JSDL (2)• WS-Notification (1.5)• WS-RF (1.5 – average)

– WS-BaseFaults (2)– WS-ResourceProperties (2)– WS-ServiceGroup (1)– WS-ResourceLifetime (1)

• WS-Eventing (1)