Opened 12 years ago
Last modified 12 years ago
#38 assigned
RSpecs: Rack Ads include external references
Reported by: | ahelsing@bbn.com | Owned by: | ibaldin@renci.org |
---|---|---|---|
Priority: | minor | Milestone: | |
Component: | AM | Version: | SPIRAL4 |
Keywords: | Cc: | ||
Dependencies: |
Description
Individual rack (not ExoSM) advertisement RSpecs should include external references - show links to non-local resources (whether they are Orca controlled or not). EG to the mesoscale, NLR, Internet2, etc.
These connections should follow the stitching guidelines:
-there must be a link element for each connection to an External Aggregate. -these link elements will each have two interface_ref component_id -one of the interface_ref component_id references a local node->interface component_id -the other interface_ref component_id is equal to a link--->interface_ref component_id in a link element of the External Aggregate -both of the peering Aggregates need to point to each other in consistent manner within their mainBody:link elements
Note the relation to ticket #36
Change History (4)
comment:1 Changed 12 years ago by
Owner: | changed from somebody to ibaldin@renci.org |
---|---|
Status: | new → assigned |
comment:2 Changed 12 years ago by
comment:3 Changed 12 years ago by
There are still a log of component+unknown entries in the ExoSM Ad RSpec.
comment:4 Changed 12 years ago by
Priority: | major → minor |
---|
Note: See
TracTickets for help on using
tickets.
I now see that all the nodes have 1+ interfaces, and there is 1 link per such interface. And those links include 2 interface_ref elements. Good so far.
However, many of those references are to
urn:publicid:IDN+exogeni.net+component+unknown
Clearly that needs work.
I haven't investigated whether all the logical external connections are represented.