1. Consider that the type "Duration" in the String is composed by
characters and numbers, it's not easy to convert it to double for
comparison, I modified the latency's annotation to
cfg.latency().toNanos().
2. Exclude two EdgeLinks for the calculation of the whole path's latency
3. The unit of latency in ONOS is not the same, so I set all the latency units to
nanoseconds.
4. Add the latency constraint option for ConnectivityIntentCommand.
Change-Id: Iddf5634880e43ed563db9978659db5eb9ee6c7f8
- Fix for a bug where intent compilation complete state,
can overwrites intent installation complete state,
if intent installation completes before compilation complete state is written to the store.
- Introduced internalState version on IntentData,
which is effectively mutation count, in order to avoid
batch write of compilation result overwriting installation result
Change-Id: I5d77dfbe496e690ebdf2b4f9643d2b64c4233182
Defines the interface for mastership service for virtual networks.
This service is needed to achieve HA and load balancing.
Change-Id: I5b68511c114ebd818429f4f6eb622dff95dd8630
1.Fix the bug of Treating path index as port number for APS;
2.Creating APS switching operations dynamically, instead of hard code;
3.Change APS interface for general using;
4.Compatible test base on the devices of OPENFLOW and NETCONF protocol.
Change-Id: Ib750d40ed28fc184a96b58e97715beab3d80ff17
- (part one)
- Enhanced HostManager to react to NetworkConfigEvents such that
it applies annotations to relevant host instances from the
config data.
- A little refactoring in DeviceManager.
- Updated topoModel.js to use updated field names latOrY/longOrX.
Change-Id: I06536a6b2279291ffe638549a80b56a9fe94f48a
(cherry picked from commit 78193fd06661a7fa524c8b3a8fa7ddb69d7437c9)
- check made for returned backing host being null.
Change-Id: Ib7df17c45d4b39a85662ec5e37dab4821da8225d
(cherry picked from commit 0a9b5a1c1d4f21a4426b1d2e62d1e951a38c2c04)
Reasons makes Intent stuck in WITHDRAWING state:
1. The patch for CORD-1180 caused next objective queued in the objective
system if there is no next group for that next objective.
2. Default single table pipeline removes next group from flow objective
store when removing forwarding objective.
3. The flow objective Intent installer will remove forwarding objective
first, then remove next objective.
4. The flow objective Intent install will wait until all objective context
completed, however, according to reason 1, 2 and 3, the next objective
will be queued forever since there will be no next group in the store. So
the Intent state will stuck in WITHDRAWING until the Intent manager retry.
To fix this issue, we need to modify default single table pipeline, make it
not remove next group when removing forwarding objective.
Change-Id: Ia51a3361f19b60332ca1a276583cdfc036d93343
- It took 25 secs and now it taks only 200 ms.
- It is a temporary fix. It will be removed when OVS-SNAT features is merged.
Change-Id: If98ba8f4f59ca90b3300c64ea0da92c9558c4303
1. Uses NETCONF get operation instead of get-config.
2. Prevents reply-error log flooding in netconf session when polling port power range with protection switch, which does not support power range configuration retrieving.
3. Some code optimization.
Change-Id: I5c4d0b0f6681dd1bf6b8c7450daf07db0104a758
