- Make createInitialPhase() static and move it to IntentProcessPhase
- Additionally, rename to newInitialPhase()
- IntentWorker's constructor receives an initial intent process phase
Change-Id: I4774493230a008fc5530d9d90b262e1eb441f946
- IntentWorker is placed in phase package
- Make public IntentProcessPhase subclasses package private now
Change-Id: Ie7d218fe5d8a516f3913ff8881d9d17cfd8e4c46
Made Jono's changes to ECM per Madan's suggesion.
Added cell beast.
Re-enabled anti-entropy.
Added ability to push bits through test proxy for faster upload.
Change-Id: I1455d6d443a697d7a3973c88cb81bfdac0e1dd7f
Create an installable intent, not relying on an IntentCompiler.
This change enables IntentCompilers to be moved to a dedicated package.
Reference: ONOS-1066
Change-Id: Ie5bca33720232afaa4d6642d4f9fda933f6d00e3
The unit tests only depend on PointToPointIntentCompiler and it would be
obstacles when IntentCompiler subclasses are moved to a dedicated package
Change-Id: Ifbfe5ef2a4bae014d2b6cae599fe8860a54e01ca
Reference: ONOS-1066
- Define IntentProcessor interface containing methods to process an intent
- Pull out IntentCompiler related tasks to CompilerRegistry
- Pull out IntentInstaller related tasks to InstallerRegistry
- Create an IntentProcessor subclass as inner class in IntentManager
Change-Id: Ia3e8d574a1053e7ddc9b961873ef758c9e0b1b26
by catching the appropriate exception.
Apparently, if a property is configured/enabled in file Foo.cfg, e.g.:
flowTimeout = 10
then the corresponding object/value in the Dictionary returned by
ComponentContext.getProperties()
has class type String.
However, if the property is commented-out, e.g.:
then the Dictionary still contains an entry for "flowTimeout", but
its class type is Integer.
Also, updated similar code elsewhere that was catching the generic
Exception with catching more specific exception(s).
Change-Id: I33ec348eb9efe3188e22cfc8cee2bb704948726d
In unit tests that are mocking an entire interface, instead
extend the Adapter class so the unused method overrides
are no longer needed.
Change-Id: I6e332cc5cb59410f163deea223fbc94e73d83917
Problem is due to two packet requests from different services
for the same selector resulting in the same flow rule.
Since these rules where the same, only one ended up on the data plane,
but sadly only the first request made it into the flow service meaning
that in cases where what was in the flow service does not match what is
on the dataplane resulting in a PENDING_ADD situation.
Change-Id: I4c03e753be6e198e04f0b5263a2aa8cf2edc51e1
Change-Id: Ib977f4cf9a59ddec360072891fd803c6f9ee84f1
Injecting optical device annotations and ports works for multi-instance (ONOS-870).
Change-Id: Icdde16ef72fc4e47eec7213250b04902083f0537
The APIs are for supporting service data to install on network devices.
This is related to JIRA ticket ID ONOS-869.
Updated API code and added implementation code files.
Modified API for supporting payload abstruction, and added routing mechanism for pushing flow rules to devices.
Added more javadoc, and fixed some minor issues.
Updated javadoc, removed unnecessary method, and test code.
Change-Id: I105defc92a9e01b30601fcb56a9dafa086d4adc0
