id summary reporter owner description status priority milestone component version resolution keywords cc dependencies 25 Ad Rspec: stitching extension issues ahelsing@bbn.com ibaldin@renci.org "There are a few issues with the stitching extension as implemented. See email from Tom Lehman with details. - Only include the stitching element once - Only include 1 aggregate in that extension - Ensure consistent node/port/link IDs and references to nodes and links in the main body - If you don't support scheduling, say scheduled=false in the stitching extension - trim excess whitespace Tom Lehman's comments on making IDs match: {{{ i) Main Body of Advertisement RSpec Link Element Population (for links which connect to External Aggregates): -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 ii) Stitching Extension Element Population: -There will be one Stitching Extension with a single aggregate element per Aggregate -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 }}} " closed minor AM SPIRAL4 duplicate #36, #37, #38, #39, #40, #45