Opened 11 years ago
Closed 11 years ago
#27 closed (fixed)
Ad RSpec: follow node/link/interface ID conventions
Reported by: | ahelsing@bbn.com | Owned by: | ibaldin@renci.org |
---|---|---|---|
Priority: | major | Milestone: | |
Component: | AM | Version: | SPIRAL4 |
Keywords: | Cc: | ||
Dependencies: |
Description
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?
Change History (4)
comment:1 Changed 11 years ago by
Owner: | changed from somebody to ibaldin@renci.org |
---|---|
Status: | new → assigned |
comment:2 Changed 11 years ago by
See related comments on ticket #44.
Try to make link component_id reference what you are linking TO. Current IDs seems to be identical to the interface IDs (except for changing 'interface' to 'link').
comment:3 Changed 11 years ago by
Here is a sample link element showing how you could construct a link component_id such that it clearly indicates what is being connected:
<link component_name="procurve-pgeni-losa//eth5//ion" component_id="urn:publicid:IDN+emulab.net+link+procurve-pgeni-losa:3.31-ion.internet2.edu+interface+rtr.wash:ge-7/1/3"> <component_manager name="urn:publicid:IDN+emulab.net+authority+cm"/> <interface_ref component_id="urn:publicid:IDN+ion.internet2.edu+interface+rtr.wash:ge-7/1/3"/> <interface_ref component_id="urn:publicid:IDN+emulab.net+interface+procurve-pgeni-losa:3.31"/> </link>
comment:4 Changed 11 years ago by
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
Note: See
TracTickets for help on using
tickets.
This should be an easy fix.