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:
- Shahbaz Memon (JUELICH)
- Björn Hagemeier(JUELICH)
- Davide Solomoni (INFN)
- Peter Solomoni (INFN)
- Szabolcs Székelyi (NIIFI)
- Zsombor Nagy (NIIFI)
- Florido Paganelli (Lund University)
1. Discussed the EMI's cloud related documentation from DNA1.3.1 and DoW
1.1 excerpt from from DNA 1.3.1 (Technical Development Plan)
-  Evaluate integration scenarios with off-the-shelf computing cloud systems
-  Successful computational usage of emerging computing models i.e. clouds with EMI components
- Focus is clouds and thus only virtualization in this context - all other topics of virtualization are tackled by virtualization task force
- EMI-2: CEs capable scaling out to clouds, and Cloud Services
1.2 excerpt from DoW
- Interoperability between grids, supercomputers and emerging computing models like clouds and desktop grids will be extended to address scalability and accessibility requirements. (Project Vision Page 11)
- bridge the gap between grid and cloud infrastructures. (Page 26)
- MS29. MJRA1.4 - Successful computational usage of emerging computing models->This milestone indicates a success in using emerging computing models (i.e. clouds) with EMI components. (Page 33)
1.3 excerpt from wiki
- To be Confirmed:Expected result is a 5 page report (wiki page or document) that also includes one rough architecture / infrastructure sketch
1.4 goal: due M30 (Oct 2012)-> A-REX, CREAM, U. TSI, U. XNJS, U. EMIXS. Successful computational usage of emerging computing models i.e. clouds with EMI components (scaling out to clouds).
2 Status of the technical collaboration with other projects (StratusLab and VenusC)
- Meeting with KTH (PDC) at the EGI Technical Forum
- Rough draft is available from Annex (Not visible for all). We are expecting a draft architecture in December.
- The project's major focus is on SaaS/PaaS
- SkypeCon with Vangelis Floros from GRNet
- Technical documents / deliverables available
- The project will produce the IaaS layered components
3 All hands meeting preparation
- Who is attending (Davide Solomony, Zsombor Nagy, Eric Yen, Shahbaz Memon)
- Planned presentations (WNode, NorduGrid cloud initative, Presentations on StratusLab and VenusC)
- It is also planned to discuss requirements, work plan, and time lines
4 Available cloud tools developed by EMI partners
Davide: WNode - a virtualized environment providing integration of grid (gLite) and cloud (OCCI) resources
Zsombor: NIIF implemented and hosting a cloud service, where it is possible to create and run a collection of virtual machines with one command e.g. an SGE cluster with ARC's A-Rex service installed on the head node.