gLite and the VO-Box Concept

9
INFSO-RI-508833 Enabling Grids for E-sciencE www.eu-egee.org gLite and the VO-Box Concept Erwin Laure, CERN On behalf of the EGEE Design Team Joint OSG and EGEE Operations Workshop September 27-29, 2005

description

gLite and the VO-Box Concept. Erwin Laure, CERN On behalf of the EGEE Design Team Joint OSG and EGEE Operations Workshop September 27-29, 2005. gLite Key Concepts. Centered around VOs - PowerPoint PPT Presentation

Transcript of gLite and the VO-Box Concept

Page 1: gLite and the VO-Box Concept

INFSO-RI-508833

Enabling Grids for E-sciencE

www.eu-egee.org

gLite and the VO-Box Concept

Erwin Laure, CERNOn behalf of the EGEE Design Team

Joint OSG and EGEE Operations WorkshopSeptember 27-29, 2005

Page 2: gLite and the VO-Box Concept

Joint OSG and EGEE Operations Workshop 2

Enabling Grids for E-sciencE

INFSO-RI-508833

gLite Key Concepts

• Centered around VOs– It’s ultimately the VO who gets resources allocated and need to

decide how to best use them (share them among the VO users)

• Distinguish between infrastructure and VO services

• Infrastructure services– Operated and trusted by the resource administrator– Implement site policies

Including what share of the resources are allocated to a VO

– Provide the required security, auditing, and accounting – Grid and standard services

E.g. batch system, gatekeeper, gridFTP, …

Page 3: gLite and the VO-Box Concept

Joint OSG and EGEE Operations Workshop 3

Enabling Grids for E-sciencE

INFSO-RI-508833

gLite Key Concepts

• VO services– Implement intra-VO policies

Scheduling, priorities, etc.

– Managed and operated by a VO Typically by sites on behalf of VOs A service instance may serve multiple VOs

– Currently mostly higher level services Resource brokers, catalogs, …

– There is the need of deploying VO services closer to the resource Better information about the resource and better control

about the resource Downside: more and more services to be deployed at the

sites – see discussion later on

Page 4: gLite and the VO-Box Concept

Joint OSG and EGEE Operations Workshop 4

Enabling Grids for E-sciencE

INFSO-RI-508833

VO Service Issues

• Need for management– Installation, updates, start, suspend, resume, stop, …

• Need for persistance– Restart in case of failures, machine reboot etc.

• Assure availability– Service replication etc.

• Adhere to site security, auditing, accounting, etc. policies

• These issues are well known in distributed systems – what complicates it for the Grid are the different administrative domains, local policies, dynamic nature and amount of VOs (and hence of VO services)

• VO services should not add additional complexity to the management of the resources.

• gLite approach tries to address these issues taking site concerns into account

Page 5: gLite and the VO-Box Concept

Joint OSG and EGEE Operations Workshop 5

Enabling Grids for E-sciencE

INFSO-RI-508833

Example: current gLite CE

LSF PBS/Torque

Condor

GT 2 Gatekeeper

LCASLCMAPS

WSS

CEMon

Condor-CBlahpd

NotificationsLaunch

Condor-CLaunch

Condor-C

Submitjob

Localbatchsystem

CE

Grid

Should evolve into a VO scheduler

InfrastructureService

VOService

Page 6: gLite and the VO-Box Concept

Joint OSG and EGEE Operations Workshop 7

Enabling Grids for E-sciencE

INFSO-RI-508833

Managed Services

• VO services need to be Managed Services

• Ensure they don’t consume more resources as allocated• Provide persistency and management functions (start, stop,

suspend, resume)• Adhere to site security, auditing, and accounting policies

• All that could be done by site admins but it would be favorable to have infrastructure services taking care of that

Page 7: gLite and the VO-Box Concept

Joint OSG and EGEE Operations Workshop 8

Enabling Grids for E-sciencE

INFSO-RI-508833

Managed Services Architecture

Authorization & configuration policies

Managed Service Factory

Resource Manager

Man

agem

ent

Cli

ents

Managed service factory functions Resource

manager commands

(Managed services)

Monitoring & enforcement

Man

aged

S

ervice C

lients

Page 8: gLite and the VO-Box Concept

Joint OSG and EGEE Operations Workshop 9

Enabling Grids for E-sciencE

INFSO-RI-508833

Example: future gLite CE

LSF PBS/Torque

Condor

GT4 Gatekeeper(Factory)

Localbatchsystem

CE

Grid

InfrastructureService

VOService

Condor(Resource Manager)

LCASLCMAPS

WSSVO Service(Condor-C)

BlahpdSU/Exec

(GT4, gLite, …)

CEMon

Page 9: gLite and the VO-Box Concept

Joint OSG and EGEE Operations Workshop 10

Enabling Grids for E-sciencE

INFSO-RI-508833

Summary• VO-Box is very similar to the Managed Service concept

– We believe the VO managed service concept is crucial to the success of Grid technologies

• gLite introduces some (existing) infrastructure services to allow managed computation taking into account– Dynamic service creation– Service monitoring and management– Enforcement of security, auditing and accounting policies– Not a replacement of current infrastructure, but rather leverage it

• First prototyping performed in the gLite CE but the concept is general enough to be used for any kind of VO service.

• Close collaboration with Condor and Globus will help in interoperability with OSG edge services– VM based workspace concept of OSG is compatible with the gLite

concepts. Provided VM technologies proof to be efficient enough gLite can be extended towards them.