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)
A lot of problems this week with dashboard, Monday morning doesn't work
Tuesday morning not didn't work again. Friday worked too low ?.
Cern has some pps nodes under sam but monday 8 may be disappeared
Report from NORTH:
Problems Encountered during shift
Two times the COD Dashboard was unavailable, tuesday morning and
Information for the new COD team *
Last weeks handover log mentioned the following:
GGUS:43130 has to be extended by the reason of SD (until 12/15/08
-Gstat ), but this action was not possible to be done. The ticket has
expired and it is still on the Dashboard.
This is reported as a technical problem of the dashboard.
Last week we were able to update this ticket again.
<big> PPS Report & Issues </big>
Please find Issues from EGEE ROCs and general info in:
In order to make easier the life of VOs that want to run either 32b application or 64b one, we would like to make sure that every french site is correctly publishing the GlueHostArchitecturePlatformType attribute of their lcg-CE GlueSubCluster.
According to the link http://goc.grid.sinica.edu.tw/gocwiki/How_to_publish_my_machine_architecture, the value is obtained by taking the result of "uname -m" command launched on the worker node (that is, the OS bits capability)
We are however wondering whether that value has to be adapted or not to the effective Glite-WN version (i686 or x86_64). In particular, if your WN OS is x86_64 and your Glite-WN version is i686, the job environment is set to i686. In such a case, do we really have to publish x86_64 as explained in the above link ? Isn t it a bit error-prone for the VOs ?
Job list match problems at DESY reported by user. Traced back to Top-level BDII. Switched back to a host running an older version. Same effect observed at FZK as well.
Details are logged in GGUS:44201
[Might be presently assigned to the wrong support unit]