EGI-InSPIRE:UNICORE integration task force

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.

Update: Too late to be part of V1 of http://www.ogf.org/documents/GFD.180.pdf waiting together with 2 other use cases for V2.

• AP: Reopen GOCDB requirement ticket for EndPointServiceURL https://rt.egi.eu/rt/Ticket/Display.html?id=975 and ask for second solution (Add URL field for ServiceEndpoint and repeat ServiceEndpoint to represent different URLs /Associate a ServiceEndpoint with a new „1-to-many‟ EndpointLocation entity), with a proposed timeline of 6 months.

Progress: David provided us with some updated slides on the possible implementation with more detail: https://wiki.egi.eu/wiki/File:GocdbGlue2Unicore.pdf

• 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!

Progress: Ticket towards GGUS created: https://gus.fzk.de/ws/ticket_info.php?ticket=68354

Updated: GGUS ticket correctly sent to Jülich managed list emi-support@unicore.eu , this list has currently a small number of subscribed members. Awaiting internal EMI decision to add more people like e.g. KB

• AP: DM to rename the first 3 UNICORE service types.

unicore6.registry

unicore6.UNICOREX

unicore6.gateway

Update: GOCDB now uses the new Unicore service type names (unicore6.gateway, unicore6.registry, unicore6.UNICOREX). See: https://wiki.egi.eu/wiki/GOCDB/Input_System_User_Documentation#Service_types

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

• 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=1607

• AP: ML making a doodlepoll for next meeting, this time with Global Timezones and maybe function enabled. http://www.doodle.com/9zw6qmkcmzvy5sq9

• AP: KB sends a summary of CIS, why it is not supported by EMI and why the XML approach is advantageous monitoring wise.

• AP: KB and FR to send documentation links to operational-documentation-best-practices@mailman.egi.eu as soon as considered sufficiently completed, suggested procedure which could be of interest in this context: how to install more than one UNICORE service on one host.

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