1 / 13

WLCG Management Board Update: Network Issues, Security Challenges, and Middleware Developments

In the latest WLCG Management Board meeting held on December 7, 2010, key topics discussed included network problem resolution, security challenges in Tier 1 and Tier 2 sites, and updates on middleware components. The board tackled issues such as degraded network services and emphasized daily updates on high-priority tickets. Additionally, discussions covered GGUS enhancements, EGI's requests for middleware support, and capacity marketing from sites. The board emphasized the need for improved collaboration among NGIs and their accountability in managing site challenges.

umika
Télécharger la présentation

WLCG Management Board Update: Network Issues, Security Challenges, and Middleware Developments

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. GDB Update WLCG Management Board John Gordon 7th December 2010

  2. Main TopicsToday • Network ProblemResolution • Security Challenge 4 • Services BOF • Middleware • InstalledCapacity • HEPiX • CREAM • WLCG Information Officer

  3. Network ProblemResolution • Link failure handled OK, problems are with degraded service • Network contacts A & B are responsible for ensuring that there connection to external network and end-to-end link between sites are “clean” • Network contacts inform site contacts of change of state (preferably) or site contacts poll • Experiments request at least daily update of ticket and on all change of state – at least for those tickets marked high priority • Problem followed until solved • Escalation, if required, based on common WLCG timelines

  4. Security Challenge 4 • SSC4 challenged Tier1s and a handful of T2 with Panda jobs • Response improved leading to conclusion that sites need to be challenged to get them ready for real exposures • Done for T1s but challenge to do it for T2s • NGI responsibility • Launch a central challenge and have NGIs track it

  5. Services BOF@CHEP • Discussion on some key issues raised • Prolonged site downtimes – discussion of recent events & possible repercussions • GGUS categories: mainly “other” • Assign on submit (often unknown) or on close? • GGUS enhancements • “Escalation” of ticket type: TEAMALARM

  6. Several follow-up actions, such as GGUS enhancements, conditions, prolonged downtimes • Next CHEP will most likely be preceded by a full WLCG Collaboration Workshop with at least one workshop between now and then

  7. Middleware • Retirement dates for some glite3.1/SL4 components • EGI asked for a delay from January to March • Best efforts support negotiated for WLCG batch interfaces. Need to agree expectations. • There will be other middleware from WLCG (egxrootd GIP) . Should we have a WLCG Second Level Support • List of proposed changes of support teams for various glite components was controversial. No-one appeared to have been consulted. Neither those currently doing the support nor those supposed to take over. • Possible solution that EMI PTs adopt various orphan components. • Will EGI MWSU also adopt them?

  8. WLCG Information Officer • WLCG Information System • Not simply a BDII • WLCG Information Officer • Contact person to help improve reliability of the service and information provided • Interacting with experiments, sites, EMI, EGI, OSG, NDGF, WLCG management • First planning • Use case collection • Top Level BDII deployment strategy • Information consolidation and cleaning • Initial communication channels established (EGI, OSG, NGDF) • Questions? Send e-mail to Flavia.Donno@cern.ch WLCG Information Officer- 8

  9. InstalledCapacity • Most sites now publishing sensible cpu and disk numbers • Many do not publish cpu fair share to show LHC share of installed cpu. • T1s were asked to improve their T2s • Not much sign of this. • Reminder! • http://gstat-wlcg.cern.ch/apps/capacities/federations • Pledge Comparison • Have the information for a report

  10. HEPiX • IPv6 migration plans. IPv4 numberspace is about to run out (isn’t it always?), US Government has told all federal bodies to migrate this year. • Tomorrow’s GDB • Private Clouds, a number of sites implementing them. • EOS (Michel reported some critical comments of the project which were vehemently contested by CERN. Heated discussion in the room. • SL6 needs about 4 months work after RH release RHEL6 which is rumoured to be December 2010.

  11. CREAM • Real testing has now been done by most experiments • Alice already demand it • ATLAS use it in production when it exists • When will sites believe that they should install?

  12. December GDB • Experiment Operations • IPV6 • Security Update • CVMFS for Software Distribution • Middleware • Celebration Drink

  13. January GDB • DAaM Demonstrator Review • Wednesday 12thJanuary • Is half a day enough? • Argus • EMI Release 1 (?)

More Related