Custom Query (138 matches)

bbn-hn installs software from the xCAT Yum repository, but doesn't keep that repo config file in /etc/yum.repos.d.

The ExoSM Ad Rspec lists at least one link twice:

urn:publicid:IDN+exogeni.net:acisrencivmsite+link+acisrencivmsite.rdf#AcisRenci/Euca/GigabitEthernet/1/ethernet

Per Tom Lehman's email, can you modify IDs for nodes, links, interfaces, and ports to match the conventions, and better support tools for interoperability?

b) The current format of a node, interface, and link component is:

node component_id="urn:publicid:IDN+geni-orca.renci.org+node+bbnNet.rdf#bbnNet/Domain/vlan" 
interface component_id="urn:publicid:IDN+geni-orca.renci.org+interface+bbnNet.rdf#BbnNet/IBM/G8052/TenGigabitEthernet/1/20/ethernet
link component_id=
    <interface_ref component_id="urn:publicid:IDN+geni-orca.renci.org+interface+bbnNet.rdf#BbnNet/IBM/G8052/TenGigabitEthernet/1/20/ethernet"/>
    <interface_ref component_id="urn:publicid:IDN+ion.internet2.edu+interface+rtr.newy:ae0"/>

The following adjustment would sync up with ProtoGENI practice better, and make it easier to correlate with stitching extension:

the basic rule is to construct the interface component_id by taking the node component_id portion after the "node+", and adding  ":anything-desired".  So a ":" demarc between the node and interface portions.  

Here is an example:

node component_id="urn:publicid:IDN+geni-orca.renci.org+node+bbnNet.rdf#bbnNet/Domain/vlan" 
interface component_id="urn:publicid:IDN+geni-orca.renci.org+interface+bbnNet.rdf#bbnNet/Domain/vlan:IBM/G8052/TenGigabitEthernet/1/20/ethernet
link component_id=
    <interface_ref component_id="urn:publicid:IDN+geni-orca.renci.org+interface+bbnNet.rdf#bbnNet/Domain/vlan:IBM/G8052/TenGigabitEthernet/1/20/ethernet"/>
    <interface_ref component_id="urn:publicid:IDN+ion.internet2.edu+interface+rtr.newy:ae0"/>

Would it be possible to use this format for all node, interface, and link component formations?