In order to enable an iCal export link, your account needs to have an API key created. This key enables other applications to access data from within Indico even when you are neither using nor logged into the Indico system yourself with the link provided. Once created, you can manage your key at any time by going to 'My Profile' and looking under the tab entitled 'HTTP API'. Further information about HTTP API keys can be found in the Indico documentation.
Additionally to having an API key associated with your account, exporting private event information requires the usage of a persistent signature. This enables API URLs which do not expire after a few minutes so while the setting is active, anyone in possession of the link provided can access the information. Due to this, it is extremely important that you keep these links private and for your use only. If you think someone else may have acquired access to a link using this key in the future, you must immediately create a new key pair on the 'My Profile' page under the 'HTTP API' and update the iCalendar links afterwards.
Permanent link for public information only:
Permanent link for all public and protected information:
- This is the biweekly DTEAM & sites meeting
- The intention is to run the meeting in EVO: http://evo.caltech.edu/evoGate/. Join the meeting in the GridPP Community area.
- The phone bridge number is +44 (0)161 306 6802 (CERN number +41 22 76 71400). The phone bridge ID is 64688 with code: 4880.
Review of weekly issues by experiment/VO
-- Check on transfer problems http://hepwww.rl.ac.uk/nraja/UKUploadProblems/index.html
- Only Brunel now seeing problems?
- Experiment blacklisted sites
- Experiment known events affecting job slot requirements
- Site performance issues
-- September availability figures will be distributed shortly. We are aware of an issue whereby a problematic WMS has affected results.
Meetings & updates20m
- ROD team status (any points to raise to sites or issues to follow up?)
- Tier-1 update
- NGI support process... some recent problems in tickets submitted via GGUS reaching NGS/NGI colleagues who now support some of our services. This is being addressed but please raise any concerns quickly. One general comment, please provide as much information in the ticket as possible for the TPM to make a more accurate assessment.
- The most recent EGI Grid Ops meeting was yesterday: https://www.egi.eu/indico/conferenceDisplay.py?confId=182. Main item picked out by SP was: "Current deadline of 31.01.2011 for BDII on 3.1 means that the lcg-CE will loose support of critical component (resource BDII) then. As lcg-ce is still needed; so that's a problem".
- The next WLCG Grid Deployment Board will be on 13th October (the agenda is here http://indico.cern.ch/conferenceDisplay.py?confId=72063). Graeme is the T2 rep this month but any of you can join via EVO (WLCG community). Are there any issues for us to raise? Topics to be covered are:
Operational security - the recent vulnerability and response
Middleware - update on 3.1 decisions
Installed capacity - starting to assume that http://gstat-prod.cern.ch/gstat/summary/GRID/GRIDPP/ is now accurate for capacity (not jobs).
Then a series of talks on the Data Access & Management Demonstrators.
- Escalated tickets https://gus.fzk.de/download/escalationreports/roc/html/20101011_EscalationReport_ROCs.html
3 tickets on hold.
56316 - NGS-RAL not in BDII
58733 - RAL-PP biomed. dcache issue.
61228 - ALICE RAL T1.
Deployment priorities & timelines20m
Is this summary correct: Sites that have CREAM working are RAL T1, Glasgow, Manchester, Oxford, Birmingham and Imperial. Liverpool has CREAM setup but not in production. Installation is scheduled at RALPP, QMUL, UCL and Brunel. Further information is required for Lancaster, Sheffield, Cambridge, Bristol and Durham.
- New CA release http://grid-deployment.web.cern.ch/grid-deployment/lcg2CAlist.html.
- Next HEPSYSMAN meeting Monday 22nd November in Birmingham.
- Top-level BDII decision in WLCG
Q32010 Tier-2 reports8m
- Observations & comments
- Any escalation issues?