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
France ROC: IN2P3-CC T1: How to publish CE authorization restriction for a VO? We restricted the access to production role for CMS and Atlas on our T1. But is it possible to publish this in order to prevent job submission from unauthorized people ?
SW Europe ROC: PIC: Strange behavior of the SAM tests this weekend. Two SAM tests where send to the CEs within 10 minutes. The first was OK, the second failed without an obvious reason. This tests where executed at the end of a period where when the SRM tests were marked gray at GRIDVIEW.
<big>Drop of support for plain proxies</big>
At present, gLite software is being certified by SA3 using both plain grid proxies as well as VOMS proxies. As the EGEE project has moved away from plain grid proxies to VOMS-based proxies, and SA3 is trying to make the best of its limited manpower, SA3 has proposed to the TMB (former TCG) to drop the support for plain grid proxies (i.e. generated via grid-proxy-init) in the EGEE m/w.
EGEE will certify services only with VOMS proxies. Problems or bugs affecting services accessed using plain proxies will be no longer fixed.
If you have any objection to this proposal please write to firstname.lastname@example.org before the next TMB (Wed. 18th June 2008).
<big> Issue with upgrade of MyProxy to gLite 3.1</big>
The myproxy-server daemon will hang when it is started from a non-interactive shell. It appears to work fine when started from an interactive shell.
The cause of the problem is that the myproxy-server has been linked against a multi-threaded flavor of Globus instead of the single-threaded flavor expected by the code.
We have asked the VDT project for an urgent rebuild of the code against the correct Globus flavor. We will certify the new RPM and release it to production with high priority. In the meantime sites can either stay with the MyProxy service provided by gLite 3.0, or restart the myproxy-server interactively as needed.
<big> WLCG issues coming from ROC reports </big>
No items this week.
<big>WLCG Service Interventions (with dates / times where known) </big>
The site TAU-LCG2 will be decommissioned on June 15. Until then it is put in SD. If you need data from the SE or have any other questions, feel free to contact the site admin.
PIC Tier-1 will have an Scheduled Downtime next tuesday the 10th of july in order to perform interventions on various grid services: SRM (dcache upgrade), CE (NFS sw area migration), FTS (head node migration), LFC-atlas (DB backend migration) and LHCb-DIRAC (IP changes).
The SD and broadcast have been already filed in the GOCDB.