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:
Significant work is already under-way to establish interoperability between collaborating grid infrastructures around the world. The Grid Interoperability Now (GIN
working group within the Open Grid Forum (OGF) has hosted technical discussions between major grid operators that have improved the interoperability between these systems.
The grid infrastructures are continuously expanding their user bases and providing support to a wider range of application domains. As the infrastructures grow in size and reliability, the user communities they support depend on them more and more. The grid infrastructures are critical to the success of major international scientific undertakings such as the Large Hadron Collider. Other scientific instruments will be coming online around the world in the next few years for which international production grid infrastructures will be essential.
The technical work of the GIN group is continuing, providing increased levels of interoperability that will consequently reveal the need for an agreed policy of accessibility across the combined infrastructures to support new instruments and their user communities.
Currently there is no forum that brings together the leadership of the major grid structures and hence there is a no mechanism for discussing policy and strategy across the combined infrastructures.
We propose to establish a forum to address such issues and are tentatively scheduling a first meeting at OGF22 (Boston, USA, February 2008) where the aim will be to:
* define the mandate and membership of the forum
* determine the governance structure and frequency of its meetings
* identify those areas of infrastructure policy and strategy where agreement would be necessary
* explore the relationship of the forum with other bodies etc.
Attandence is by invitation only!
DEISA: Victor Alessandrini, Stefan Heinzel, Andreas Schott, Hermann Lederer
EGEE: Bob Jones, Erwin Laure
NAREGI: Satoshi Matsuoka
OSG: Ruth Pordes, Miron Livny
TeraGrid: JP Navarro
Mandate, Membership, Identification of Scope45mHaym Saloman
Identification of Infrastructure Policy and Strategy Areas of Common Interest30mHaym Saloman
Overall goal: give users guidelines what to do in order to exploit
* Negotiation of usage
- Is there a notion of a "home" grid?
this would allow to reuse techniques used in mobile telephony but
how do "multi-Grid" VOs relate to that?
- Access Policies
Supercomputer Grids have tighter regulations for access
does this call for different VOs or could existing mechanisms
be exploited to enforce these policies?
do people have to sign with each resource center separately?
can we come up with a common user registration? Can we have a
information sufficient to allow access to all participating grids
or would a common denominator do?
- CPU and data usage
who are the actors: VO, user? Grid, resource provider?
Could there be a common application form?
different models exist:
* guaranteed resources
* opportunistic resources
have allocations on guaranteed resources be negotiated with each
how can opportunistic resources be negotiated?
how can data be exchanged and managed between infrastructures
- network connectivity
does the existing/planned network have enough capacity/right
when the federated Grid becomes reality?
research network vs. private networks
- tied into "home Grid" discussion
- is there a need of a common way how Grids account with their VOs
and who would be the actors
- should there be a "bank" i.e. somebody who keeps the accounts?
- would you participate in the design of a standard accounting
- would you push out account status to a "home Grid" or "home VO"?
Governance Structure and Meeting Frequency15mHaym Saloman
Is OGF a suitable host structure?
Is the frequency of OGF appropriate?