The Link Discovery of the Juniper driver leverages on some parameters
that has been changed in ONOS-6323
Change-Id: I6519ba1676de531a74340eaaddc8cc47912bb417
- use snmp-index as port number, which seems to be unique.
duplicates were observed for local-index
- physical-interface Port's enabled state is admin-status & oper-status (was only admin-status)
- logical-interface Port's enabled state is above & if-config-flags.contains(iff-up)
Note: local loopback also falls into this category
- logical-interface Port's portSpeed is inherited from parent physical interface speed.
Change-Id: Ie70d07589db01f6b394c90cb1e599b5eb2f8ec91
There are 2 maps to store groupstores, keep both in sync from the start.
It can happen that the deviceid-based map isn't properly initialized
when the store gets data from other peers in a cluster in activate()
Change-Id: Ia33929f734a846c72890cf57095ea9ff8d2d394c
- (Still WIP)
- Cleaned up createHandlersAndOverlays() in UiWebSocket.
- Augmented handlerCrossConnects to link Topo2MH to Topo2TrafficMH.
- Topo2Stop event now shuts down background traffic monitoring.
Change-Id: I87e7151ea813b7514521201ecffcf2c9eed22cd7
Even if caller has checked that isTimestampAvailable() returns true,
it was possible for consecutive getTimestamp() call to throw an Exception.
e.g., another thread could have released mastership for the Device, etc.
This patch will make getTimestamp() exception-safe to call,
after confirming isTimestampAvailable() returned true,
by keeping history of last known term number of this Device.
- for ONOS-6210
Change-Id: I79e19d5f8eb95bf0b5796f87aacd5df5edd39e39
- 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
We had this limit before because we derived VLAN from subnet.
We no longer do that and thus user should be free to config 0+ IPv4/IPv6 addresses
Change-Id: I144c618112e4b437ebf64ea3b5ab05a83263cb17
Create package "ofdpa" under pipeline package
Move helper functions and classes to OfdpaGroupHandlerUtility
Change-Id: I47e42f2c8afc9088ed684cd6a087233a82c452f6
- (Still WIP)
- refactored trafficSummary() and related methods up into superclass
- introduced hook method for link aggregation
Change-Id: I0a993bbc5ba5f0e861214f8d06877dad3f7bc8ee
- build and package the checkstyle rules in the onos-build-conf artifact
- modify maven build to use new version of artifact
- fix checkstyle problems in maven-only code
Change-Id: I4e4dc890ca909e47463629c732a2fc5335bb4d2a
- wiring in Traffic2Monitor calls
- added utility script to dynamically set debug level on Topo2 classes
Change-Id: Ie727de39739729e1c240ca0484ed08f020546dae
The current version of flow rule provider always returned success
regradless of physical flow rule's installation.
This commit makes to enable to sync with virtual and physical rule
batch operation
Change-Id: I1c9bfc30d23e0e7b24bf8be8774f67e304f3b28e
1. fixed to remove virtual flow rules
2. fixed to remove the installed rules after deactivation
3. minor refactoring
Change-Id: I3685d89840eeef8dbbf53f7afe819f39043b434f
1. Change inputPowerRange to powerRange in the port view page.
2. Replace the update Frequency methods in roadmUtil.
Change-Id: I19a840156d8cdcb9c142bd88a6b5a667bb135f77
