[TOPOPROCES-28] Support for link aggregation is missing Created: 30/Jun/15  Updated: 19/Oct/17  Resolved: 07/Feb/16

Status: Resolved
Project: topoprocessing
Component/s: General
Affects Version/s: unspecified
Fix Version/s: None

Type: Bug
Reporter: Martin Uhlir Assignee: Unassigned
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All

External issue ID: 3901

 Description   

Framework does not support aggregation and filtration of links.

In the first - preparatory - phase, classes and variables need to be renamed and structures prepared to use more general term Item (representing Nodes, Links and Termination Points) instead of current Node.

In the second phase, aggregation of Links has to be implemeted, as well as its translation into datastore nodes structure format and writing into datastore.

 Comments   
Comment by Andrej Záň [ 25/Jan/16 ]

topoprocessing framework currently doesn't consider source and destination node of link during aggregation. Two links <b>should not</b> be aggregated, if they don't have mutual source and destination node.
For example, if target field is set to bandwidth then these two links should not be aggregated:

link1
bandwidth:100
src-node:node1
dst-node:node2

link2
bandwidth:100
src-node:node1
dst-node:node3

but these two should:

link1
bandwidth:100
src-node:node1
dst-node:node2

link3
bandwidth:100
src-node:node1
dst-node:node2

Comment by Andrej Záň [ 02/Feb/16 ]

Link aggregation should be used with conjunction with link computation. In background links aggregation will be processed after link computation and it will aggregate links created by link computation.

Comment by Andrej Záň [ 07/Feb/16 ]

https://git.opendaylight.org/gerrit/#/c/33784/

Generated at Wed Feb 07 20:40:30 UTC 2024 using Jira 8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d.