Alert.png 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"

From EGIWiki
Jump to navigation Jump to search
Line 29: Line 29:
*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)
:Progress: ML will report on her email discussion with Laurence Field and plans to push the GLUE 2.0 use case in propagating downtime information
:Progress: ML will report on her email discussion with Laurence Field and plans to push the GLUE 2.0 use case in propagating downtime information
: Update: EMI registry in very early planning stage, XML solution in the meantime. Second solution for GOCDB (the GLUE 2.0 based approach) again in discussion. ML to bring forward and discuss the usecase in the next OGF PGI wg meeting.


*AP: Reopen GOCDB requirement ticket for EndPointServiceURL and ask for second solution with a proposed timeline of 6 months.


*AP: ML to test sending a GGUS ticket to UNICORE:
*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?
:See ticket https://gus.fzk.de/dmsu/dmsu_ticket.php?ticket=68192 Who got it?
: Update: https://gus.fzk.de/dmsu/dmsu_ticket.php?ticket=68177 was produced as another test ticket. Check why nobody got the tickets!




*AP: ML to send EI minutes of GOCDB dedicated phone conference
*AP: DM to rename the first 3 UNICORE service types.  
 
 
*AP: DM to rename the first 3 UNICORE service types.
:unicore6.registry
:unicore6.registry
:unicore6.UNICOREX
:unicore6.UNICOREX
:unicore6.gateway
:unicore6.gateway
: Update: remind DM occasionally to put this on the top of his priority list


*AP: for everybody (especially EI, KB and FR): to keep https://rt.egi.eu/rt/Ticket/Display.html?id=306 updated.


*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)
: https://rt.egi.eu/rt/Ticket/Display.html?id=306


* AP: ML making a doodlepoll for next meeting, this time with Global Timezones and maybe function enabled.


*AP: official requirement towards APEL (accounting monitoring must be sufficient to decide whether all deployed middlewares of a site publish accounting data)
*AP: KB sends a summary of CIS, why it is not supported by EMI and why the XML  approach is advantageous monitoring wise.


== 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 in March
 
*AP: ML to send EI minutes of GOCDB dedicated phone conference
 
*AP: KB contacting Germany through ticket 306
: https://rt.egi.eu/rt/Ticket/Display.html?id=306

Revision as of 14:49, 8 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)
Progress: ML will report on her email discussion with Laurence Field and plans to push the GLUE 2.0 use case in propagating downtime information
Update: EMI registry in very early planning stage, XML solution in the meantime. Second solution for GOCDB (the GLUE 2.0 based approach) again in discussion. ML to bring forward and discuss the usecase in the next OGF PGI wg meeting.
  • AP: Reopen GOCDB requirement ticket for EndPointServiceURL and ask for second solution with a proposed timeline of 6 months.
  • 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?
Update: https://gus.fzk.de/dmsu/dmsu_ticket.php?ticket=68177 was produced as another test ticket. Check why nobody got the tickets!


  • AP: DM to rename the first 3 UNICORE service types.
unicore6.registry
unicore6.UNICOREX
unicore6.gateway
Update: remind DM occasionally to put this on the top of his priority list
  • AP: official requirement towards APEL (accounting monitoring must be sufficient to decide whether all deployed middlewares of a site publish accounting data)
  • AP: ML making a doodlepoll for next meeting, this time with Global Timezones and maybe function enabled.
  • AP: KB sends a summary of CIS, why it is not supported by EMI and why the XML approach is advantageous monitoring wise.

Closed Actionpoints

  • AP: ML making a doodlepoll for next meeting in March
  • AP: ML to send EI minutes of GOCDB dedicated phone conference
  • AP: KB contacting Germany through ticket 306
https://rt.egi.eu/rt/Ticket/Display.html?id=306