Glexec, SCAS & CREAM

Milestones

• CREAM-CE capable of large-scale direct job submission

• Glexec & SCAS capable of large-scale use on WN in logging only mode

• Show CREAM-CE/glexce/SCAS at scale– Support direct job submission– Support WMS job submission

glExecPPS: On WN with setuid OK for small scale deployments.Logging only mode not working

Large scale WNDeployment (needs SCAS)

SCAS

PATCHFailed

certification

CREAM CEReleased – but not advertisedDeployed on 2 sitesALICE experience OKPPS: On plenty of sites

PATCH Ready for Certification:WN Proxy Renewal

Large scaleDirect

SubmissionDeployment

CREAM UIUsed by ALICEFrom VO BOX

Large scale directMulti-User Pilot Jobs

WMS

PATCHPassed Certification:Has untested ICEBug fix patchentering certification

Large scale WMSMulti-User Pilot Jobs

Condor-G CREAMSimple submission workingMoving through failure cases

Authorization Service

• Components:– PAP (Administration): Core functionality complete– PEP (Enforcement): Complete. Developer testing– PDP (Decision): Started

• Integration & Scalability Testing– January & February 2009

• Enter Certification– Mid-March 2009 subject to satisfactory testing

Deployment (In Discussion)

• Incremental deployment– No big bang

• Local Deployment– No external dependencies. Local configuration

• Remote Policy checks– Pull in remote policy from OSCT

• Perform Authz checks during WMS site selection– Sends requests to sites or sites release policy to WMS

• Further details from recent SA3/JRA1 session– http://indico.cern.ch/getFile.py/access?

contribId=18&sessionId=8&resId=0&materialId=slides&confId=42513

Summary

• Priority remains glexec/SCAS/CREAM integration & deployment at scale– When independent components are proven

• Authz Service in EGEE-III DoW– Will be integrated & deployed when ready• Load tests needed for CREAM integration

– Activation will be incremental & can be site specific