Custom Query (1408 matches)

slicerstatus output should look like the below:

{'geni_expires': '2013-05-17T13:30:10.000-04:00',
 'geni_resources': [{'geni_error': '',
                     'geni_status': 'failed',
                     'geni_urn': 'urn:publicid:IDN+emulab.net+sliver+xilocaltest1_vlan_ion.internet2.edu-16571'}],
 'geni_status': 'failed',
 'geni_urn': 'urn:publicid:IDN+emulab.net+slice+xilocaltest1'}

The ION aggregate seems to die if the project name (sub-authority) contains a hyphen. It also dies if there is a hyphen in the client_ids.

Sample errors:

ERROR:omni: {'output': "Internal API error: <Fault 102: 'person_id 2: 
AddPersonToSite: Invalid argument: No such site'>", 'geni_api': 2, 
'code': {'am_type': 'sfa', 'geni_code': 5, 'am_code': 5}, 'value': ''}

ERROR:omni: {'output': "Internal API error: <Fault 102: 'person_id 2: 
AddSite: Invalid argument: Login base must consist only of lowercase 
ASCII letters or numbers'>", 'geni_api': 2, 'code': {'am_type': 'sfa', 
'geni_code': 5, 'am_code': 5}, 'value': ''}

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">