Anil noticed there was a race condition here where we might write
authorEd Warnicke <hagbard@gmail.com>
Tue, 12 May 2015 22:27:11 +0000 (15:27 -0700)
committerEd Warnicke <hagbard@gmail.com>
Tue, 12 May 2015 23:35:09 +0000 (23:35 +0000)
commitbaa85cd9345b9c602286a9f7c072cfa743025338
tree4aad05f489d831aef1c9e0453a93145755b3f9a3
parent4dea4b9de2554b25590ced0355dbf6131c60735e
Anil noticed there was a race condition here where we might write
an ovsdb-node to the operatational store before recording the
TransactInvoker we needed for people to be able to use it to write to
ovsdb.  This fixes that by imposing the order:

1)  Record the TransactInvoke for the ovsdb-node (internally)
2)  Write the ovsdb-node to OPER
3)  Register callbacks for monitors from ovsdb

Change-Id: I55202678521065b1a8c2f018a9f229b6be263a48
Signed-off-by: Ed Warnicke <hagbard@gmail.com>