In order to enable an iCal export link, your account needs to have a 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.
I have read and understood the above.
In conjunction with a having a key associated with your account, to have the possibility of exporting private event information necessitates the creation of a persistent key. This new key is also associated with your account and whilst it is active the data which can be obtained through using this key can be obtained by anyone in possession of the link provided. Due to this reason, it is extremely important that you keep links generated with this key 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 remove it from 'My Profile' under the 'HTTP API' tab and generate a new key before regenerating iCalendar links.
I have read and understood the above.
Permanent link for public information only:
Permanent link for all public and protected information:
08:30
- 08:40
Architecture of the Tier-2s within NDGF10'
(how do they appear to the rest of the world? as single
sites with a CE and SE?)
08:40
- 09:10
Storage element30'
Status of the virtual Storage Element that presents NDGF as a single site for storage management and data access
Analysis of the internal data rates within the NDGF Tier-1
(some concern that these may be higher than currently assumed)
Operation of the File Transfer Service for communication with other Tier-1s (ATLAS) and other Tier-2s (potentially for ATLAS, definitely for CMS if NDGF is a CMS Tier-1)
Implementation of the ATLAS data placement model
(RAW data and all its derivatives at the same site)
Implementation of the base SRM functionality (SRM v 2.2) and storage classes
Provision of a catalog equivalent to LFC for ATLAS
09:10
- 09:20
Progress and plans for the distributed database service for ATLAS in NDGF10'
(3D project)
09:20
- 09:30
Provision of site availability metrics10'
09:30
- 09:40
Model for NDGF daily operation and integration with the LCG/EGEE grid operations services10'
09:40
- 09:50
Accounting plans10'
see accounting presentations at the GDB (06dec06,
09jan07) and the discussions and decisions at the MB
(19dec06, 08jan07)
Integration of cpu accounting with the APEL repository at the GOC
User-level accounting
Storage accounting
09:50
- 10:00
Implementation of scheduling priorities based on VOMS groups and roles10'
10:00
- 10:10
Installation schedule for 200710'
10:10
- 10:40
Status and plans for testing the distributed Tier-1 functionality and integrating into the ATLAS and ALICE services30'
10:40
- 10:50
Organisational and management issues10'
Is it clear now how CMS fits in to NDGF, organisationally and technically?
Formal resource commitments for the Nordic countries and signing the MoU
NDGF representation in the WLCG Overview Board, and Computing Resource Review Board
Does NDGF feel adequately represented in the various WLCG boards, committees and meetings, and does it feel that it is well enough informed about the activity of the project?
Share this page
Social networks
Calendaring