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.
Hi,
Is it possible to add additional attributes in a NETCONF RPC request in addition to message-id?
See the following example:
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="1" some-attribute="0001">
Looking at the NETCONF RFC...
NSO creates one instance of the action when the application starts. There is no way to get one python instance for each action invocation unless you create your own handler.
There is no proplist provided with actions, but what you can do is use varia...
The python lock will only block that specific function, or any other code that uses `with _provisioning_lock:` in the same python file. My suggestion would be to use the lock for the entire action like this:
import threading
_action_lock = threading...
Hi Fantolino,Can you elaborate on what this inconsistent behavior is and how it is failing? Also, this data that is shared is it in CDB or only in the python code?I will try and reply based on what I think is going on.When multiple transactions are m...
A bit late of a reply, but if the goal is to configure both in the same transaction I would recommend using a third service to configure the other two.
C
/ \
A B
With this approach, making a change in C will trigger both A and B in the sa...
In this case the GUI is trying to be helpful by validating the changes before doing commit. You will see the same thing in the CLI if you do "validate".
admin@ncs% commit dry-run
cli {
local-node {
data -servicey newservice {
...
