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
firstname.lastname@example.org 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
Dear IT C-COD,
Although it looks like the dashboard is full, the scenario is such:
Many AP sites haven't updated their alarms (in OK status) or tickets (expired on 12th) since the weekend.
Some of the sites are in downtime, and therefore those alarms/tickets are currently ignored.
Lastly, and this is one for the WLCG meeting: The apel situation does not appear to have been finally resolved:
"APEL Publication works normally and records are properly received, yet no update can currently be reflected in SAM or in the accounting portal.
Note to operators: please ignore alarms on the APEL-Pub test until further notice."
Therefore, I advise a moratorium on these tickets/alarms until APEL tells us all is OK again.
NE ROC/NDGF C-COD
** The SAM MPI tests are raising alarms from this morning, as agreed last week **
Update received from Isabel Campos (MPI Task Force) last week here summarised.
The current situation is the following:
there are 90 sites which publish the MPI-START tag, 88 are tested by SAM and 2 other sites (IFCA and RAL) are not tested because the way they publish the SubCluster info.
Of those sites: 69 working fine (67 at SAM + IFCA + RAL)
which gives a 76% of sites passing the tests (75% if we don't count the sites out of SAM)
For all the sites with errors a ticket in GGUS has been opened and most of them are working actively on finding a solution. There is a guide with the list of errors found and possible solutions for them at http://wiki.ifca.es/e-ciencia/index.php/MPI_Errors
Documentation for MPI Support in EGEE: https://twiki.cern.ch/twiki/bin/view/EGEE/MpiTools
More information about errors in the MPI knowledge DB: http://wiki.ifca.es/e-ciencia/index.php/MPI_Errors