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)
France ROC: IN2P3: Issue with Tarball distribution as pointed out through GGUS #49265 (https://gus.fzk.de/ws/ticket_info.php?ticket=49265)
Basically, the SL4/x86_64 tarball of glite-WN is not well built. It actually suffers the same problem than the RPM-based distribution as explained in the known issues (http://glite.web.cern.ch/glite/packages/R3.1/x86_64/deployment/glite-WN/glite-WN-known-issues.asp).
In order to solve the problem once and for all, it would be enough to rebuild the tarball by applying the workaround as described within the known issues for the RPM-based distribution.
For a site, the use of tarball distribution is sustainable if and only if the delivered tarball is well-built. In no case, a site should complete the tarball building process by installing missing RPMs. Once a building problem is identified, the tarball should be rebuilt by the provider itself.
By the way, we think that the GGUS ticket was prematurely closed as a new (and completed) tarball was not provided.
Within the french ROC, 3 sites make use of the Tarball distribution for UI/WN. They were asked not to deploy the 2 last updates because of the building problem.
Does some body know how many sites are using the tarball distribution for glite-WN ? Are the french sites the only ones?
at risk: reconfiguration, reboot of several disk pools on 25/6: 11:00 - 13:00 UTC
<big> Integration of Mathwork's Matlab with gLite + licences </big>
Information from NA4:
NA4 has been working closely with Mathworks in order to smoothly integrate MATLAB MDCS with gLite. This product has passed through an extensive trial period during the past year, delivering a couple of interesting success stories (see the article in the latest iSGTW: http://www.isgtw.org/?pid=1001851).
Regarding the license schema; both the resource provider (MDCS) and the user (MATLAB gui) should have a license in order for the latter to access the product on the grid. For the grid context we have agreed that a third party license is the most appropriate which means that an installation on an RC will give access to all VOs supported by this cluster. Therefore, there is no control of who is accessing the product as long as he/she is member of one of the supporting VOs. Pricing information can be made available on request. From what we've discussed with Mathworks these prices are rather indicative which means that they would be potentially willing to negotiate them.
For any sites interested in this, enquiries should first be send to:
Vangelis Floros (email@example.com) and firstname.lastname@example.org.
Maria Dimou, Rob Quick
(OSG - Indiana University)