Fixing the ordering of flow programming operations
* When the subscriber is provisioned, it seems the related flows are being sent
in proper order. However, Voltha receives these in the wrong order. In order to
solve this problem, Charles' suggestion is implemented.
* New property named enableEapol is added, the default is true - it can be
changed to false from ONOS CLI, when it is false, OLT app does not send EAPOL
trap flows.
* Meter-mod & Flow-mod ordering issue is solved
* Multiple OLT support is added (internal maps are updated)
* New cli commands to debug bandwidthProfile and meter relations
Change-Id: Ic0a15aafa5403e00106dc660061e2a0b46ba5b01
diff --git a/pom.xml b/pom.xml
index 2c6270d..d0574ec 100644
--- a/pom.xml
+++ b/pom.xml
@@ -22,7 +22,7 @@
<parent>
<groupId>org.onosproject</groupId>
<artifactId>onos-dependencies</artifactId>
- <version>1.13.9-rc1</version>
+ <version>1.13.9-rc2</version>
<relativePath></relativePath>
</parent>
@@ -33,7 +33,7 @@
<properties>
<project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
- <onos.version>1.13.9-rc1</onos.version>
+ <onos.version>1.13.9-rc2</onos.version>
</properties>
<modules>