- It was creating 2 theads everytime a Device connected.
Now uses thread pool shared across Devices, where threads will die out on idle.
Should resolve ONOS-3579
Change-Id: I490b2ef677853677fbd151af27f6ac2be563774c
- net and cli bundle has dependency to optical-model bundle,
which should be removed in the longer run. (ONOS-4626)
Change-Id: Ieff43ef2002ee21f4578a6e2a729cd35ce3eae3d
Changes:
- Improves processSpecific in AbstractCorsaPipeline in order to support
Intents without an explicit match on the Ethertype;
- Implements vlan based circuits in CorsaPipelineV3 through the management
of the FwdObjective without Treatment;
- Distinguish Groups from simple actions;
- Corsa group are identified using the actions of the treatment;
- handling of the pending next similar to DefaultSingleTablePipeline
Change-Id: Iff0f70d56c64193524c6640f31ffb3f5629499dc
- Add alart command for FUJITSU OLT
volt-notification-alertfilter <netconf:target>
volt-notification-setalertfilter <netconf:target> <alert-severity>
volt-notification-subscribe <netconf:target> {disable}
- Update fujitsu-drivers.xml and shell-config.xml in FUJITSU directory
- Apply Yuta's and Andrea's suggestion to startSubscription method and other methods which related to startSubscription method.
-> Remove startSubscriptionConnection() and createSubscriptionString() method in 4th patch-set.
-> Modify cosmetic issue related to Static-string.
-> Update "No replay" to "No reply" in VoltGetPonLinksCommand.java
Change-Id: I2c8d5484ea0ff9f0b1b970fe8b183bec12193c46
- Reverting iteration through meta instructions to earlier mode
Assuming instructions appear in the order they were added
- Saving explicitly provided VlanId to new variable modifiedVlan:
modifiedVlan is the value to be used when modifying existing tag
assignedVlan is the value to be pushed to untagged packets
pushedVlan is the value to be pushed to tagged packets (i.e. when pushVlan == true)
- Extra checks added for the following cases:
Do not allow to pop tag after modifying existing tag
Do not allow to modify a tag after pushing a new tag
Do not allow including multiple modify VLAN operations
Change-Id: I92801e3845a2ca1e88181698cb0ba3c22224acf4
Arista switch with its recent network OS, EOS, supports remote configuration & control. The protocol for this is Arista's proprietary but REST style.
Since ONOS has already REST southbound protocol, the control of Arista switch can be easily done by using this.
- Implemnted driver Loader for Arista switch
- Implemented DeviceDescriptionDiscovery for Arista switch
- [Deleted] Implemented the method sending post to Arista switch and return the result as a String
Change-Id: I9d4b8f0d707361949ff530ff414adb0437ae87d9
- Add the following commands for FJ OLT
volt-onus <netconf:target> <ONU ID>
volt-setonu <netconf:target> <ONU-ID:parameter type:parameter value>
volt-onustats <netconf:target> {ONU-ID}
volt-rebootonu <netconf:target> <ONU-ID>
volt-ethloopback <netconf:target> <ONU-ETH-ID[:loopback mode]>
- Add the method of doUserRpc() in Netconfsession/NetconfSessionImpl
*If you dont allow to implement the method, i can move it to our XmlUtility method.
- Add new behaviours in /core/.../net/behaviour, and @Beta in the interface.
- Move those behaviour interface to fujitsu driver directory.
* VoltPonLinkConfig.java as well.
- Update fujitsu-drivers.xml
- Change the method name from doUserRpc to doWrappedRpc
Change-Id: Ic39d3a11ba35d2377e552af097eda65c5554c63f
Adding ability to version extraneous stuff.
Change-Id: I2e18dafd6d8705504ab01000d6707037415dfd0c
(cherry picked from commit 251016df5db8f11a14c4856f9b381e85ae1e2631)
[Done]
- Add vOLT ponlink commands for FUJITSU OLT
- Add new implementation with respect to the commands
- Move those commands to Fujitsu drivers directory
- Modify BUCK to avoid an error
Change-Id: I7a61234e18367aa74445800dd09f98c10edc35c4
- Added tunnel interface configuratoin to interfaceConfig and
deprecated tunnelConfig
- OVSDB client service provides interface create/remove APIs instead
of tunnel interface create/remove, and this APIs can be used to
create/remove various types of interfaces like tunnel, patch, tap and so on
- Use tunnel description when create tunnel interface so that we can extend
more config options later
- Some cleaup OVSDB client
Change-Id: I4653595504a27b18384a92ebe4b31ce9d99237cd
Similarly to ONOS-4206, due to a bug in kryo, a non-registered class
(Date in this case) was causing such a problem.
Change-Id: I993f4b41d4deaa617065b29086a49d834832eca8
treatments.
Match and action parameters can now be built from primitive data types
(short, int, long or byte[]) which are then casted automatically
according to a given BMv2 configuration. Also, simplified demo
applications code / structure.
Change-Id: Ia5bebf62301c73c0b20cf6a4ddfb74165889106f
OVSDB provides lots of bridge configuration options but the exisisting
bridge config implementation only allows some of them by overloading
addBridge method. Also some of the bridge properties were set static
and unable to configure. This patch fixes these limitations.
- Added some bridge config options to the bridge description
- Deprecated multiple overloaded addBridge methods
- Some code clean up
Change-Id: Ibc828177b210bd4b215aea0b63cc359776c13e03
