- 25 Feb, 2016 19 commits
-
-
In order to avoid nextId collisions, all users of the flow objective service should use the provided allocateNextId() method when constructing new NextObjectives. I found one instance where this was not the case: CordMcast. Solution: removed private id generator from CordMacst and replaced it with allocateNextId. Change-Id: I134931b58c524291ae937dd6f0051ee549236734
Zsolt Haraszti authored -
- Using @Property and @Modified annotations - Fix DistributedPacketStore / DistributedStatisticStore / DistributedFlowStatisticStore Change-Id: I6c907498496b9f21a8ef13b7badeb24770cb88ff
sangyun-han authored -
It is impossible to use openstack4j directly from ONOS apps due to the Jersey version conflict. Change-Id: I2df32430de42d627b03e0a2f8d8d2b9067ad3e14
Hyunsun Moon authored -
Problem: The decoder in GroupCodec (used by the REST layer) chopped the upper 16 bit in caller-provided group IDs. Since group IDs are inherently greater than 16-bit on any OFDPA-based device, the current casting rendered the REST layer unusable for such devices. Fix: removed casting, verified that all tests pass, and verified that I can now create healthy group entries on OFDPA-based switches. Change-Id: Ieb51071ff9b0d47f4ff1f90d80970b6c0df946b7
Zsolt Haraszti authored -
- Impelent Region management REST API - Add unit test for Region management REST API - Add swagger docs for Region management REST API - Add SCR Component and Service annotation for RegionManager Change-Id: I042e92ed7144d596659b779a59239afba832ca62
Jian Li authored
- 24 Feb, 2016 21 commits
-
-
This patch resolves ONOS-4032 Change-Id: I12e2ed7d352928fe94559ab978f5db7e9f56f1b0
Sho SHIMIZU authored -
This is a quick fix for ONOS-3923, not a long-term solution. Change-Id: I56e8af57de37e6db1f5e2355d5bb60372adc83f6
Sho SHIMIZU authored
