Custom Query (138 matches)
Results (13 - 15 of 138)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #63 | fixed | RSpecs: ugly node component_name | ||
| Description |
The component_name on nodes is a little ugly. Typically, this is teh end part of the component_id (the part after +node+). But not in these RSpecs. Could we clean that up? Not a big deal. |
|||
| #65 | fixed | Ad RSpec: Duplicate link | ||
| Description |
The ExoSM Ad Rspec lists at least one link twice: urn:publicid:IDN+exogeni.net:acisrencivmsite+link+acisrencivmsite.rdf#AcisRenci/Euca/GigabitEthernet/1/ethernet |
|||
| #68 | fixed | RSpecs: Manifest lists AM ID as the component_id | ||
| Description |
Using the NICTA tutorial request RSpec, I get a manifest like:
<node client_id="f830d586-f392-49da-a7fa-10adeb97a815#geni1" component_id="urn:publicid:IDN+exogeni.net:nictavmsite+authority+am" exclusive="true" sliver_id="urn:publicid:IDN+exogeni.net:nictavmsite+sliver+f830d586-f392-49da-a7fa-10adeb97a815#geni1">
Note the component_id is for an AM. It should be for a node. |
|||
Note: See TracQuery
for help on using queries.
