GLUE for describing resource requests (use case DGSI)
Hi, I'm working in the DGSI project (a German D-Grid project) where our goal is to design and implement an interoperability framework between community schedulers and community bound resources. More specifically, this include protocols and services for delegation of activities as well as resources. We are primarily basing our protocols on OGF standards and recommendations and have tight collaboration with both the GRAAP (WS-Agreement/Negotiation) and DCI-Fed working groups within OGF. In the first information model we decided to use GLUE 2.0 for both resource descriptions and resource request specification. However describing resource requests with GLUE turned out to be difficult to implement. The main issue that we have is the restrictions in the GLUE 2.0 XML schema which makes it difficult to use only specific elements/group of elements in a document instance. For example, we would like to use the AccessPolicy element to describe requirements on who (e.g. DN/VO) is authorized to access a delegated resource. But to use this element, we need to create the entire hierarchy with Service/ComputingService/ComputingEndpoint and their respective required elements (e.g. ID, QualityLevel, ...) when using the GLUE 2.0 XSD. Currently, our solution is to use JSDL for specifying both activity and resource delegation requests. However, JSDL is not sufficient for all our use cases/requirements and we would like to use GLUE for specifying resource requests in our next version. Is there any work going on in the glue-wg to make the XSD rendering more lenient towards other use cases such as resource requirement specification? Or making it possible to use a subset of GLUE and combine it with other info models such as JSDL? Thank you in advance and Best Regards, Mikael Högqvist
Hi Mikael, the new rendering of GLUE 2.0 that we are preparing will solve this issue. We'll contact you when a new draft will be ready, before the end of the year. Cheers, Sergio On 18 November 2010 12:27, Mikael Högqvist <hoegqvist@zib.de> wrote:
Hi,
I'm working in the DGSI project (a German D-Grid project) where our goal is to design and implement an interoperability framework between community schedulers and community bound resources. More specifically, this include protocols and services for delegation of activities as well as resources. We are primarily basing our protocols on OGF standards and recommendations and have tight collaboration with both the GRAAP (WS-Agreement/Negotiation) and DCI-Fed working groups within OGF.
In the first information model we decided to use GLUE 2.0 for both resource descriptions and resource request specification. However describing resource requests with GLUE turned out to be difficult to implement. The main issue that we have is the restrictions in the GLUE 2.0 XML schema which makes it difficult to use only specific elements/group of elements in a document instance.
For example, we would like to use the AccessPolicy element to describe requirements on who (e.g. DN/VO) is authorized to access a delegated resource. But to use this element, we need to create the entire hierarchy with Service/ComputingService/ComputingEndpoint and their respective required elements (e.g. ID, QualityLevel, ...) when using the GLUE 2.0 XSD.
Currently, our solution is to use JSDL for specifying both activity and resource delegation requests. However, JSDL is not sufficient for all our use cases/requirements and we would like to use GLUE for specifying resource requests in our next version.
Is there any work going on in the glue-wg to make the XSD rendering more lenient towards other use cases such as resource requirement specification? Or making it possible to use a subset of GLUE and combine it with other info models such as JSDL?
Thank you in advance and Best Regards, Mikael Högqvist _______________________________________________ glue-wg mailing list glue-wg@ogf.org http://www.ogf.org/mailman/listinfo/glue-wg
-- Sergio Andreozzi - Policy Development Manager EGI.eu - Amsterdam - The Netherlands - http://egi.eu
Hi Sergio, thats great news, thank you, Mikael On 29 November 2010 15:51, Sergio Andreozzi <sergio.andreozzi@egi.eu> wrote:
Hi Mikael, the new rendering of GLUE 2.0 that we are preparing will solve this issue. We'll contact you when a new draft will be ready, before the end of the year. Cheers, Sergio
On 18 November 2010 12:27, Mikael Högqvist <hoegqvist@zib.de> wrote:
Hi,
I'm working in the DGSI project (a German D-Grid project) where our goal is to design and implement an interoperability framework between community schedulers and community bound resources. More specifically, this include protocols and services for delegation of activities as well as resources. We are primarily basing our protocols on OGF standards and recommendations and have tight collaboration with both the GRAAP (WS-Agreement/Negotiation) and DCI-Fed working groups within OGF.
In the first information model we decided to use GLUE 2.0 for both resource descriptions and resource request specification. However describing resource requests with GLUE turned out to be difficult to implement. The main issue that we have is the restrictions in the GLUE 2.0 XML schema which makes it difficult to use only specific elements/group of elements in a document instance.
For example, we would like to use the AccessPolicy element to describe requirements on who (e.g. DN/VO) is authorized to access a delegated resource. But to use this element, we need to create the entire hierarchy with Service/ComputingService/ComputingEndpoint and their respective required elements (e.g. ID, QualityLevel, ...) when using the GLUE 2.0 XSD.
Currently, our solution is to use JSDL for specifying both activity and resource delegation requests. However, JSDL is not sufficient for all our use cases/requirements and we would like to use GLUE for specifying resource requests in our next version.
Is there any work going on in the glue-wg to make the XSD rendering more lenient towards other use cases such as resource requirement specification? Or making it possible to use a subset of GLUE and combine it with other info models such as JSDL?
Thank you in advance and Best Regards, Mikael Högqvist _______________________________________________ glue-wg mailing list glue-wg@ogf.org http://www.ogf.org/mailman/listinfo/glue-wg
-- Sergio Andreozzi - Policy Development Manager EGI.eu - Amsterdam - The Netherlands - http://egi.eu
Hi Sergio, how is the new rendering getting along? :-) Best, Andre. On Mon, Nov 29, 2010 at 3:51 PM, Sergio Andreozzi <sergio.andreozzi@egi.eu> wrote:
Hi Mikael, the new rendering of GLUE 2.0 that we are preparing will solve this issue. We'll contact you when a new draft will be ready, before the end of the year. Cheers, Sergio
On 18 November 2010 12:27, Mikael Högqvist <hoegqvist@zib.de> wrote:
Hi,
I'm working in the DGSI project (a German D-Grid project) where our goal is to design and implement an interoperability framework between community schedulers and community bound resources. More specifically, this include protocols and services for delegation of activities as well as resources. We are primarily basing our protocols on OGF standards and recommendations and have tight collaboration with both the GRAAP (WS-Agreement/Negotiation) and DCI-Fed working groups within OGF.
In the first information model we decided to use GLUE 2.0 for both resource descriptions and resource request specification. However describing resource requests with GLUE turned out to be difficult to implement. The main issue that we have is the restrictions in the GLUE 2.0 XML schema which makes it difficult to use only specific elements/group of elements in a document instance.
For example, we would like to use the AccessPolicy element to describe requirements on who (e.g. DN/VO) is authorized to access a delegated resource. But to use this element, we need to create the entire hierarchy with Service/ComputingService/ComputingEndpoint and their respective required elements (e.g. ID, QualityLevel, ...) when using the GLUE 2.0 XSD.
Currently, our solution is to use JSDL for specifying both activity and resource delegation requests. However, JSDL is not sufficient for all our use cases/requirements and we would like to use GLUE for specifying resource requests in our next version.
Is there any work going on in the glue-wg to make the XSD rendering more lenient towards other use cases such as resource requirement specification? Or making it possible to use a subset of GLUE and combine it with other info models such as JSDL?
Thank you in advance and Best Regards, Mikael Högqvist _______________________________________________ glue-wg mailing list glue-wg@ogf.org http://www.ogf.org/mailman/listinfo/glue-wg
-- Sergio Andreozzi - Policy Development Manager EGI.eu - Amsterdam - The Netherlands - http://egi.eu
_______________________________________________ glue-wg mailing list glue-wg@ogf.org http://www.ogf.org/mailman/listinfo/glue-wg
-- Nothing is ever easy...
participants (3)
-
Andre Merzky -
Mikael Högqvist -
Sergio Andreozzi