Custom Query (138 matches)

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?

Individual racks (not ExoSM) should include a proper stitching extension ad: include the extension once, with a single aggregate.

Follow Tom Lehman's rules for populating that extension:

-Identify all mainBody:link elements which have a link->interface_ref component_id which is for an External Aggregate.'
-A stitch:node element must be created for each of the nodes associated with the above identified mainBody:link elements
    Note:  only the mainBody:node elements which are part of a connection to an External Aggregate must be included
                in the Stitching Extension.  However, Aggregates may include other mainBody:node elements if they desire.
-The stitch:node elements are populated as follows described below:
   --stitch:node id==mainBody:node component_id
   --stitch:port id==mainBody:link->interface_ref component_id (which equals a node->interface component_id)
   --stitch:link id==stitch:portid with ":some-descriptive-term" appended
   --stitch:remoteLinkId==the stitch:link id from the External Aggregate stitching extension
-both of the peering Aggregates need to point to each other in consistent manner with  their stitch:link and stitch:remoteLinkId elements

The stitching extension Ad has element names something like: <elementName> ValueHere </elementName>

Strip extraneous whitespace from such values.