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:
28-R-15 (CERN conferencing service (joining details below))
CERN conferencing service (joining details below)
email@example.com Weekly OSG, EGEE, WLCG infrastructure coordination meeting.
We discuss the weekly running of the production grid infrastructure based on weekly reports from the attendees. The reported issues are discussed, assigned to the relevant teams, followed up and escalated when needed. The meeting is also the forum for the sites to get a summary of the weekly WLCG activities and plans
OSG operations team
EGEE operations team
EGEE ROC managers
WLCG coordination representatives
WLCG Tier-1 representatives
other site representatives (optional)
To dial in to the conference:
a. Dial +41227676000
b. Enter access code 0148141
OR click HERE (Please specify your name & affiliation in the web-interface)
Report from CERN:
Due to network intervention at CERN on March 19th a number of alarms were raised either because lxdpm104.cern.ch (which is central SE for SAM) or lcg-bdii.cern.ch (top level BDII) were unavailable. Such alarms were set to off without raising the tickets.
Report from CH-DE:
The Handover log has been reviewed .
This tool permits now to send a message to a Regional Team .
This message will be visible in the summary on the right only in your
scope and in the scope of the Team contacted .
If you remark a bug , or if you have any feedback , don' t hesitate .
HIGHLIGHTgLite 3.2 Update 01 was released to production
This is the first release of the 3.2 baseline and contains:
WNs + Torque clients for SLC5
signed rpm repository
Please notice that this version is supported only on 64bit machines
Release notes in
<big> EGEE issues coming from ROC reports </big>
None this week
<big>Grid Service Interventions </big>
CERN Significant network disruption, 19th March 06:00 to 08:00 CET.
In order to profit from this intervention it has been suggested by the UK that
regions and sites record the problems seen during this time. Please report back
next week and the results can be considered.
any major problems to be discussed this week?
Please have a look at the daily reports given at WLCG daily calls here.
<big> LHCb items </big>
<big> WLCG service recommended baseline versions </big>
The current FTS tries SRM v1 unless endpoints are published correctly.
To force type 2 use
Once glite-data-transfer-agents 3_3_4_1 is released
this will be default anyway.
Given all sites are using SRM v2.2 now we recommend that
this configuration be added to all the current FTSes now prior
to this upgrade reaching production.
Exactly this was discussed last week and Rob had an action to check.
#46647:Duplicate of the above?
If 'yes' is this human error?
Guenter is also asked to check on the GGUS side via
Review of action items5m
It's show time folks, again! Next week: LHC experiment VOs to perform an ALARM ticket test (full round from opening to ticket closing) to Tier1s.
[savannah ticket #107452] and
[testing rules]. Summary reports must be sent to firstname.lastname@example.org by April 3rd at the latest!