The wiki is deprecated and due to be decommissioned by the end of September 2022.
The content is being migrated to other supports, new updates will be ignored and lost.
If needed you can get in touch with EGI SDIS team using operations @ egi.eu.
Difference between revisions of "EGI-InSPIRE:UNICORE integration task force"
| Line 26: | Line 26: | ||
== Open Actionpoints == | == Open Actionpoints == | ||
AP: Find out more about the EMI registry and the static info contained: How is the distinction between the static data GOCDB and EMI registry, how can we propagate downtime info for just one Service Endpoint (URLs are needed to distungish between different instances)? (contact Laurence Field) | *AP: Find out more about the EMI registry and the static info contained: How is the distinction between the static data GOCDB and EMI registry, how can we propagate downtime info for just one Service Endpoint (URLs are needed to distungish between different instances)? (contact Laurence Field) | ||
AP: ML to | *AP: ML to test sending a GGUS ticket to UNICORE: | ||
:See ticket https://gus.fzk.de/dmsu/dmsu_ticket.php?ticket=68192 Who got it? | |||
AP: | *AP: ML to send EI minutes of GOCDB dedicated phone conference | ||
*AP: DM to rename the first 3 UNICORE service types. | |||
:unicore6.registry | |||
:unicore6.UNICOREX | |||
:unicore6.gateway | |||
*AP: KB contacting Germany through ticket 306 | |||
: https://rt.egi.eu/rt/Ticket/Display.html?id=306 | |||
*AP: official requirement towards APEL (accounting monitoring must be sufficient to decide whether all deployed middlewares of a site publish accounting data) | |||
== Closed Actionpoints == | == Closed Actionpoints == | ||
AP: ML making a doodlepoll for next meeting. (next time with Global Timezones enabled) | AP: ML making a doodlepoll for next meeting. (next time with Global Timezones enabled) | ||
Revision as of 17:39, 2 March 2011
| Main | EGI-inSPIRE SA1 | Tools | Middleware | Documentation | Security | Performance | Interoperability |
The meetings can be found under https://www.egi.eu/indico/categoryDisplay.py?categId=49" . Currently we aim at a frequency of at least one meeting per month.
A new dedicated mailinglist has been created: it is called unicore-integration-tf@mailman.egi.eu https://www.egi.eu/sso/groupView/unicore-integration-tf
Current members are those who expressed interest to participate in the first or second meeting or were attending it.
Open Actionpoints
- AP: Find out more about the EMI registry and the static info contained: How is the distinction between the static data GOCDB and EMI registry, how can we propagate downtime info for just one Service Endpoint (URLs are needed to distungish between different instances)? (contact Laurence Field)
- AP: ML to test sending a GGUS ticket to UNICORE:
- See ticket https://gus.fzk.de/dmsu/dmsu_ticket.php?ticket=68192 Who got it?
- AP: ML to send EI minutes of GOCDB dedicated phone conference
- AP: DM to rename the first 3 UNICORE service types.
- unicore6.registry
- unicore6.UNICOREX
- unicore6.gateway
- AP: KB contacting Germany through ticket 306
- AP: official requirement towards APEL (accounting monitoring must be sufficient to decide whether all deployed middlewares of a site publish accounting data)
Closed Actionpoints
AP: ML making a doodlepoll for next meeting. (next time with Global Timezones enabled)