Bug 963 - OSGi error in Topology manager component - After exiting
mininet of13 simulation

* added check in onLinkRemoved() to check if link exists before
atempting to delete it (without check, lots of datastore transaction
errors were displayed on mininet shutdown because links were already
removed with nodes)
* added checks to check if node, connector or link exists before trying
to remove it (reads are cheap and delete exception can break the
transaction chain)
* made reads synchronous
* added illegalState exception handling to operation processor
* made affected links removal to be in the same transaction as
Node/NodeConnector removal(creating and applying snapshot for each link
is expensive)
* updated tests

Change-Id: Icef03a02bbfb88a7cebd0fe35e4b713dcfeb317c
Signed-off-by: Jan Hajnar <jhajnar@cisco.com>
Bug 1309 - Cannot publish LinkDiscovered event

* added back MD_SAL_TYPE for nodeConnectorId and nodeId for case when
nodeId and NodeConnectorId are not in openflow format (NodeId and
NodeConnector Ids are strings)
* added test that shows

Change-Id: I73438a14b0b32a9fd3b0bc311663ad29b7bd7dd1
Signed-off-by: Jan Hajnar <jhajnar@cisco.com>
Bug 1025: Fixed incorrect revision in sal-remote-augment, which caused log polution.

Change-Id: I5db5bfb43217d21bad58c913de8dedac5d7cdf23
Signed-off-by: Tony Tkacik <ttkacik@cisco.com>
Merge "Bug 963 - OSGi error in Topology manager component - After exiting mininet of13 simulation"
Merge "Bug 1309 - Cannot publish LinkDiscovered event"
Merge "Bug 1025: Fixed incorrect revision in sal-remote-augment, which caused log polution."