If you are an NSO user, you are probably aware that when you write and read data from any of the NSO northbound interface agents, such as NETCONF, RESTCONF, CLI, MAAPI, etc., those agents are going through the NSO transaction manager before reaching the CDB "running" datastore and the southbound NEDs.
Even if you are aware that the NSO transaction manager is tightly integrated with all NSO components, when managing the network using the NSO device and/or service manager, there are a number of crucial decisions to consider. Such as, are you going to enable the NSO commit queues, are you going to make use of the logical datastores that comes with NMDA, how will you reconcile your services with a device that is out-of-sync, and what requirements for northbound interfaces will you have for the devices you deploy in your network?
Did you also know that, in the bigger picture, NSO’s transaction manager is extended by the devices transaction managers, that may be implemented by ConfD or not at all, and that NSO may be managing a hundred other transaction managers in parallel?
Even if the device is enabled by ConfD and its transaction manager, there are a quite a few things to consider when deciding on how to manage such devices and maximizing the value of a full-fledged transaction manager instead of the opposite.
In this 1h workshop, scheduled on February 18th, 10am PST, we will spend most of our focus on the integration between NSO and ConfD's transaction managers and go through the more common and impactful design decisions when integrating with the two while keeping the bigger picture in mind.