Getting started with using kickers to run an action after a service has been created. How do you set one of the leaves from the service as a variable in the kicker?   Yang:     module postmod_test { namespace "http://example.com/postmod_test"; prefix postmod_test; import ietf-inet-types { prefix inet; } import tailf-common { prefix tailf; } import tailf-ncs { prefix ncs; } import tailf-kicker { prefix kicker; } description "Bla bla..."; revision 2016-01-01 { description "Initial revision."; } list postmod_test { description "This is an RFS skeleton service"; key name; leaf name { tailf:info "Unique service id"; tailf:cli-allow-range; type string; } uses ncs:service-data; ncs:servicepoint postmod_test-servicepoint; leaf vlan { type uint16; } container actions { tailf:action vlanCleaner { tailf:actionpoint CleanUpIpam; input { uses kicker:action-input-params; } output { } } } } } Python     # -*- mode: python; python-indent: 4 -*- import ncs from ncs.application import Service from ncs.dp import Action # ------------------------ # SERVICE CALLBACK EXAMPLE # ------------------------ class ServiceCallbacks(Service): @Service.create def cb_create(self, tctx, root, service, proplist): self.log.info('Service create(service=', service._path, ')') # --------------- # ACTIONS EXAMPLE # --------------- class CleanUpIpam(Action): @Action.action def cb_action(self, uinfo, name, kp, input, output, trans): self.log.info('action name: ', name) self.log.info('KICKER HAS BEEN KICKED') self.log.info(f'Action input: kicker-id: {input.kicker_id}, path: {input.path}, tid: {input.tid}') self.log.info(dir(input)) # --------------------------------------------- # COMPONENT THREAD THAT WILL BE STARTED BY NCS. # --------------------------------------------- class Main(ncs.application.Application): def setup(self): self.log.info('Main RUNNING') self.register_service('postmod_test-servicepoint', ServiceCallbacks) self.register_action('CleanUpIpam', CleanUpIpam) def teardown(self): self.log.info('Main FINISHED') Kicker   kickers data-kicker test3 monitor /postmod_test:postmod_test kick-node postmod_test:actions action-name vlanCleaner What I would like is to send the value of vlan into the kicker.   So from the service using the leaf vlan: leaf vlan { type uint16; } Create a kicker like so: kickers data-kicker test3 monitor /postmod_test:postmod_test kick-node postmod_test:actions action-name vlanCleaner variable VLAN value /vlan Is this possible with a data-kicker? I see the example in the guide using $PATH but not sure how that relates to a service leaf.   Thanks       ... View more

Trying to use the device platform to do leafref to the device loopbacks for a service. After adding the following Yang, I am getting the following warnings:   yang/SR-enable.yang:58: warning: the node is config, but refers to a non-config node 'platform' defined at yang/SR-enable.yang:49 yang/SR-enable.yang:65: warning: the node is config, but refers to a non-config node 'platform' defined at yang/SR-enable.yang:49 leaf platform { config false; tailf:link "/ncs:devices/ncs:device[ncs:name=current()/../device-name]/ncs:platform/ncs:name"; type leafref { path "/ncs:devices/ncs:device[ncs:name=current()/../device-name]/ncs:platform/ncs:name"; } } leaf loopback-XE { when "current()/../platform = 'ios-xe'"; type leafref { path "/ncs:devices/ncs:device[ncs:name=current()/../device-name]/ncs:config/ios:interface/ios:Loopback/ios:name"; } } leaf loopback-XR { when "current()/../platform = 'ios-xr'"; type leafref { path "/ncs:devices/ncs:device[ncs:name=current()/../device-name]/ncs:config/cisco-ios-xr:interface/cisco-ios-xr:Loopback/cisco-ios-xr:id"; } } Is this the correct way to do this or will it lead to problems down the road? We were using the ned-id instead of the platform but found that it is causing problems when trying to migrate to a new ned in version 5.   Thanks ... View more

