November 2012 - glue-wg - lists.ogf.org

Decision on Flat XML Schema
by Shiraz Memon 13 Nov '12

13 Nov '12

Dear Glue’s, After continued requirements analysis within the WG and at OGF 35/36, we would like to propose that the flat XSD style is adopted as the official GLUE2 XML rendering style over the nested/hierarchical style (or a combined approach). The main reasons for this style choice are summarised below. Further details, including a pro/con comparison are available from the WG’s wiki (see http://redmine.ogf.org/dmsf_files/176?download=) At the time of decision on the flat schema, the group is aware that there are early implementations of GLUE2 XML rendering that use a formerly proposed hierarchical XSD schema. For the sake of inter-operability and compatibility between implementations, when considering the flat schema as the official one, the OGF GLUE group will guide (on best effort basis) on how to create a mapping between the previous hierarchical XSD schema and the agreed flat XSD schema. If you have any remaining concerns regarding this style choice, please respond before 25th Nov. If we hear no major concerns before this date, we will progress with an update to the GFD and XSD for subsequent submission to the OGF. Summary of the main reasons for a flat over nested/combined approach: 1. The flat style enables a single document root element (<Entities>). This acts as an element bag that lists Glue entity elements in a defined order. 2. The flat style more efficiently models many-to-many associations and a child with multiple parents (style mixing is unnecessary, no combinations of nesting and ID refs). 3. The flat style is better suited for rendering the results of ‘projection’ queries, i.e. queries that slice the data and return selected entities. The nested style is less efficient as you need to cascade render all children/grandchildren/so on for completeness (whereas the flat style can simply show that an association exists using an element ID reference, which means that the whole entity graph does not need to be rendered). 4. Abstract elements with corresponding xsd:substitutionGroups and concrete entity implementations will be included within the base schema. Only those concrete entity implementations defined within this XSD will be used for interop/compliance. However, this extension mechanism facilitates profiling of new sub-type specialisations in the future without having to modify the base schema. 5. We recognise that the flat approach requires extra steps when validating as it is necessary to check the correctness of associations by traversing/cross referencing the element IDs. However, we believe the extra benefits provided by the flat approach outweigh the drawback of this additional validation step. 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> ------------------------------------------------------------------------------------------------ ------------------------------------------------------------------------------------------------ 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 ------------------------------------------------------------------------------------------------ ------------------------------------------------------------------------------------------------ Kennen Sie schon unsere app? http://www.fz-juelich.de/app

1 0

Custom DateTime types in glue XSD
by Shiraz Memon 12 Nov '12

12 Nov '12

Hi, In the current xml schema[1] the datetime types are customised to enforced specific pattern (similar to UTC). Doing this would make schema less intuitive for the xml binding libraries, first in terms of validation and secondly a desired formatted string has to be crafted. Interestingly the default xsd "datetime" type already allows both UTC and ISO8601. It is then up to the service developers to which date interchangeable format do they want to use. If you agree and foresee less changes on your side, I can update the given schema to use xsd:dateTime instead of glue:DateTime_t. If necessary or unclear, we can discuss this in our meeting tomorrow. [1] https://github.com/OGF-GLUE/XSD/blob/master/schema/GLUE2.xsd Cheers, 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 ------------------------------------------------------------------------------------------------ ------------------------------------------------------------------------------------------------ Kennen Sie schon unsere app? http://www.fz-juelich.de/app

3 6

GLUE WG teleconference, Thursday, November 7, 2012
by JP Navarro 08 Nov '12

08 Nov '12

Greetings Glue WG, Coordinates and agenda for tomorrow's GLUE WG teleconference follow: Coordinates: : Thursday, November 8, 2012 : 16:00-17:00 Central Europe, 10:00-11:00 AM US Eastern Teleconference and screen sharing: : https://webconf.vc.dfn.de/ogf-glue-wg/ (Adobe Connect) : Login as Guest using your real name Agenda: 1) GLUE adoption in XSEDE (Warren, 15 minutes) 2) GLUE adoption in EMI-ES (Florido, 15 minutes) 3) GLUE adoption in ARC (Florido, 15 minutes) 4) Any other adoptions? See you tomorrow, Shiraz Memon JP Navarro

2 5

Redmine
by stephen.burke＠stfc.ac.uk 07 Nov '12

07 Nov '12

Hi, I just noticed that our main page at http://www.ogf.org/gf/group_info/view.php?group=glue still points to gridforge, presumably it should change to redmine? Secondly, I wanted to look at the known issues page in the wiki, but if I look here: http://redmine.ogf.org/projects/glue-wg/wiki most of the links are dead including the known issues - what happened? Stephen -- Scanned by iCritical.

4 5

Endpoint.TrustedCA and ComputingEndpoint.TrustedCA Inconsistency in GFD147
by Florido Paganelli 02 Nov '12

02 Nov '12

Hi all, We recently stumbled upon problems while running EMI-ES integration tests across EMI middleware. The reason is there are different descriptions and therefore different interpretations of the TrustedCA attribute in Endpoint and ComputingEndpoint. Here are the two relevant tables in GFD147: Entity Inherits from Description Endpoint Entity <http://glue20.web.cern.ch/glue20/#tableEntity> A network location having a well-defined interface and exposing specific service functionalities. Attribute Type Mult. Unit Description TrustedCA DN_t <http://glue20.web.cern.ch/glue20/#b13> 0..* The Distinguished Name of a trusted Certification Authority (CA); i.e., certificates issued by the CA are accepted by the authentication process. Alternatively this may identify a standard bundle of accepted CAs, e.g. those accredited by the IGTF. Note that this does not imply that such certificates will be authorized to use the Endpoint <http://glue20.web.cern.ch/glue20/#tableEndpoint>. Entity Inherits from Description ComputingEndpoint Endpoint <http://glue20.web.cern.ch/glue20/#tableEndpoint> A network Endpoint for creating, monitoring, and controlling computational Activities called jobs. It MAY also be used to expose complementary capabilities (e.g., resource reservation or proxy manipulation). Inherited Attribute Type Mult. Unit Description TrustedCA DN_t <http://glue20.web.cern.ch/glue20/#b13> 0..* Distinguished name of the trusted Certification Authority (CA), i.e., certificates issued by the CA are accepted for the authentication process I just don't understand this sentence: "Alternatively this may identify a standard bundle of accepted CAs, e.g. those accredited by the IGTF. Note that this does not imply that such certificates will be authorized to use the Endpoint." Does "This" still mean a DN or a string? In GLUE2 every attribute value has a very well defined type, in this case DN_t. DN_t is a distingushed name as defined by RFC4514 (http://www.ietf.org/rfc/rfc4514.txt) but how can a DN represent a bundle of accepted CAs? gLite middleware is using a plain string there, for example IGTF. But IGTF is NOT a DN_t. This was also one of the things I didn't understand in Stephen's EGI GLUE2 profile. Can anybody comment on this? Sometimes these GLUE2 inconsistencies make me crazy :P -- Florido Paganelli Lund University - Particle Physics ARC Middleware EMI Project

3 13