LinkCollectionObjectiveCompiler should generate filtering objective
according to different situation.
This implementation use criterion from in/egress FilteredConnectedPoint and encapsulation tag for the
filtering objective.
Change-Id: Ib2ccd6fb00d055a96f2762ce261780ebc544a77b
Lables for encapsulation won't release because Intent manager release the
resources by Intent key only.
Allocate encapsulation labels by using Intent key instead of Intent Id to
resolve this problem.
Change-Id: I8fd52245063ded725e4b2c3911f52c029591ab90
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
- (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)
If an application want to create custom Intent installer, it might need
ObjectiveTrackerService.
However, the ObjectiveTrackerService is not public api (in /core/net,
should be /core/api); so application outside the ONOS can't use it.
Move ObjectiveTrackerService and it's dependence to /code/api
Change-Id: Ie2ad8dd9d39ccae1c91f4b57887089e0aec83ede
Next-objectives that edited groups are now queued in the FlowObjectiveManager instead of the driver.
During linkup immediately checking for previous portups that should be added to a hash group.
A final retry 30 secs later to catch all ports that should be part of the same hash group.
Change-Id: I7ef450149d685890ca47932b8e559a0c11dc5ab4
Avoid same IntentData resubmitted by multiple ONOS nodes.
Also, avoid same IntentData/IntentOperationContext modified by different
threds.
Change-Id: Ifb550c41204d6e86e379fd44c2787980920d2b9e
Introduced the DomainConstraint which marks intents that allow domains.
Added the handling of domains to the base compiler and its implementations.
Fixed existing test by adding the domain service and added new ones for domains.
Change-Id: I6594e92e41c2434a9b667415e6fb90a6c571df79
- addConfig will create and 'advertise' a new default Config object.
In the case of BasicLinkConfig, default link type will be DIRECT.
Link subsystem ignores link transition from DIRECT to INDIRECT
in order to prefer LLDP info over BDDP info.
As a result it is difficult to create an INDIRECT link
via Java API calls.
Change-Id: Id736f3a8332b7558387c3eb7598e1239779c6fe8
- Allocate resources by Intent.Key instead of IntentId
- ONOS-5808 changed the IntentManager's Intent withdrawal behavior to
release resouces allocated by Intent.Key
(was releasing resource allocated by IntentId)
Change-Id: I62e048e4ee8f841b92d9985784c95abba3d37a0a
- Reduce logging for
- Packet rule installation failure for NETCONF packet switch
- NETCONF device which does not support port stats
Change-Id: I4721f65088f34d3e473f22738f27e093fe8df270
