Currently, cumin (or any Aviary client) can only connect to the scheduler or query server endpoints based on a pre-configured host and port.
1) per-pool standalone service (SOAP or REST) that the Aviary providers register with, and can be queried by cumin
2) modify the Condor plugin API so that plugins can push endpoint data to the Collector ClassAd, which in turn could be inserted into a QMF collector object property
Have you chosen any of these 2 options? How can we test this bug?
Likely using an approach of communication over SOAP between the Aviary plugins, query server, and a new Aviary collector plugin that binds the endpoint references.
Not expected until post Sept 30.
How we can test this feature? Is there any description how to setup it?
Technical note added. If any revisions are required, please edit the "Technical Notes" field
accordingly. All revisions will be proofread by the Engineering Content Services team.
Cause: Cumin needed a means to locate Aviary SOAP endpoints.
Consequence: Cumin was unable to find Aviary SOAP endpoints that may have been activated with ephemeral ports.
Change: WSDL, XSD and code was designed and developed to provide a SOAP interface to locate other SOAP endpoints.
Result: Cumin can retrieve Aviary SOAP endpoints through a well-known point of contact.
$CondorVersion: 7.8.8 Dec 14 2012 BuildID: RH-7.8.8-0.1.el6 $
$CondorPlatform: X86_64-RedHat_6.3 $
on RHEL 5.9/6.4 x i386/x86_64 and it works. --> VERIFIED
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.