- Edge point update should be triggered based on TopologyEvent.
{Device, Link}Event can be triggered before TopologyEvent,
which will result in use of the outdated Topology to determine
if the port is an edge port leading to incorrect edge port set.
(ONOS-4896)
- Ports on Edge Link should not be considered part of infrastructure,
should be candidate for Edge point.
Change-Id: I7d69cc242ba7849996c1105ccd1956975db63480
- 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
[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
- Shut down openflow meta app before driver test,
was causing port collision issues with openflow server
- Fixed NPE in Network config store
- reordered tests to insure proper sequencing
Change-Id: Ib39330153f543ee960b8631a0dc9246ee4251851
Log exceptions when trying to access metadata file
Close connections opened when checking file availability
Change-Id: Ibe89e66ba52dba1c47b559bb784fd7376a3319f2
Serialization was failing when the inner ByteBuffer instance was a
HeapByteBuffer. Also, simplified ImmutableByteSequence.toString()
Change-Id: I4f75086a9b6536205fb43b78a0e4d2bfce9e8a5c
Input string from REST should not be converted into byte array directly.
Before: "1" -> ascii 49 -> 0x31
After: "0x01" -> 0x01
GroupKey is a byte array with arbitrary length and represented by hex string
Change-Id: If27101f0e5522212c7e434fab58b66e67e9676d7
