We provide an interface for assigning weights to buckets
in a group and thus we should not silently ignore it.
Properly set bucket weight to bucket.weight().
Change-Id: I7dce89e793140ee365a016f4bf26f0ccf206b8dd
- Using osgi_jar for all modules except apps
- Adding target for installation of core modules to .m2 repo
Change-Id: I65d9e3a9567918e275191724842d7d9b1f485128
- NPE when a switch has already been removed and an attempt is made
to access stats on the switch.
- NPE in group provider if the system is in the process of shutting down.
- Lower ERROR to WARN when switch resources are not available.
Change-Id: I5b90ff328b19c2d661fde3a24e90614999c4c900
Removing dependence on hashing for unique groupkeys in ofdpa driver.
Group-store no longer removes groups from store if a group-operation fails due to GROUP_EXISTS.
Group-store also checks for unique group-id when given by app.
Group-provider now logs warning before making call to core.
Change-Id: I4a1dcb887cb74cd6e245df0c82c90a50d8f3898a
Edge case fix in group store where extraneous group buckets are updated so the group can be reused
Bug fix for broadcast group in OF-DPA as there can only be one l2flood group per vlan
Group operation failure codes are now reported by the provider to the core
Group ids are displayed in hex in a couple of places
Change-Id: Ib48d21aa96e0400b77999a1b45839c28f678e524
Control message monitoring brings some overhead to controller.
In an extreme stressing environment (e.g., running Cbench),
it leads potential performance degradation.
This commit tries to mitigate the Cbench regression with two steps:
1. improve the monitoring performance by assigning more # of
threads in each thread group.
2. make the control message listening feature optional.
Change-Id: I4f7361b7c598c6de71d390eab78a20ada381d4dd
- Forwarding behavior added to {Device,Link}Store by ONOS-490
cauesed false update information sent from ONOS node, which has been detached from the cluster,
to be accepted by rest of the cluster after the detached node has rejoined cluster.
- Fix for periodic mastership check was left out
when MastershipService#requestRoleFor(..) return value was changed to Future.
- Fix for triggerProbe() related messages getting dropped,
right after STANDBY -> MASTER role change.
- Local state (connectedDevices) was preventing
vertical (Core -> switch) Mastership state synchronization.
- Various debug log, comment added during investigation.
Change-Id: I777beadf04db8a879830a07bfdc7ab0e2279f190
