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.

EGI-InSPIRE:UNICORE integration task force

From EGIWiki
Jump to navigation Jump to search
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: "EMI registry use case" 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: MB 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. MB 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.
Update: currently reviewing related document EMI Execution Service Specification https://twiki.cern.ch/twiki/pub/EMI/EmiExecutionService/EMI-ES-Specification_v1.0.odt
Update: EMI ESS reviewed, currently no PGI wg meetings.


  • AP: "ServiceEndpointURLs in GOCDB" 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
Update: Personal discussion at the EGI UF, Vilnius with John Casson: A new proposed solution with getting rid of the primary key constraint and a new timeline of one month has been discussed. It fulfills all our requirements. This requirement has now top-priority within GOCDB development.
Update: Requirement has been fixed and seems to work: ttps://goc.gridops.org/portal/index.php?Page_Type=View_Object&object_id=22973&grid_id=0



  • AP: EI to contact Maciej Pawlik and Paweł Wolniewicz to discuss sensible Nagios configuration default definitions.



  • AP: Start a more tight collaboration with Belarus. AL to keep us updated on efforts to go open source or other possibilities to collaborate, KB to send info on new release with all major features.


  • AP: "Best practices" 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.
Update: PL-Grid restructuring whole UNICORE documentation system otherwise concentration on EMI 1 release. MB will now start by pointing them to standard unicore.eu documents which conclude good documentation and installation guides and see if they would like to already include a link to them. What is missing: real best practices, the very solutions to different real integration problems. Some material exists in Polish language.
Update from Mathilde: UNICORE installation documentation (not yet covering the EMI UNICORE rpms) can be found at http://www.unicore.eu/documentation/manuals/unicore6/files/manual_installation.pdf The basic scenario (section 2) should answer the question on how to install multiple services on one server. It is not perfect for EGI purposes but maybe it is of interest.
Update: Michaela sent those links to the best practices mailinglist, but hasn't got any feedback yet.


  • AP: "Next Meeting": MB making again a doodlepoll for next meeting with Global Timezones and maybe function enabled.
Update: http://www.doodle.com/7xcgzsqxadp45v6q


  • AP: "List of service types to be integrated." MB compiling a list of the next service types which should be integrated into GOCDB and sending it to our mailinglist for discussion
Update: Some discussion of this list during the meeting, AP on KB to send his list to the mailinglist as well and to continue discussing there and to put the output of this discussion in ticket https://rt.egi.eu/rt/Ticket/Display.html?id=944

Closed Actionpoints


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

Final: Currently keep the small number who will get the GGUS ticket, who will forward them to the UNICORE tracking system in sourceforge. Follow up of this AP is out of the scope for this task force. Will be taken up gain within EMI. UNICORE related GGUS FAQ has been transported to EGI wiki: GGUS:UNICORE-Client_FAQ and GGUS:UNICORE-Server_FAQ.


  • AP: DM to rename the first 3 UNICORE service types.
unicore6.registry
unicore6.UNICOREX
unicore6.gateway
Final: 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: KB sends a summary of CIS, why it is not supported by EMI and why the XML approach is advantageous monitoring wise.
Why this is not supported by EMI is a political decision based on limited manpower and effort, KB wrote a detailed description on the usage of CIS in the monitoring system.


  • 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