Trying to implement fail2ban onto the NSO service fro external auth.  According to the docs NSO sends via stdin username and password. See the picture below.   Is it possible to add other fields to this? More specifically the remote IP of the auth request. This way we can implement fail2ban. Currently, the audit.log shows the from <HOST> but using a custom script for auth only sends via stdin (username, password).   So something like this: #logging.info("userpass info: {}".format(user_pass_split)) username = user_pass_split[0] password = user_pass_split[1] remote_ip = user_pass_split[2] ... View more

Trying to figure out how to use DataCallbacks within python. I am trying to rework this example from the forums https://community.cisco.com/t5/nso-developer-hub-discussions/callback-python-code/td-p/3510805 I am not making the links to get the daemon to create in the Main class. According to the API example:   Example handler and registration: class Handler(object): def get_object(self, tctx, kp, args): return {'leaf1': 'value', 'leaf2': 'value'} def get_next(self, tctx, kp, args, next): return None def count(self): return 0 dcb = DataCallbacks(log) dcb.register('/namespace:container', Handler()) _confd.dp.register_data_cb(dd.ctx(), example_ns.callpoint_handler, dcb) To register you use the dp.register_data_cb.   I am trying to do this in the class Main(ncs.application.Application):  which states: # If we registered any callback(s) above, the Application class # took care of creating a daemon (related to the service/action point). Code below.   What am I missing that will get the callback to register correctly and start the daemon for it? Newbie here when it comes to dealing with this, I tried to follow the guide but wasn't able to make the translation from Java to python. I tried to use self.dd.ctx() in the register_data_cb but dd doesn't have the ctx like in the api guide.   Yang: module pydp { namespace "http://tail-f.com/ns/example/pydp" ; prefix pydp; yang-version 1.1 ; import tailf-common { prefix tailf; } import ietf-inet-types { prefix inet; } container interface { list GigabitEthernet { key "name" ; leaf name { type string; } leaf shutdown { tailf:info "Shutdown the selected interface" ; type empty; } container stats { config false; tailf:callpoint "stats" ; leaf sent { type uint32; } leaf received { type uint32; } } action clear { tailf:actionpoint "clear" ; output { leaf received { type uint32; } leaf sent { type uint32; } } } } } } Python #!/usr/bin/env python import logging import time import socket import select #from config_ns import ns import ncs.maapi as maapi import _ncs import ncs from ncs.application import Service from ncs.experimental import DataCallbacks class DataCbs( object ): def __init__ ( self , log): self .log = log def get_object ( self , tctx , keypath , _args): self .log.info( "cb_get_elem: " + str (keypath)) if_name = str (keypath[ 2 ][ 0 ]) # (sent, recv) = get_counters(if_name) return { "stats" : { "sent" : 10 , "received" : 20 } } class Main(ncs.application.Application): def setup ( self ): # The application class sets up logging for us. It is accessible # through 'self.log' and is a ncs.log.Log instance. self .log.info( 'Main RUNNING' ) # Service callbacks require a registration for a 'service point', # as specified in the corresponding data model. # handler = DataCbs( self .log) dcb = DataCallbacks( self .log) dcb.register( '/pydp:interface/pydp:GigabitEthernet' , handler) _ncs.dp.register_data_cb( self .dd.ctx() , 'stats' , dcb) #d.start() # If we registered any callback(s) above, the Application class # took care of creating a daemon (related to the service/action point). # When this setup method is finished, all registrations are # considered done and the application is 'started'. def teardown ( self ): # When the application is finished (which would happen if NCS went # down, packages were reloaded or some error occurred) this teardown # method will be called. self .log.info( 'Main FINISHED' ) When starting the package I get the following logs related to trying to use the self.dd.ctx() <ERROR> 31-Oct-2019::15:00:20.577 pydp ComponentThread:main: - Traceback (most recent call last): File "/opt/ncs/ncs-4.7.4.3/src/ncs/pyapi/ncs_pyvm/ncsthreads.py", line 173, in run self.main._run() File "/opt/ncs/ncs-4.7.4.3/src/ncs/pyapi/ncs/application.py", line 216, in _run self.setup() File "/var/opt/ncs/state/packages-in-use/1/pydp/python/pydp/main.py", line 45, in setup _ncs.dp.register_data_cb(self.dd, 'stats', dcb) TypeError: dx argument must be a _ncs.dp.DaemonCtxRef Thanks ... View more