Introducing Bridge Operational State 67/17967/4
authorEd Warnicke <eaw@cisco.com>
Wed, 8 Apr 2015 18:34:44 +0000 (11:34 -0700)
committerEd Warnicke <eaw@cisco.com>
Thu, 9 Apr 2015 18:51:43 +0000 (11:51 -0700)
commit1e4f7fd184540dedb3420cd3c0bcc231152bb8fb
tree150d7186663cd5582730687666042bb0a14b2b7c
parente02f7027214b32e8a7b56dba2fe2f89ca8a0e0d0
Introducing Bridge Operational State

And using it for Bridge/TerminationPoint Delete Operations

In order to correctly handle 'merge' of data on update
we will need the BridgeOperationalState functionality,
so we can know what we *have* and thus whether to do
an insert/update/mutate.

Change-Id: I9e5200bf1b7f724e346b0855c32f6510773f5e5d
Signed-off-by: Ed Warnicke <eaw@cisco.com>
southbound/southbound-impl/src/main/java/org/opendaylight/ovsdb/southbound/OvsdbDataChangeListener.java
southbound/southbound-impl/src/main/java/org/opendaylight/ovsdb/southbound/ovsdb/transact/BridgeCreateCommand.java
southbound/southbound-impl/src/main/java/org/opendaylight/ovsdb/southbound/ovsdb/transact/BridgeOperationalState.java [new file with mode: 0644]
southbound/southbound-impl/src/main/java/org/opendaylight/ovsdb/southbound/ovsdb/transact/BridgeRemovedCommand.java
southbound/southbound-impl/src/main/java/org/opendaylight/ovsdb/southbound/ovsdb/transact/TerminationPointCreateCommand.java
southbound/southbound-impl/src/main/java/org/opendaylight/ovsdb/southbound/ovsdb/transact/TerminationPointDeleteCommand.java
southbound/southbound-impl/src/main/java/org/opendaylight/ovsdb/southbound/ovsdb/transact/TransactCommandAggregator.java
southbound/southbound-impl/src/main/java/org/opendaylight/ovsdb/southbound/ovsdb/transact/TransactUtils.java