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)
firstname.lastname@example.org 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
CMS has finished 3 of of 4 mid-week Global Run exercises, as planned. They are 1,5 days long exercises. From the computing standpoint, it has been a valuable set of exercise to check the full T0 workflow, also on (relatively) recently deployed components, from P5 down to transfers of the data to T1 sites, with custodiality also. We plan to run a CRUZET-4 cosmic run exercise in the time slot August, 18th-25th, most probably continuing after that with magnetic field on. From the computing standpoint, and from the support and shifting experience, we are trying to use these exercises to get prepared to a season of constant data flow.
Problems found: some network at P5 issues, some DB-related interventions and issues, all properly documented and discussed with CERN-IT in several fora already. Progress can be done on identified areas, work is being done especially in the communication flows, and CRUZET-4 will be a chance to test for several days in a raw a quasi-real-life scenario for cosmic data flow and in general for some computing workflows.
NOTE: agreement with Castor@CERN for upgrading the CMS instance of Castor@CERN to 2.1.7-14 version was found for tomorrow, Tuesday, August 12th, 09h00-11h30 CERN time.
<big> LHCb report </big>
<big> Storage services: Recommended base versions </big>