- glue-wg - lists.ogf.org

call on the 7th of may?
by Florido Paganelli 20 May '13

20 May '13

Hi all, JP once asked me to report on LDAP status the 7th of May. Is a meeting planned for that date or not? Cheers, Florido -- ================================================== Florido Paganelli ARC Middleware Developer - EMI Project System Administrator Lund University Department of Physics Division of Particle Physics BOX118 221 00 Lund Office Tel: 046-2220272 Email: florido.paganelli(a)REMOVE_THIShep.lu.se ==================================================

3 3

FW: [Editor - document #70] GLUE v. 2.0 – Reference Realization to XML Schema
by david.meredith＠stfc.ac.uk 23 Apr '13

23 Apr '13

Hi all, FYI the Glue2 XML doc is now in public comment until July 20th, see: http://redmine.ogf.org/projects/editor-pubcom/boards Cheers David > -----Original Message----- > From: redmine(a)ogf.org [mailto:redmine@ogf.org] > Sent: 22 April 2013 13:39 > Subject: [Editor - document #70] GLUE v. 2.0 – Reference Realization to XML > Schema > > > Issue #70 has been updated by Redmine Admin. > > Assignee changed from Andre Merzky to Greg Newby > > Is now in public comment until July 20th > ---------------------------------------- > document #70: GLUE v. 2.0 – Reference Realization to XML Schema > https://redmine.ogf.org/issues/70#change-155 > > Author: David Meredith > Status: public comment > Priority: Normal > Assignee: Greg Newby > Category: > Target version: > Document Type: Proposed Recommendation > > > This document provides the realization of the GLUE 2 information model > (v.2.0) as XML Schema. > > > -- > You have received this notification because you have either subscribed to it, > or are involved in its topic. > To change your notification preferences, please click here: > http://redmine.ogf.org/my/account

2 1

author list for XML rendering
by david.meredith＠stfc.ac.uk 27 Mar '13

27 Mar '13

Hi everyone, As I am sure you are aware, we have been working on the GLUE2 XML rendering over the last 6mths or so. We are now at a stage where we would like to submit the doc for public comment. The document has changed considerably since the previous version - the XSD is now based on 'flat' rendering using ID ref elements (rather than defining hierarchical/nested XSD) and includes abstract elements with substitution groups to model inheritance and extensibility. Despite the extent of these changes, we have carried over and modified a number of complex type definitions and constructs from the previous (hierarchical) document. With this in mind, a consensus for the author list and for additional acknowledgements is required. Note, given the extent of the changes, I don't want to submit the doc to public comment with names that I don't recognise but who have made important contributions in the past. Therefore, can you please let me know your preference/guidance? i.e. whether you still want to be named as an author (or not - you may not agree with the changes) or feel an acknowledgement is more suitable given the changes? Thanks for any clarifications, David ========================== David Meredith Scientific Computing Dept Daresbury Laboratory Tel: +44 (0) 1925 603762 Fax: +44 (0) 1925 603100 (Site) Email: david.meredith(a)stfc.ac.uk Skype name: davidismeredith -- Scanned by iCritical.

4 7

Re: [glue-wg] Information has been added
by david.meredith＠stfc.ac.uk 13 Mar '13

13 Mar '13

Hi Laurence, At OGF yesterday we agreed to move the GLUE2 XML rendering into public comment within the next few weeks. The XSD, draft GFD and examples are at the link[1] below. A prior question however: Wouldn't it be prudent to consider common names for XML elements and JSON-attributes across the two different renderings, especially the elements/attributes used to define the relationships between entities? Currently, the XML rendering adopts a naming scheme that uses referenced element with the suffix 'ID' (e.g. to reference an endpoint, an entity defines a Ref element called '<EndpointID> ' within its '<Associations>' element). Importantly, as described in section 3.5.1 in the attached doc, we name the Ref element after the referenced element's super-class (if applicable). This is to cater for a well-defined use-case: It allows standard queries to be executed on an instance document regardless of the referenced entity sub-type (I understand that this preference/use-case emerged with use of the LDAP rendering). Conversely however, I see that in your JSON rendering you are specifically naming the attribute after the referenced entity-sub-type specialisation, e.g. 'executionenvironmentforeignkey' rather than 'resourceforeignkey' (resource being the executionenv's abstract super-class). What are your thoughts? Cheers David [1]http://redmine.ogf.org/dmsf/glue-wg?folder_id=31 > -----Original Message----- > From: Laurence [mailto:Laurence.Field@cern.ch] > Sent: 12 March 2013 10:16 > To: Stefan Roiser > Cc: Maria Alandes Pradillo; infosys-discuss (Grid Information System > Discussion List) > Subject: Re: Information has been added > > Hi Stefan, > > I have added the benchmark to the nested view. > > http://gsr.cern.ch/apps/gsr/nested/json > > This is a little more complicated due to the relationships. The benchmark a > sub-object of the execution environment (the hardware). The share is > related to an execution environment (executionenvironmentforeignkey). > > Laurence > > > > > On 03/11/2013 03:19 PM, Stefan Roiser wrote: > > Hi Laurence > > > > Correct, yes this would be useful to have, e.g. would make some page > obsolete I'm currently maintaining for LHCb. > > > > cheers > > > > Stefan > > > > On 11 Mar 2013, at 15:17, Laurence <Laurence.Field(a)cern.ch> wrote: > > > >> The power is a property of the computing hardware, not the queue. We > can advertise the power of the hardware and indicate what hardware your > queue can access. > >> > >> Laurence > >> > >> > >> On 03/11/2013 02:52 PM, Stefan Roiser wrote: > >>> Hi, > >>> > >>> for what concerns the queues could we add info on the SI2K power of > the queue? This would allow us to calculate the queue length, or maybe this > could be done directly on the page in HepSpec06.seconds (i.e. > MaxCPU*SI2K*60/250) ? > >>> > >>> cheers > >>> > >>> Stefan > >>> > >>> On 5 Mar 2013, at 16:55, Maria Alandes Pradillo > <Maria.Alandes.Pradillo(a)cern.ch> wrote: > >>> > >>>> Hi Laurence, > >>>> > >>>> I would like to write here Andrea's proposal formulated at the end of > the meeting: > >>>> > >>>> We should be able to show the following information in REBUS: > >>>> > >>>> For each site, list the computing endpoints (Endpoint Record view) > >>>> For each computing endpoint, list the available computing managers > >>>> (batch system) (Computing Manager view) For each computing > manager, > >>>> list the available queues including Max Wallclock time and Max CPU > >>>> time (Computing Share view) > >>>> > >>>> Display this information per VO and FQAN (This is missing) > >>>> > >>>> Would it be useful for the discussion to create a "Job Submission view" > displaying: > >>>> > >>>> Site Name > >>>> Computing Endpoint > >>>> Computing Manager > >>>> Queue > >>>> Max Wallclock time > >>>> Max CPU time > >>>> VO name > >>>> FQAN > >>>> > >>>> Is it possible? > >>>> > >>>> Thanks! > >>>> Maria > >>>> > >>>> > >>>> > >>>>> -----Original Message----- > >>>>> From: Laurence Field > >>>>> Sent: 05 March 2013 16:41 > >>>>> To: infosys-discuss (Grid Information System Discussion List) > >>>>> Subject: Information has been added > >>>>> > >>>>> I have added the queue name to the Computing Share > (mappingqueue) > >>>>> and a new object Computing Manager than contains the > productname > >>>>> and product version. The objects Service Endpoint, Computing Share > >>>>> and Computing Manager all now now a foriegnkey to the Service > >>>>> > >>>>> http://gsr.cern.ch/apps/gsr/computingmanager/html > >>>>> > >>>>> All the information is now there for creating the flat json structure. > >>>>> > >>>>> Laurence > >>> --- > >>> Stefan Roiser, CERN, IT Department, CH-1211 Geneva 23, +41 76 > >>> 4875334 > >>> > >>> > >>> > >>> > >>> > >>> > > --- > > Stefan Roiser, CERN, IT Department, CH-1211 Geneva 23, +41 76 4875334 > > > > > > > > > > > > -- Scanned by iCritical.

2 2

Correction: OGF Glue Session Tomorrow
by Shiraz Memon 11 Mar '13

11 Mar '13

I have mistakenly mentioned the wrong international timings. Tuesday March 2013 (12.03.2013) Session I: 08:30 AM - 10:00 AM (13:30 - 15:00 CET) Session II: 10:30 AM - 12:00 PM (15:30 - 17:00 CET) Shiraz On Mon, Mar 11, 2013 at 1:50 PM, Shiraz Memon <a.memon(a)fz-juelich.de<mailto:a.memon@fz-juelich.de>> wrote: Dear WG, We will have two GLUE sessions at the OGF 37 tomorrow. The agenda is as follows: Session #1: 1) Working Group Status, JP Navarro (15') 2) XML Rendering document review, David Meredith (45') 3) GLUE 2 Unified/Psuedo-standard enumerations, Florido Paganelli (30') Session #2: 4) XSEDE GLUE 2 Update, Warren Smith (10') 5) JSON Rendering Discussion, Warren Smith & Shiraz Memon (20') 6) Big Data in GLUE 2, Morris Riedel (20') Date and Timings: Tuesday March 2013 (12.03.2013) Session I: 08:30 AM - 10:00 AM (14:30 - 16:00 CET) Session II: 10:30 AM - 12:00 PM (16:30 - 18:00 CET) Here are the meeting co-ordinates for the participants who would like to join remotely. URL: https://webconf.vc.dfn.de/ogf-glue-wg/ Login as Guest using your real name Best regards, -- Ahmed Shiraz Memon Federated Systems and Data Jülich Supercomputing Centre (JSC) Phone: +49 2461 61 6899<tel:%2B49%202461%2061%206899> Fax: +49 2461 61 6656<tel:%2B49%202461%2061%206656> -- Ahmed Shiraz Memon Federated Systems and Data Jülich Supercomputing Centre (JSC) Phone: +49 2461 61 6899 Fax: +49 2461 61 6656 ------------------------------------------------------------------------------------------------ ------------------------------------------------------------------------------------------------ Forschungszentrum Juelich GmbH 52425 Juelich Sitz der Gesellschaft: Juelich Eingetragen im Handelsregister des Amtsgerichts Dueren Nr. HR B 3498 Vorsitzender des Aufsichtsrats: MinDir Dr. Karl Eugen Huthmacher Geschaeftsfuehrung: Prof. Dr. Achim Bachem (Vorsitzender), Karsten Beneke (stellv. Vorsitzender), Prof. Dr.-Ing. Harald Bolt, Prof. Dr. Sebastian M. Schmidt ------------------------------------------------------------------------------------------------ ------------------------------------------------------------------------------------------------

1 0

OGF Glue Session Tomorrow
by Shiraz Memon 11 Mar '13

11 Mar '13

Dear WG, We will have two GLUE sessions at the OGF 37 tomorrow. The agenda is as follows: Session #1: 1) Working Group Status, JP Navarro (15') 2) XML Rendering document review, David Meredith (45') 3) GLUE 2 Unified/Psuedo-standard enumerations, Florido Paganelli (30') Session #2: 4) XSEDE GLUE 2 Update, Warren Smith (10') 5) JSON Rendering Discussion, Warren Smith & Shiraz Memon (20') 6) Big Data in GLUE 2, Morris Riedel (20') Date and Timings: Tuesday March 2013 (12.03.2013) Session I: 08:30 AM - 10:00 AM (14:30 - 16:00 CET) Session II: 10:30 AM - 12:00 PM (16:30 - 18:00 CET) Here are the meeting co-ordinates for the participants who would like to join remotely. URL: https://webconf.vc.dfn.de/ogf-glue-wg/ Login as Guest using your real name Best regards, -- Ahmed Shiraz Memon Federated Systems and Data Jülich Supercomputing Centre (JSC) Phone: +49 2461 61 6899 Fax: +49 2461 61 6656 ------------------------------------------------------------------------------------------------ ------------------------------------------------------------------------------------------------ Forschungszentrum Juelich GmbH 52425 Juelich Sitz der Gesellschaft: Juelich Eingetragen im Handelsregister des Amtsgerichts Dueren Nr. HR B 3498 Vorsitzender des Aufsichtsrats: MinDir Dr. Karl Eugen Huthmacher Geschaeftsfuehrung: Prof. Dr. Achim Bachem (Vorsitzender), Karsten Beneke (stellv. Vorsitzender), Prof. Dr.-Ing. Harald Bolt, Prof. Dr. Sebastian M. Schmidt ------------------------------------------------------------------------------------------------ ------------------------------------------------------------------------------------------------

1 0

updated Glue2 XSD and GFD
by david.meredith＠stfc.ac.uk 11 Mar '13

11 Mar '13

Dear all, In prep for tomorrows OGF GLUE2 meeting, I updated the XSD, XML example docs and GFD which can be downloaded from the following folder (also in zip attached): http://redmine.ogf.org/dmsf/glue-wg?folder_id=31 I highlighted a few minor TODOs in the README.txt and provided examples of doc validation using xmllint. Tomorrow we can go through the doc, point out the key features and hopefully agree to publish for public comment. Thanks David ========================== David Meredith Scientific Computing Dept Daresbury Laboratory Tel: +44 (0) 1925 603762 Fax: +44 (0) 1925 603100 (Site) Email: david.meredith(a)stfc.ac.uk Skype name: davidismeredith -- Scanned by iCritical.

1 0

DN encoding discussion and agreement
by JP Navarro 04 Mar '13

04 Mar '13

The GLUE Specification v. 2.0: http://redmine.ogf.org/dmsf/glue-wg?folder_id=18 with regard to X.509 Distinguished Names (section A.12) and the DN_t (B.13) incorrectly references IETF RFC 4514. In our last call we agreed to replace the reference to the RFC with text describing the de facto GLUE 2 interoperable format for DNs is the legacy OpenSSL format with a syntax like "/C=foo/O=bar/cn=person". This change would result in a corrected/errata specification release. We also decided NOT to add anything to the specification about alternate DN formats, but instead to start working group discussions about other standard format(s) that to be added to the specification int the future. Thanks, JP

1 0

XSD design choice related to LDAP
by david.meredith＠stfc.ac.uk 28 Feb '13

28 Feb '13

Dear WG, For the GLUE2 XML rendering we have a design choice that I understand was also relevant in the design of the LDAP schema. Some feedback would be most helpful, especially as I understand that user requirements triggered similar changes in the LDAP schema (i.e. from style A to B as described below?) Q. In the conceptual spec, when an entity inherits associations from a super class it usually redefines the inherited associations. For example, ComputingService redefines its inherited 'Endpoint.ID' to 'ComputingEndpoint.ID.' Similarly, StorageService redefines its inherited 'Endpoint.ID' to 'StorageEndpoint.ID'. Therefore, should we reflect these redefinitions in the XML element names (or not), e.g. option A or B below? I think the strength of A is that it is made clear that a ComputingService SHOULD (or is this MUST?) reference a ComputingEndpoint. The strength of B is that queries can be more standard across different implementations (akin to polymorphic queries, .e.g. the following XPath could be used to query for all endpoint IDs from all service implementations: "/Entities/*[@BaseType='Service']/Associations/EndpointID"). There are strengths with both approaches and the decision I think has to be driven by use-case experience, hence I put this to the LDAP folks. Thanks in advance, David Option A: Redefine the associations (e.g. ComputingEndpointID, ComputingShareID) ================================================================== <ComputingService BaseType="Service"> <ID>computingService1</ID> ... <Associations> <ComputingEndpointID>computingEndpoint1</ComputingEndpointID> <ComputingShareID>someShare</ComputingShareID> </Associations> </ComputingService> Option B: Don't redefine the associations (e.g. use inherited EndpointID, ShareID) =============================================================== <ComputingService BaseType="Service"> <ID>computingService1</ID> ... <Associations> <EndpointID>computingEndpoint1</EndpointID> <ShareID>someShare</ShareID> </Associations> </ComputingService> ========================== David Meredith Scientific Computing Dept Daresbury Laboratory Tel: +44 (0) 1925 603762 Fax: +44 (0) 1925 603100 (Site) Email: david.meredith(a)stfc.ac.uk Skype name: davidismeredith -- Scanned by iCritical.

2 2

Meeting Reminder
by Shiraz Memon 28 Feb '13

28 Feb '13

Dear All, We will meet tomorrow to continue discussing the pending items from our last meeting. Date & Time: 26.03.2013, 16:00-~17:30 CET, 10:00-~11:30 US Eastern URL: Sign-in on ogf-glue-wg<https://webconf.vc.dfn.de/ogf-glue-wg/> as a Guest using your real name. Agenda Items: 1) Progress on XML rendering document and related issues: use of BaseType, union or annotation based open enumerations, public comment etc... 2) Updating the XML Schemas on GitHub source repository (implies snyc. with the latest rendering document) 3) Progress on unified enumerations 4) LDAP rendering update 5) OGF 37 preparation Best regards, Shiraz -- Ahmed Shiraz Memon Federated Systems and Data Jülich Supercomputing Centre (JSC) Phone: +49 2461 61 6899 Fax: +49 2461 61 6656 ------------------------------------------------------------------------------------------------ ------------------------------------------------------------------------------------------------ Forschungszentrum Juelich GmbH 52425 Juelich Sitz der Gesellschaft: Juelich Eingetragen im Handelsregister des Amtsgerichts Dueren Nr. HR B 3498 Vorsitzender des Aufsichtsrats: MinDir Dr. Karl Eugen Huthmacher Geschaeftsfuehrung: Prof. Dr. Achim Bachem (Vorsitzender), Karsten Beneke (stellv. Vorsitzender), Prof. Dr.-Ing. Harald Bolt, Prof. Dr. Sebastian M. Schmidt ------------------------------------------------------------------------------------------------ ------------------------------------------------------------------------------------------------

2 2