UKI Monthly Operations Meeting (TB-SUPPORT)

Wednesday 15 Mar 2006, 10:30 → 11:30 Europe/Zurich

VRVS - Fog VRVS room

Jeremy

Take place via VRVS - FOG virtual room

10:30 → 10:40 Progress with 2.7.0 upgrades

- Review of individual site progress and plans to upgrade. - Problems and experiences to be fed back to the CERN deployment team

Speaker: Jeremy

more information more information

10:40 → 10:50 Highlights from the pre-CHEP Service Challenge workshop!

- Experiment planning and expectations - Agreed functionality - Issues with the SRMs

Speaker: Jeremy/Alessandra/Graeme/Greig

document document

more information more information

10:50 → 11:00 Deployment plans for gLite 3.0

- The current planning for the next release after 2.7.0 which is named gLite 3.0 - What functionality will be in gLite 3.0 - Requirements for SC4

Speaker: Jeremy

transparencies transparencies transparencies

11:00 → 11:15 An update on GridPP preparation for SC4

- What have we achieved so far - What problems are being experienced that are likely to impact other sites moving forward - What is the timeline for future tests (see: http://wiki.gridpp.ac.uk/wiki/Service_Challenge_Transfer_Tests) - Other than achieveing throughput rates what are our objectives - Planning to get more sites involved/further developed (go here to find out what is involved: http://wiki.gridpp.ac.uk/wiki/Transfer_Test_Checklist)

Speaker: Deployment team

11:15 → 11:25 Network monitoring boxes

- A reminder of what the network monitoring boxes announced on TB-SUPPORT are for - Are there any issues with site security policies? - Information that is required to install/deliver them - Specific requests to sites - Q&A

Speaker: Robin Tasker?

11:25 → 11:30 AOB

- Advance notice of the SC4 Tier-2 tutorials and workshop to be held at CERN during the week of 12th June. Please see draft agendas: http://indico.cern.ch/conferenceDisplay.py?confId=1148 & http://indico.cern.ch/conferenceDisplay.py?confId=a058483 - Phasing out of SL3 scheduled for October 2006 - Sites should check that they are publishing "memory per job slot" not total memory.