EGI-InSPIRE:Globus integration task force

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 on everybody: Advertise First Globus community Forum Meeting http://www.ige-project.eu/events/egcf1

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

Update: JR and other people on the LRZ testbed to get the missing Globus log part of the RUS publisher client, the harvester, from the original NeSCForge (or Steven Booth) and adept it according to their needs.

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

Answer: SOAP over https.

• 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

  Update: Update: IGE (SC) contacts the EMI ComputeAccounting over their mailinglist and actively participates in the UR fields analysis.

• AP: HH (or somebody else from IGE) to provide more details and timelines on IIS in the https://rt.egi.eu/rt/Ticket/Display.html?id=390 RT ticket and our mailinglist after the EGCF1

• 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

• AP: Create mailinglist and doodle first meeting. http://www.doodle.com/zhxx9wsn589asn2f