Hi,   Shouldn't this delete be part of your "pre-modification" logic? That is where you set what you expect as default configuration. You typically want to avoid "deletes" in FastMap.   Roque ... View more

well...you missing an iterator. Something like this (not tested but check the developer guide):   <config-template xmlns="http://tail-f.com/ns/config/1.0" servicepoint="HOSTNAME">   <devices xmlns="http://tail-f.com/ns/ncs" foreach=' {/DEVICE}'>     <device><name>{.}</name>       <config>         <hostname xmlns="http://tail-f.com/ned/cisco-ios-xr">{string(.)}</hostname>       </config>     </device>   </devices> </config-template> ... View more

Hi, The best way to do what you need is to partition your service in two transactions via reactive fastmap. If you are not familiar with reactive fastmap, there are plenty of references in this forum or in the documentation. Such as here: https://community.cisco.com/t5/nso-developer-hub-documents/nso-dev-days-python-reactive-fastmap-lab/ta-p/3652772 Roque ... View more

I just want to point out that maybe you are trying to achieve with NSO two objectives that may be in contraction. On one side, you want NSO to automate your provisioning and activation. On the other side, you want to personalise your operator experience in an increasingly complex way.    You may have solve this current problem but you may have new challenges ahead. This is the reason why a lot of users implement a separate GUI framework on top of NSO APIs and de-couple the two problems. ... View more

Hi,   Are you certain that you are requesting the same query to the device over the two methods? You can search the exact RPC and what NSO is doing by looking at the device traces. In my experience, you are probably are searching from a long tree.   Roque ... View more

Hi Sean,   I have a similar situation with IOS-XR 6.5.2 that may explain what is going on.   What happened to me was a bug in IOS-XR (CSCvo17475) that  rejected SSH interactive sessions (like NSO opens) while allowing non-interactive ssh sessions (like what you open manually).   As a user, SSH was working from the shell but not from NSO nor plain python scripts. The work-around of using a proxy (as you did) solved the problem temporarely. The final fix was a patch for IOS-XR.   Just a reference of a similar situation that had a logical explanation. You may want to check the support database of UCS if there is a similar problem already reported or with TAC.   Roque ... View more

Hi,   tailf:set-hook is basically an extension that appliies to tailf:callpoint. It does not have any requirements from python or java or erlang as the callpoint ID will be applied as normal.   What tailf:set-hook does is to define if the scope of the transformation. I believe by default is "subtree" but could be set to "node" or "object".   Roque     tailf:callpoint id Identifies a callback in a data provider. A data provider implements access to external data, either configuration data in a database or operational data. By default ConfD uses the embedded database (CDB) to store all data. However, some or all of the configuration data may be stored in an external source. In order for ConfD to be able to manipulate external data, a data provider registers itself using the callpoint id as described in confd_lib_dp(3). A callpoint is inherited to all child nodes unless another 'callpoint' or an 'cdb-oper' is defined. The callpoint statement can be used in: leaf , leaf-list , list , container , refine , and grouping . The following substatements can be used: tailf:config If this statement is present, the callpoint is applied to nodes with a matching value of their 'config' property. tailf:transform If set to 'true', the callpoint is a transformation callpoint. How transformation callpoints are used is described in the 'Transformations, Hooks, Hidden Data and Symlinks' chapter in the User's Guide. tailf:set-hook Set hooks are a means to associate user code to the transaction. Whenever an element gets written, created, or deleted, user code gets invoked and can optionally write more data into the same transaction. The difference between set- and transaction hooks are that set hooks are invoked immediately when a write operation is requested by a north bound agent, and transaction hooks are invoked at commit time. The value 'subtree' means that all nodes in the configuration below where the hook is defined are affected. The value 'object' means that the hook only applies to the list where it is defined, i.e. it applies to all child nodes that are not themselves lists. The value 'node' means that the hook only applies to the node where it is defined and none of its children. For more details on hooks, see the 'Transformations, Hooks, Hidden Data and Symlinks' chapter in the User's Guide. tailf:transaction-hook Transaction hooks are a means to associate user code to the transaction. Whenever an element gets written, created, or deleted, user code gets invoked and can optionally write more data into the same transaction. The difference between set- and transaction hooks are that set hooks are invoked immediately when an element is modified, but transaction hooks are invoked at commit time. The value 'subtree' means that all nodes in the configuration below where the hook is defined are affected. The value 'object' means that the hook only applies to the list where it is defined, i.e. it applies to all child nodes that are not themselves lists. The value 'node' means that the hook only applies to the node where it is defined and none of its children. For more details on hooks, see the 'Transformations, Hooks, Hidden Data and Symlinks' chapter in the User's Guide. tailf:cache If set to 'true', the operational data served by the callpoint will be cached by ConfD. If set to 'true' in a node that represents configuration data, the statement 'tailf:config' must be present and set to 'false'. This feature is further described in the section 'Caching operational data' in the 'Operational data' chapter in the User's Guide. tailf:opaque Defines an opaque string which is passed to the callback function in the context. tailf:internal For internal ConfD / NCS use only. ... View more

Hi, I should also add that you should avoid using the "legacy-REST" API that you are using and move to the "standard-REST-RESTCONF" API as it is the current best practice.   Example GET RESTCONF call with Json output: curl -X GET \ http://localhost:8080/restconf/data/tailf-ncs:java-vm \ -H 'Accept: application/yang-data+json' \ -H 'Authorization: Basic YWRtaW46YWRtaW4='   Where please pay attention that "tailf-ncs" is the name of the YANG module (and not its prefix) when you change namespaces in your query   ... View more