VO Privilege Activity

VO Privilege Activity

• The VO Privilege Project develops and implements fine-grained authorization to grid-enabled resources and services

• Started Spring 2004• Sposored by US CMS (Fermilab) and US ATLAS

(BNL)• People: Fermilab, BNL, PPDG• Technologies: VOMS, VOMRS, Gridmap and

SRM/DCache callout interface, GUMS, gPLAZMA, and SAZ

VO Privilege ActivityMotivations

• Improve user account assignment at grid sites– Make user-to-account mapping flexible and

dynamic, using remote Grid Identity Mapping Services

– Base user-to-account mapping on both user role and least privilege access

• Reduce account management administrative overhead

GUMS

Local or Remote ClientProxy with VO Membership | Role Attributes

Site-wide Assertion Service

Site

SAZ

VOMS

Site-wide Mapping Service

Auxiliary Mapping Service

PRIMAC SAMLlibraries

CE

SE

gPLAZMAStorage

metadata

PRIMAJava SAMLgPLAZMA

PRIMAAuthorization

Service

Globus Gatekeeper PRIMAcallout

SRM-GridFTP gPLAZMA callout

gPLAZMALiteAuthorizationServices suite

VO Privilege ActivityArchitecture

Resource Selection Service (ReSS) Activity

The Resource Selection Activity

• The Resource Selector is a component of the OSG Job Management Infrastructure.

• The project started in Sep 2005 with a planned duration of 9 months

• Sponsored by PPDG as a DZero contribution to the Common Project

• People: Fermilab, OSG TG-MIG group, PPDG

The Resource Selection ActivityMotivations

• A Resource Selector allows…– …expressing requirements on the resources

in the job description• without a Resource Selector, the user is

responsible for selecting the resource for the job

– …the user to refer to abstract characteristics of the resources in the job description

• without a Resource Selector, the user must use concrete resource attribute values in the job description (e.g. to initialize the job environment)

The Resource Selection ActivityDeliverables

• The Resource Selection Activity has two major goals

1. Enable OSG resource usage by DZero. Jobs will be prepared and data will be handled by the SAM-Grid.

2. Develop and deploy a Resource Selection Service that VOs with requirements on job management similar to DZero can use.

The Resource Selection ActivityArchitecture

CondorMatch Maker

InfoGatherer

classads

CEMon

CE

Gate1

job-managersjob-managersjob-managers

jobs info

CLUSTER

CEMon

CE

Gate2

job-managersjob-managersjob-managers

jobs info

CLUSTER

CEMon

CE

Gate3

job-managersjob-managersjob-managers

jobs info

CLUSTER

classads classads classads

CondorScheduler

jobWhat Gate?

Gate 3

job

OSG Auditing Activity

OSG Auditing Activity

• The activity develops a system to record a suitable audit trail for grid services– Audit trail is a set of log entries to determine

who did what, when, where and how– Audit trail is critical for both debugging and

security investigations

• Started Winter 05

OSG AuditingGoals

• Provide tools to the site to gather audit events, process them, correlate them, in order to facilitate post-mortem investigations and malicious use detection – Security concerns impose that a site auditing service could allow

queries that do not expose much data (e.g. yes/no question such as: did this DN submit more than 10 jobs in the past 24 hours?). The feasibility/utility of across-site auditing is under investigation.

• Determining what has happened in a GRID environment– Chain of events to follow: user contacts a resource broker, which

submits to a gatekeeper, which starts a batch job, which execute on a node, which starts a file transfer, …

Auditing at a site(an example)

GridFTP

…

GKGRAM

Centralizedlogging

ParsingAuditingService

Allows to search through events and make correlation. The user will use a GUI or command line tools to navigate through the data, and will retrieve pointers to the actual log entries when needed.

We need to make sure the services actually provide enough information.

Some sites already have a way to collect and store logs, based on syslog or other standard practices. We want to leverage and integrate within the framework.

Site

Cyber security

OSG Accounting Activity

OSG Accounting Activity

• The goal of the activity is to develop a system to track the consumption of OSG services and resources user by user

• Sponsored by SLAC, Fermilab and PPDG

• Started Summer 2005

• More Info: google “osg accounting”

OSG Accounting ActivityMotivation

The OSG infrastructure must provide its users with precise and reliable information about resources consumption.

Availability of such information will • allow resource providers to directly link resources

consumption with VOs and science projects goals,• improve resource planning and organization at the

resource providers sites• eventually, support automatic resource allocations and

consumption based on an economic model.

OSG Accounting ActivityArchitecture

OSG Accounting Activity

OSG Edge Services Framework Activity

OSG Edge Services Framework Activity

• In OSG, services on the “Edge” of the Grid/Fabric site boundaries grant users access to site private services.

• Started in September 2005.• Collaboration: Physicists, Computer Scientists &

Engineers, Software Architects.• People: USALTLAS, USCMS, Globus Alliance,

ANL, U. Chicago, UC San Diego• Web collaborative area –

http://osg.ivdgl.org/twiki/bin/view/EdgeServices

OSG Edge Services Framework Activity Vision

OSG site provides access to a shared compute & storage cluster via two types of services. Those shared between VOs, and those that are VO specific.VO specific service deployment is made possible via a shared services framework.

OSG Edge Service Framework ActivityMotivation

• OSG has many VOs each with many different requirements

• Resources may be partitioned into specific, VO-dedicated servers along side shared, open grid services used by many VOs.

• Each VO may want to use different software to implement any particular kind of an edge service

• Each VO may put different requirements on edge service in terms of resource usage.

ESF - Phase 1

ESF

SECE

Site

CMS

Role=VO Admin

XEN vm

Based on XEN&

Gt4 work spaces

ESF - Phase 1

ESF

SECE

Site

CMS

Role=VO Admin

dom0

ESF - Phase 1

ESF

SECE

Site

Role=VO Admin

dom0

ESF - Phase 1

ESF

SECE

Site

Role=VO Admin

dom0

ESF - Phase 1

ESF

SECE

Site

CMS

Role=VO Admin

dom0

ESF - Phase 1

ESF

SECE

Site

CMS

Role=VO User

domU dom0

XEN

ESF - Phase 1

ESF

SE

Site

CMS

Role=VO User

CE

dom0domU

ESF - Phase 1

ESF

SECE

Site

CMS

Role=VO User

dom0domU