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 0148141
OR click HERE (Please specify your name & affiliation in the web-interface)
ROC NE: Vera Hansper has submitted GGUS ticket 42341 on October 15th. This ticket has been assigned the the GridView support unit. No action has been undertaken yet to solve this ticket.
ROC UK/I: Noticed some problems with the formatting of this ROC report. Multiple unlabelled lines for the downtime history against many sites and only some of these line up.
<big> Publishing "correct" values for cluster SI2k and Total CPU</big>
Last week PIC asked: In the GridMap monitoring (http://gridmap.cern.ch) if one clicks the "show SI2k" button in the "topology view" section, the sites are scaled wrt the "total cpus" value in a SI2k units, which looks as computed just multiplying the number of job slots published times the GlueHostBenchmarkSI00. As most
of the clusters are not homogeneous, this is not correct.
GlueHostBenchmarkSI00 is just the value to which internal accounting
Answer: If you scale CPU speed to some value then you should also scale your SubCluster's Total and Logical CPU count so that your total power is reflected.
<big> Job submission mechanism needed in the CREAM CE</big>
What submission mechanisms does the CREAM CE need to support?
- GRAM (WS / pre-WS)?
<big> Pool accounts on VO Boxes </big>
<big> WLCG issues coming from ROC reports </big>
ROC UK/I: very few sites passing the LHCb SAM tests today.
ROC CERN: [Information] Support for a new Role=pilot for LHCb has been deployed at CERN
ROC CERN: [Information] The ATLAS grid queues default resource requirements have been updated to select nodes with at least 1.9GB of memory
<big>WLCG Service Interventions (with dates / times where known) </big>