-
Type:
Bug
-
Status: Closed (View Workflow)
-
Priority:
Minor
-
Resolution: Done
-
Affects Version/s: None
-
Fix Version/s: 1.4.0
-
Component/s: None
-
Labels:None
-
Epic Link:
-
Sprint:Emu Sprint 2 (10/12-10/30)
Before https://gerrit.onosproject.org/#/c/3054/4 patch, HostToHostIntent implicitly had non-OPTICAL link type constraint.
After the patch, implicit constraint has disappeared, but CLI commands had a logic on it's own to check and add non-OPTICAL link constraint, but the GUI code path didn't.
Since Host ~= MAC/Ethernet Address, it seems to make sense for HostToHostIntent to have implicit non-OPTICAL constraint.
HostToHostIntent.Builder, probably should be modified to check and add the non-OPTICAL constraint, if it hasn't already been specified by builder method.