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:Globus integration task force

From EGIWiki
Jump to navigation Jump to search
Main EGI-inSPIRE SA1 Tools Middleware Documentation Security Performance Interoperability



The meetings will be found in indico under the catagory https://www.egi.eu/indico/categoryDisplay.py?categId=53. A new dedicated mailinglist has been created: it is called globus-integration-tf@mailman.egi.eu https://www.egi.eu/sso/groupView/globus-integration-tf Current members are those who expressed interest to participate in the first meeting or were attending it or were pointed out by other people.

Open Actionpoints


  • AP: MB to test GGUS leaf to IGE: what is the mailinglist and who is on it.
Update: Ticket created: https://gus.fzk.de/ws/ticket_info.php?ticket=70499


  • AP: EP to report on installation of Grid-SAFE in the LRZ testbed to our mailinglist when done.


  • AP: HH to pass on question to IGE about which transport mechanism is intended to be used in Grid-SAFE.


  • AP: MB to send link with suggested extensions to OGF-UR by APEL to HH. HH to check within IGE if those extensions are sufficient for use in Grid-SAFE.
    Update: MB, checked again with John Gordon about current valid APEL extensions:
    • a) extensions to the basic UR, eg it didn't include the sitename for example. Cristina del Cano Novales wrote a comparison of our UR with the standard as input to OGF, after the Catania meeting. It is probably somewhere in GridForge but a quick browse didn't find it.
    • b) a variation on the UR that represented total CPU time etc for a number of jobs. We made the mistake of calling this the aggregated accounting record. Some people had a semantic problem with this name and expected it to contain a concatenation of all the job records. We should have called it a summary accounting record. http://forge.gridforum.org/sf/docman/do/listDocuments/projects.ur-wg/docman.root.current_drafts.aggregate_ur_schema
    • c) Cristina has proposed an updated APEL UR schema with the fields aligned more closely to the standard. This is list of fieldnames used in a relational database, not an XML DTD. This is being discussed in a special group in EMI chaired by Cristina: https://twiki.cern.ch/twiki/bin/view/EMI/ComputeAccounting



  • AP: MB to ask NGIs on desired timelines for Globus integration to determine need for a second Early Adopter team for Globus at current stage.
    • AP: TA to ask within NGI-DE for a second EA volunteer.


  • AP: MB to organize the next meeting as a dedicated accounting meeting with the accounting experts: either as a Phoneconference slot during the EGCF1 or in week 21 before the 2nd EMI allhands F2F in Lund.
    Update: Current status: Phonemeeting during EGCF1 on Wednesday afternoon possible. Details still defined between MB and HH, otherwise Monday the 23rd as backup option.
    Update: Meeting held on Wednesday as intended.
  • AP: (on request of COO after a discussion at the TCB): Which type of OS for GLOBUS resources will be used by the NGIs that plan to integrate their GLOBUS resources into EGI? This information is important for the integration of GLOBUS into the UMD.
    Update: "if we do not have sites that volunteer for EA activity in StagedRollout then there is no point in including that particular platform (e.g. CentOS on x86_64) in the UMD!"

Closed Actionpoints

  • AP: Fill mailinglist
  • AP: Decide on date for first meeting and put together an agenda.

https://www.egi.eu/indico/conferenceDisplay.py?confId=469

Retrieved from "https://wiki.egi.eu/w/index.php?title=EGI-InSPIRE:Globus_integration_task_force&oldid=17896"