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 0148141
OR click HERE (Please specify your name & affiliation in the web-interface)
ROC DECH: DESY: Issue with glite-WN-3.1.31-0
ATLAS complained to us about problems using their software. It seems that this happened after the deployment of glite-WN-3.1.31-0, which introduced the grid-cm package, that badly interferes with the ATLAS Python installation, which seems to be not properly set up.
We want to make the operations meeting aware of the problem since it might affect many other sites. We strongly recommend to go for a central solution in ATLAS and not patching around on the level of sites.
Some item can be found in the ROC DECH support portal:
ROC DECH: DESY: IRAN CA issue
There is rumors that the German Ministry of Science has requested (?) will request to all German resource providers to make sure that the resources cannot be used by users from Iran.
This is at least a matter for CMS sites, because they have partners from Iran in the VO using certs signed by the Iranian CA.
What is know about this in EGEE? Is there any advise how to solve this technically in case sites would need to fulfill such a request?
Removing the Iranian CA would let to failing SAM tests because proper installation of all participating CAs is checked. That btw does not make sure to exclude Iranian citizens since do not have certificate from the Iranian CA.
As announced last week*, the MATLAB product from Mathworks has been integrated and extensively tested with gLite. Any sites interested in integrating MATHLAB with gLite in their site should read the announcement* and follow the instructions there.
For technical information and other material regarding MDCS and gLite integration you can check these resources.
Video on parallel computing with MATLAB for administrators: http://www.mathworks.com/wbnr30965
NA4 wiki page: https://twiki.cern.ch/twiki/bin/view/EGEE/GLiteAndMATLABToolkitIntegration