Custom Query (138 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (25 - 27 of 138)

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19
Ticket Resolution Summary Owner Reporter
#26 duplicate Ad RSpec: Include external references ibaldin@renci.org ahelsing@bbn.com
Description

The Ad RSpec should include all external touchpoints: places where ExoGENI resources connect to I2, NLR, Starlight, or other networks, and through which an Experimenter might stitch other GENI resources to ExoGENI resources.

#27 fixed Ad RSpec: follow node/link/interface ID conventions ibaldin@renci.org ahelsing@bbn.com
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?
#28 fixed configure an always-on IP address for testing VLAN 1750 connectivity to the BBN ExoGENI rack somebody chaos@bbn.com
Description

Configure an IP address which can be used for testing connectivity to the BBN ExoGENI rack on shared OpenFlow-controlled VLAN 1750.

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19
Note: See TracQuery for help on using queries.