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)
Maite Barroso Lopez
email@example.com Weekly EGEE 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
EGEE operations team
EGEE ROC managers
site representatives (optional)
To dial in to the conference:
a. Dial +41227676000
b. Enter access code 0148141
AND click HERE (Please specify your name & affiliation in the web-interface)
From Northern Europe to Italy
ROC CERN let expire 3 tickets over the weekend, one of them has even
already expired last Thursday.
2 tickets older than 30 days: APEL problems in ROC AP with APEL support
being involved in both. Both of them expire today.
Otherwise it was a very quite week. No WLCG items I would say.
Roll back of UPDATE 57 for gLite 3.1 due to critical problems in BDII: the problems were detected by SAM failures and GGUS tickets from 2 sites.
Approximately 30 CEs were not being published as the BDII service on those machines were in a stopped state. In addition, one site reported that their top-level BDII was missing entries from a site that we publishing information correctly.
The reason for the BDII failures on the CE was that the conditional restart of the service failed. This was due to a problem with the rpm that was already installed and the problem was only triggered on the update. Most of the sites affected had auto-update enabled and hence updated the package automatically.
The problem with the top-level BDII was caused by the fact that the gLite 3.1 release was missing an rpm that was submitted for release on gLite 3.2 (patch 3154) but was never submitted for release on gLite 3.1.
During certification on gLite 3.1 the problem was not detected as it only shows up in a certain scenario where a combination of certain versions are used together. This scenario was not captured. In PPS the problem was not detected as a clean deployment test for patch #3204 was not done in PPS. This is due to an unclean rejection of a previous patch in PPS which left some machines in a spurious mode.
The release was rolled back while the problems are being fixed. The other components included in the release were not affected, but were also rolled-back, and will be made available again today in a new UPDATE.
A detailed post-mortem is being done to take corrective actions so we avoid similar cases in the future.
<big> EGEE issues coming from ROC reports </big>
AP, France, DECH and Russia hadn't validated their reports by 15:00.
Which is the version for each Storage Element implementation to be compliant with the "Usage of Glue Schema v1.3 for WLCG Installed Capacity information"? As ROC, we could push and follow the upgrade of the old version and validate the published data.
The Baseline versions of services and client tools for WLCG operations (https://twiki.cern.ch/twiki/bin/view/LCG/WLCGBaselineVersions) seems to be update last 02-Jun-2009. This useful page should be update more frequently (at every gLite update?) just to be sure that the recommendations are not out of date.
Reminder for sites to move to WMS 3.2 (available in gLite repository). This must be done by the end of October!
The RB service was made obsolete quite some time ago and it should no longer be run in the production infrastructure. Please, decommission the RB and install an up-to-date WMS as soon as possible. Still 7 around: GILDA-INFN-CATANIA, HG-01-GRNET, IFCA-LCG2, IFIC-LCG2, JP-KEK-CRC-01, RRC-KI, TR-01-ULAKBIM