Opened 10 years ago

Closed 10 years ago

#36 closed (duplicate)

RSpecs: Rack Ads including proper stitching extension

Reported by: ahelsing@bbn.com Owned by: ibaldin@renci.org
Priority: major Milestone:
Component: AM Version: SPIRAL4
Keywords: Cc:
Dependencies:

Description

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

Change History (2)

comment:1 Changed 10 years ago by ibaldin@renci.org

Owner: changed from somebody to ibaldin@renci.org
Status: newassigned

comment:2 Changed 10 years ago by ibaldin@renci.org

Resolution: duplicate
Status: assignedclosed

Same as #37. Nothing different in behavior of rack SM vs. ExoSM with respect to these comments.

Note: See TracTickets for help on using tickets.