tree 853a4793b252760b884dc9bbb4c8779a4194de0f
parent a899a2127ba8bfa7b7973813fa8beb6870fab151
author Yuta HIGUCHI <y-higuchi@ak.jp.nec.com> 1486094006 -0800
committer Thomas Vachuska <tom@onlab.us> 1488397446 +0000

Some class of constraints should not be used for link cost evaluation.

ONOS-6021

Current ConnectivityIntentCompiler simply picks first non-negative cost as Link cost value.

Some class of constraints are used to express Path viability or IntentCompiler's behavior.
Those constraints tend to returns fixed arbitrary non-negative link cost, which probably is not the best option to be used as Link cost during path computation.

This patch will:
- Introduce base class for constraints which should not influence Link cost.
- Introduce base class for constraints which should not influence Link cost or Path viability.
- Exclude above classes from link cost computation in ConnectivityIntentCompiler

MarkerConstraint
 base class for Constraints,
 which is not meant to influence Link cost or Path viability.

PathViablityConstraint
 base class for Constraints,
 which is not meant to influence Link cost.

Change-Id: Ice8b83a18cfe3bf5a68c25a853667bfaedb2b1a1