BUG: Fix missing creation of initial openflow rules upon node creation 14/16514/6
authorFlavio Fernandes <ffernand@redhat.com>
Sat, 14 Mar 2015 11:06:56 +0000 (07:06 -0400)
committerSam Hague <shague@redhat.com>
Mon, 16 Mar 2015 14:14:44 +0000 (14:14 +0000)
commit549c467cacfdf19ac7a2e6bc5325e219ae5628ce
tree7f3adac52387ee7dfeb539ad5db29ab56da9b508
parent911d1cac0b6390c7937549d4b79f66b825346075
BUG: Fix missing creation of initial openflow rules upon node creation

While using the registerDataChangeListener for createFlowCapableNodePath, we began to
see cases where onDataChanged provided no entries in getCreatedData() when it should.
To deal with that, the code will now pay attention to updates in getUpdatedData() and
treat it as create if this is the first time the listener hears about the nodeId.

Patch 2:
  - listen to operational instead of configuration mdsal tree;
  - check for create/update inside change loop
  - remove redundant [removed/added] words in log
Patch 3:
  - fix notifyNodeUpdated log
Patch 4:
  - change log level for notifyNodeUpdated
Patch 5:
  - undo patch 4. Lots of logs [1]

[1]: https://gist.github.com/67daada34dd91aff3190

Change-Id: Id1b445ec4892f9c8848b6ca5a6739948d87432c9
Signed-off-by: Flavio Fernandes <ffernand@redhat.com>
openstack/net-virt-providers/src/main/java/org/opendaylight/ovsdb/openstack/netvirt/providers/openflow13/FlowCapableNodeDataChangeListener.java