GDB 11th May 2011

From GridPP Wiki
Revision as of 08:30, 17 May 2011 by Jeremy coles (Talk | contribs)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

GDB agenda page:http://indico.cern.ch/conferenceDisplay.py?confId=106644.

Topics.

INTRODUCTION

Meetings - EGI Virtualisation and Clouds Workshop takes place 12-13th May . WLCG workshop 11th-13th July at DESY HEPiX fall meeting 21st-26th October in Victoria CHEP 2012 21st-25th May NYC

    • The May report will use an OR of CREAM and LCG-CE. SGE will be working with CREAM availability in June/July so all sites must run CREAM by then to avoid 0 in the availability figures at that point **

INFORMATION SYSTEM

Flavia Donno is leaving. New IO is Lorenzo.Dini @cern.ch.

There is a use case document that needs to be reviewed: https://twiki.cern.ch/twiki/pub/LCG/WLCGISArea/WLCG_IS_UseCases.pdf. The new semi-static BDII has been tested and helps tame variations, but wider testing needed.

ATLAS

ATLAS is developing an Atlas Grid Information System (AGIS). Not replacing BDII information but adding additional information such as:

Cloud and Tier level -- T2D • DDM endpoints (e.g. acl and quotas for groups) • PanDA queues • Frontier/Squid service info and ATLAS specific configuration

CMS - find IS rarely up-to-date enough to be useful.

LHCb - no new requirements for WMS. Moving more towards direct submission.

Lorenzo has the task now of collecting future requirements.

HEPiX

Virtualization and Clouds. Working group updates (group started 18 months ago). Good contact with and recommendations responses from StratusLab. Will focus on reuse of StratusLab Marketplace.

Other topics were IPv6; Oracle Sun issues; benchmarking activities with 64-bit and virtualisation.

Fall meeting TRIUMF October 24th-28th.

EOS UPDATE

EOS development complements CASTOR at CERN in the disk pool area. It is decoupled from the archive (no automatic tape connectivity). CASTOR will stay fully supported.

Can EOS be used outside of CERN? Short answer no not yet though software is in a public repository but there is no support manpower. After first deployment should review interest. EOS is tackling scalability and performance issues for the T0. Too early to speculate about whether this solution will ever be of interest outside of CERN. Still need to evaluate performance and will report at future GDBs.

MUPJ – GLEXEC UPDATE

Testing status for ATLAS (Jose Caballero) /atlas/Role=pilot job + glexec test, is in progress at T1s. Testing for CMS (Claudio Grandi) basically looks okay. Issue with wrappers (perl Zlib problem breaks the standard glexec wrapper scripts). Workarounds/fixes soon. LHCb preparing DIRAC code to report glexec failures (ready in weeks).

https://twiki.cern.ch/twiki/bin/view/LCG/GlexecDeployment gives more deployment details for glexec on WNs.

Relocatable dist: Receipe to rebuild glexec from sources. Configuration file needs to be in root.

SGE issues fixed in EMI-1 release.


CREAM UPDATE Over half WLCG resources now appear under CREAM. Removing LCG-CEs needs to be agreed but will happen soon.

OTHER MIDDLEWARE UPDATES

DPM 1.8.0-2 has been released to gLite 3.1 / SL4 - FTS 2.2.5 has been certified at least for gLite 3.2 / SL5

(for the other platforms the patches are not marked as such) - new patches for the gLite 3.2 UI and WN are in preparation;

the WN patch will in particular address the known issues of

the previous update

Links:

https://twiki.cern.ch/twiki/bin/view/EGEE/LCGprioritiesgLite#gLite_ status_presented_in_the_Ti

http://bit.ly/22we3i


WLCG MIDDLEWARE SUPPORT

How do we get the lost requirements back? How do we establish a fast feedback loop? How do we manage WLCG middleware work?


EMI 1 and WLCG

HEPiX Virtualisation Working Group

The working group has made good progress with VM image exchange policies. Not such good progress (though better in recent months) in delivering distributed catalogue of endorsed images.


CLOUD COMPUTING AND VIRTUALISATION

ALICE: Cloud computing is not currently a priority. Main concern for ALICE is how storage is handled.

ATLAS is interested in both. There is R&D in ATLAS evaluating cloud technologies (including academic clouds and commercial clouds). Dedicated on CVMFS and multicores.

On virtualisation CMS is not interested per-se. But CMS has nothing against sites using virtualization provided CMS requirements are met. More interest in whole-node reservation.

LHCb: Questions about using pilots with VMs… interested in a generic cloud interface (makes things simpler). Ideally the VM could run as long as necessary… and would not have to be shutdown after every job.

DPM NAGIOS & PUPPET New probes available.