Bug:645 - MDSAL Notification pool threads not getting spawned besides the core threads

Change-Id: I6851f9b90b500b2b10a135bcda784a11c8f44786
Signed-off-by: Kamal Rameshan <kramesha@cisco.com>
Bug:701-Have Typed ErrorNotification for different node errors

Change-Id: I674203531d0205dd13b47b64616624b5193bcb4d
Signed-off-by: Kamal Rameshan <kramesha@cisco.com>
Resolve Bug:748 - Remove test resources from netconf-impl.

Remove old testing resources that are not required in tests.

Change-Id: Idba3be129aa177fa2eb362032719c79fb30331ba
Signed-off-by: Tomas Olvecky <tolvecky@cisco.com>
Bug 781: Statistics manager is throwing IllegalStateException

Change-Id: I418bd4b86bbe9802be3ec7ed904a14ce537f085e
Signed-off-by: Anil Vishnoi <avishnoi@in.ibm.com>
Resolve Bug:681 - Fix config module registration to Service Registry.

Rework OSGi service registration during second phase commit: only service references
will be registered into SR, instead of old behaviour when each module's service
interfaces were used. Only one key-value entry is persisted in registration:
{name: name of service reference} .

Change-Id: I25249fe8f9e51570cd3ea963e91145b7e44da57d
Signed-off-by: Tomas Olvecky <tolvecky@cisco.com>
BUG-732 Add rollback-on-error error-option to edit-config rpcs from netconf-connector

Just in case rollback-on-error capability is supported

+ Add error response warning to netconf-connector

Change-Id: I16251a12b270bd0ed89b39bfccc5251b4b3fe934
Signed-off-by: Maros Marsalek <mmarsale@cisco.com>
Resolve Bug:807 - Keep ModuleFactory references shutdown purposes.

Retain ModuleFactory instances even if they disappear from OSGi SR,
so that the already committed instances can be closed cleanly. Also
remove shutdown customization (stopping config-manager as first bundle)
from shutdown-impl.

Change-Id: I8e90a7d593b7e4cc84c7a9a7d3f8bb804daf5f41
Signed-off-by: Tomas Olvecky <tolvecky@cisco.com>
Merge changes I67420353,I6851f9b9

* changes:
  Bug:701-Have Typed ErrorNotification for different node errors
  Bug:645 - MDSAL Notification pool threads not getting spawned besides the core threads
Merge "Bug 781: Statistics manager is throwing IllegalStateException"
Fixed typo in test name. Temporary ignore test.

Change-Id: Icdae59971bded5e76a181d4ab63132e011a561ca
Signed-off-by: Martin Vitez <mvitez@cisco.com>
Bug 722 - nagasena version bumped to 0000.0002.0038

Change-Id: Ie755a9a613096aed6f134005d216716c59b90563
Signed-off-by: Martin Bobak <mbobak@cisco.com>
Bug 509: Added support for merge operation to InMemoryData Store

Merge operation support is critical for backwards compatibility
and for Binding-Aware mapping and Restconf, which are not aware
of Mixin nodes representing lists, leaflists and choices.

Semantics of merge operation are similar to subtree modified,
but when node is not existing it creates one based on
state provided by user of the Data Broker APIs.

Merge operation also fixes concurrent creations of mixin nodes
as demonstrated in ConcurrentImplicitCreateTest,
where two separate applications may indirectly create same
root node.

Change-Id: I9ab290b512601bd99750a68ee53564e67ef0c879
Signed-off-by: Tony Tkacik <ttkacik@cisco.com>
BUG 652 leafref CCE & BUG 720 colons problem

BUG 652 leafref Class cast exception
By default if input data were in format which was possible to parse as
XPath if was done like this. It caused that for leafref which indexed to
instance-identifier the value was parsed as XPath and not as string.

BUG 720 colons problem in JSON
If input string contained colon (:) then it was dealed as namespace:value
and object of type IdentityValuesDTO was created (it is probable that
data could be of type identityref). If data wasn't of type leafref then it
was incorrectly processed as leafref.
The RestCodec was updated to correctly translate data (cases when data
contains ':' but aren't of type leafref)

Change-Id: I0cba06bce1b1c69f6901cc90d2b30a3735e5f57e
Signed-off-by: Jozef Gloncak <jgloncak@cisco.com>
Bug-590: Packet loss on first time ping test

In this commit, we are addressing a race that could cause the exception (ie first ip packet) to
be lost. What is observed with this bug is that the non-arp packet -- in this case the icmp packet --
is being 'exceptioned' to the SimpleForwarding code path because the node has not yet been programmed
with flows that would allow it to forward the packet to its destination w/out involving the controller.

The race in this case is caused by the exceptioned packet being received before the rulesDB member
in simpleForwarding module is updated. That member -- rulesDB -- is updated via the
hostTracker::notifyHTClient() callback shortly after. In this particular race, the hostTracker is already
updated with the proper information, and rulesDB is 'stale'. Thus, the proposed fix is to make the forwarding
less strict (ie. ignore rulesDB). Note that both routing and hostTracker are all simpleForwarding needs to
know how to forward the packet.

Change-Id: Icfb909ca89abff6031212b4fcd0f5d1bd1a27d6b
Signed-off-by: Flavio Fernandes <ffernand@redhat.com>
Merge "Bug 509: Added support for merge operation to InMemoryData Store"
BUG-832 Add initial configuration for controller self mount

Netconf server for config subsystem is mounted to restconf under id "controller-config" by default

This illustrates the usage of sal-netconf-connector

Change-Id: I3f324b41995dc094bac0d316788dfdb05e18ef60
Signed-off-by: Maros Marsalek <mmarsale@cisco.com>
Merge "Bug-590: Packet loss on first time ping test"
Bug 451 - Fix netconf exception handling

Change-Id: I815b34da996cf2660650577edb2e8ca623ae96df
Signed-off-by: Martin Bobak <mbobak@cisco.com>
Merge "BUG-832 Add initial configuration for controller self mount"
Merge "Bug 451 - Fix netconf exception handling"