Custom Query (1408 matches)

Our GPO run Clearinghouse is changing host names and the root certificate.

The ION aggregate should install 2 new trusted root certificates.

These certificates are posted here: ​http://groups.geni.net/geni/wiki/GeniTrustAnchors

The 2 particular files to install are: ​http://groups.geni.net/geni/attachment/wiki/GeniTrustAnchors/ch.geni.net-ca.pem ​http://groups.geni.net/geni/attachment/wiki/GeniTrustAnchors/ch.geni.net-ma.pem

ExoGENI Ad RSpecs include generally 2 URLs comma separated in the url attribute.

1 of these is the ExoSM, the other is the individual rack.

What should the SCS report in the workflow?

Options:

1. Both. Then the tools have to figure out what to do
2. Only the local rack.

I vote #2. Pick that by picking the URL that is not "geni.renci.org". This is probably the 2nd URL.

Sample element:

            <ns2:aggregate id="urn:publicid:IDN+exogeni.net:nictaNet+authority+am" url="https://geni.renci.org:11443/xmlrpc,https://nicta-hn.exogeni.net:11443/xmlrpc">      

Hops that the SCS adds that traverse ION use the capabilities tag which is schema v2. But the rspecs otherwise use stitching schema v0.1.

So requests from the SCS do not validate against the schemas.

We want that information, but it would be nice to do so in a schema compliant way.