Ah, in that case sysrepo is not relevant because it can communicate only locally on a single machine. What you need to use are YANG/NETCONF mechanisms, YANG Push based on the description, specifically. Look at the RFC and the YANG module, it is fully supported by netopeer2.

Hi Michal,
thank you, this is what we are trying to do so,
but we wanted to understand the flow for establish-sub (netopeer2-cli , only to understand logical flow ), we have loaded an example module in server, and trying to establish a subscription for a xpath in this node, but i think we are fundamentally doing something wrong,

can you please help?
OnCli, we do following

connect
get --filter-xpath=/example-multicontainer:*
DATA

establish-sub --stream new1 --filter-xpath /example-multicontainer:system-info
nc ERROR: SSH channel poll error (Socket error: disconnected).
cli_send_recv: Failed to receive a reply.

On server, we see abort,
[INF]: SR: EV ORIGIN: "/ietf-subscribed-notifications:establish-subscription" "rpc" ID 1 priority 0 for 1 subscribers published.
[INF]: SR: EV LISTEN: "/ietf-subscribed-notifications:establish-subscription" "rpc" ID 1 priority 0 processing (remaining 1 subscribers).
[ERR]: SR: Failed to collect modules to subscribe to (Item not found).
netopeer2-server: /root/new/sysrepo-2.10.1/src/utils/sn_common.c:851: srsn_sub_free: Assertion `i < snstate.count' failed.
Aborted

yang model:

module example-multicontainer {
namespace "http://example.com/ns/example-multicontainer";
prefix "ex";

container system-info {
description "Information about the system";

leaf hostname {
  type string;
  description "Hostname of the system";
}

leaf os {
  type string;
  description "Operating system of the system";
}

}

container network-config {
description "Network configuration of the system";

leaf interface-name {
  type string;
  description "Name of the network interface";
}

leaf ip-address {
  type string;
  description "IP address assigned to the interface";
}

leaf subnet-mask {
  type string;
  description "Subnet mask of the network interface";
}

}
// RPC operation to get interface information
rpc get-system-info {
description "Retrieve information about systeminfo";
output {
container system-info {
leaf hostname {
type string;
description "hostname";
}
leaf os {
type string;
description "Description of the os";
}
}
}
}
}

Thank you Michal, one followup question is, when we have subscribed with establish-push notifications on candidate datastore from application, and suppose application fails the validation, is there way to indicate to server to reject the change via netconf2 apis?

If validation fails on copy-config from candidate to running, the new config will automatically be rejected locally by sysrepo. You cannot affect this remotely via NETCONF.