[glue-wg] New Endpoint and Service types

Bartosz Bosak bbosak at man.poznan.pl
Mon Mar 10 07:50:32 EDT 2014


Dear Stephen,

We have implemented our preliminary providers for the QCG services on top
of the scripts available under package emi-resource-information-service.
Now we are going to create relevant RPMs. Meanwhile, I have a couple of
questions:
1. Do we need to publish data into both glue1 and glue2 or just into glue2?

2. It seems that the capability "notification" is not present in the
supported capabilities of the validator? If this is a purposeful
configuration, what capability should we select for the QCG-Notification
service? If not, could we ask for addtion of the "notification" capability?

3. We have a doubt about publication of site-ID. The scripts, e.g.
glite-info-glue2-simple, require provisioning of site-ID, but I don't know
how and from which place, this information can be acquired... Is there some
instruction or standard way of doing this?

4. Can you estimate when requested EndpointInterfaceName(s) and
ServiceType(s) (and maybe new capability for QCG-Notification) will be
present in the appropriate places?

Best Regards,
Bartek



2014-03-03 15:08 GMT+01:00 <stephen.burke at stfc.ac.uk>:

> Bartosz Bosak [mailto:bbosak at man.poznan.pl] said:
> > Could you check if new ServiceTypes/EndpointInterfaceNames for the QCG
> middleware have been registered in GLUE 2? Now we have some time > and we
> would like to move forward with the implementation of our publishers for
> BDII...
>
> I haven't seen anyone disagree with them. None of the names are in use,
> and the org.qcg names are your own name space anyway.
> org.oasis.notification is something which could potentially be relevant to
> other people, but assuming that it's just a vanilla implementation of a
> standard I don't see that it would be controversial. Unless anyone has a
> strong objection now I'd suggest that you go ahead with your implementation.
>
> Stephen
>
> --
> Scanned by iCritical.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.ogf.org/pipermail/glue-wg/attachments/20140310/6cacc1de/attachment.html>


More information about the glue-wg mailing list