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
This has the effect of limiting the caller so that it can't overrun the single thread that previously did the job.
If you let this back up, it will use all of your memory. :(
Change-Id: I0a3b93cfa7004e0430d228a68c60e2b7ba966d4e
and IPv4.getEcn() / IPv4.setEcn().
Those can be used to get/set the DSCP and ECN bits in the IPv4 header
without explicit bit manipulation at the caller.
Change-Id: Ia7c5779abae5c4fc7a343e3f7ef3355eb7e86e3d
Additional configuration parameters that can be configured in the configuration file (org.onosproject.fwd.ReactiveForwarding.cfg),
that determine application behavior:
- packetOutOfppTable - application will use OFPP_TABLE port in PacketOut message, sending packet back to the OpenFlow pipeline, instead of using switch port
- flowTimeout - configuring reactively installed flow timeout
- flowPriority - configuring reactively installed flow priority
- matchDstMacOnly - reactively installed flows will match only destination MAC address - behavior as legacy L2 switches. This options overrides all other options below.
- matchVlanId - reactively installed flows will match default condition with additionally with VLAN ID field
- matchIpv4Address - reactively installed flows will match default conditions, plus IPv4 address and Protocol field
- matchIpv4Dscp - reactively installed flows will match default condition, IPv4 + with IPv4 DSCP and ECN fields (need matchIPv4Address enabled)
- matchIpv6Address - reactively installed flows will match default condition with IPv6 address and NextHeader field
- matchIpv6FlowLabel - reactively installed flows will match default condition with IPv6 address and IPv6 Flow Label (need matchIPv6Address enabled)
- matchTcpUdpPorts - reactively installed flows will match default condition with IPv4 or IPv6 address and TCP/UDP ports (need matchIPv4Address or matchIPv6Address enabled)
- matchIcmpFields - reactively installed flows will match default condition with IPv4 or IPv6 address and ICMP type and code fields (need matchIPv4Address or matchIPv6Address enabled)
Change-Id: Ieef67a1a12f6341d4de3b07e1226affec66d361a
allow more LinkDescriptions to be generated.
- patch 3/4: Some cleanup/sanity checks added.
Reference: ONOS-1033
Change-Id: I0b35585d5fdec3f7e6c921172f39f67dd6723dec
* adding total to log
* using local devices and keys
* added delay between cycles
* print time if cycle is delayed
Change-Id: I16a3c041dd2e920695ab782d22fe6db8abad7da8
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
