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 0140768
Any progress for action 000212 on Steve (i.e. Publishing Production Role restriction from CE queue)?
SAM had some problems this week ...
SAM Problem: (network) problem with the CERN BDII used by the RB/WMS for job submission.
SAM Problem: File missing for host certificate test.
Issue from INFN-T1:
We noticed this problem on the GOC DB: in a open downtime, when status is changed, for example from Risk to Outage, the history is lost, so if we open one for "Risk status" and after 3 days we pass in "Outage status" for the GOC DB we have been always in "Outage Status". It seems one solution is to close the down of "Risk status" and open a new one for "Outage status".
[ROC South Eastern Europe]:
99% of SEE WNs are now SL4 with gLite 3.1. We are also testing the SDJ configuration as it is described at
Do other regions have some experience to share on this matter?
SAM still reports sites as failing when there is a well identified grid wide failure. What is the timeline for no longer publishing these failures to sites (who when they are published spend time trying to figure out the problem).
<big> WLCG issues coming from ROC reports </big>
<big>WLCG Service Interventions (with dates / times where known) </big>