Heads Up :
The post you are writing will appear in a public forum. Please ensure all content is appropriate for public consumption. Review the employee guidelines for the community here.
A key concept in NSO is transactions. Transactions exist primarily to safeguard the ACID properties of the CDB, and additionally to ensure data validation and run custom callbacks providing data transformation capabilities. This is mostly with the he...
When you run root.vpnconfig__vpnconfig[SERVICENAME].pedevice.create(pe_device_name) form your l3vpn service, you will create an instance of the vpnconfig service. That service instance will be the one creating the vpn config on the device, which you'...
It would probably be possible to open another read transaction within the service callback, read the data on the device, and expand the service config based on that. But then you'd have to figure out a way to keep track of service vs oob config, whic...
There is unfortunately no way to achieve this in templates as far as I know. You need to reconcile the service in this case, with the "keep-non-service-config" flag, so that NSO can see that something has been added to the list item after it was crea...
To start with, you can extract the python code to access the nodes through maagic by first enabling devtools and then showing the data nodes through CLI, and piping it with "display maagic". So something like this:admin@ncs# devtools true ...
The post-modification callback would work if you're going for the stacked service approach. I guess you'd have to do that if you want different API calls for different components of a service, all managed through one servicepoint.I was thinking about...
