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)
On Wednesday when Gilles implements the
new, sanitized, GOCDB service names, SAM will submit LFC_LOCAL and
LFC_CENTRAL tests instead of the current LFC tests. The only difference
is that an LFC-ping test has been added, and the tests will no longer
attempt to write to read-only LFCs. An EGEE briadcast will be sent after
<big>WLCG Service Interventions (with dates / times where known) </big>
Some modification on the critical SAM tests for LHCb
Set new critical tests targeted to test the infrastructure under the LHCb perspective: JS Shared Area and CSH test from ops. This gives a disentangled from DIRAC view of the health status f the site and guarantees to have always SAM test results for the CE (that ultimately for LHCB suffered several internal problem preventing to have CE properly rated)
Further to that we also have set critical (after month of test) the condition DB test (only valid for T1)
For the SE two more LHCb specific tests are also coming soon (they are in a test phase before becoming critical)
A second point is about warning sites that LHCB is going to broadcast the request for the pilot role as discussed at the GDB and last Workshop.
Non critical GGUS ticket submitted last week against GridKA today escalated at the daily ops meeting it looks like from the answer that streams to GridKA are off since half a year now. Some words from GridKA are welcome
<big> Storage services: Recommended base versions </big>