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:
Opening and goals of the workshop. Motto: yes we can, stability is coming to dCache.
Jos van Wezel
dCache T1 AdministratorsFTU room 156
FTU room 156
This is a closed session slot for admins only
dCache T1 Administrators union1h
Mutual introduction. Whos who in dcache land?
reflection of current practice of information exchange between T1 admins
improve stability of operations. what are the 5 most seen issues and how are they impacting stability.
T1 strategy for the coming months. What can we sustain with the current
Are we prepared to update dCache or to change the setup? Should we have a fixed maintenance cycle? Can we improve pre-testing of the experiments DDM systems at the site?
dCache T1 Administrators union cont.30m
Future meetings? Necessity? Frequency?
Do we know what our customers want? Do we know what the experiments want to see improved at least before data taking?
Dealing with experiment requests
how EGEE and OSG differ
Configuration and tune-ups at the sites30m
Presentation/discussion of (site specific) configurations for logging, monitoring, failover/redundancy, scalability.
What is special in your setup that you suggest others sites could benefit from.
What are your numbers for the JVM, for the movers per pool, for the size per disk etc.
From this slot we move into generic configurations starting with database setup and tuning.
T1 Administrators technical session part 1: administration experiences and issuesFTU FZK
The administrators sessions are forum discussions chaired by one of the T1 administrators who may start the forum with a short presentation that for example may include a list of sub topics to discuss, questions that live among the T1s admins or explains his/her own experience with the specific topic. The slot times are merely guidelines.
Postgres and Databases jamboree1h
# Backups and restore
# Best practices
* Vacuum & Analyze
# High Availability
* Warm standby
* Case: the billingDB at PIC
T1 Administrators technical session part 2: upcoming administration tasksFTU FZK
gPlazma and VOMS30m
Chimera, ready for T1 deployment30m
Erik Mattias Wadenstein
Summary and conclusions of the administrators sessions30m
Optimisation of dCache30m
All hands: sustaining dCacheFTU room 156
FTU room 156
Administrators, developers and supporters of dCache and WLCG and experiment representatives discuss stability and reliability of dat management and dCahe in particular. We try to separate dCache issues from those that must be dealt with elsewhere. GridFTP, FTS, LFC etc are interacting with dCache and have impact on stability.
Summary of experiment open issues with data management and dCache30m
What are the current showstoppers and must haves for reliable data management according to the LHC experiments. Realize these are moving targets!
WLCG status of data management: downsides, upsides, management suggestions for improvement, relationship with other services (FTS, LFC, OPN etc)
dCache status, developments and plans1h
What seem to be the recurring issues at site XXX.
What can be don to improve error tracking
What could dCache.org do to help.
Where can the T1s assist in getting problems cornered and fixed.
Plans to fix known bugs/problems and improve/enhance the dCache categorized into 3 groups: soon, next year, never. Includes a vision for Internet data storage and management with dCache.
Ticket statistics. What needed a lot of attention? What happens always on site X but strangely never at site Y. Did the information you, the admin, provided include the facts dcache.org needed to solve the ticket?
Was your ticket answered effectively?
Are the current support and contact methods optimal?