I can see in the development guide examples of setting operational data via java or the cli. Does anybody have an example of setting this via python?
Is it possible to configure operational data during service creation? In this case, it is for use during re-deploy. We have a function that checks if a subinterface is already used on the router and adds 1 to find an unused one. This causes problems during re-deploy since it always wants to add 1 to the subinterface. I am trying to accomplish setting the config false leaf service_data to the assigned sub interface value during initial service creation.
yang
Currently, have this going in the python but looking for a cleaner solution, still digging into the API docs but nothing is jumping out.
class ServiceCallbacks(Service):
# The create() callback is invoked inside NCS FASTMAP and
# must always exist.
@Service.create
def cb_create(self, tctx, root, service, proplist):
self.log.info('Service create(service=', service._path, ')')
test_var = 44
proplist.append(('sub_int', str(test_var)))
self.log.info(proplist)
if int(proplist[0][1]) != 0:
self.log.info(f"Service instance was set for {service.op_data}")
return proplist
@Service.pre_modification
def cb_pre_modification(self, tctx, op, kp, root, proplist):
self.log.info('Service premod(service=', kp, ')')
proplist = [('deploy_status', str(op))]
return proplist
@Service.post_modification
def cb_post_modification(self, tctx, op, kp, root, proplist):
self.log.info('Service premod(service=', kp, ')')
pattern = "{(.*?)}"
service_name = re.search(pattern, str(kp)).group(1)
self.log.info(service_name)
self.log.info(proplist[1][1])
root.test_op[service_name].op_data = proplist[1][1]
Then during re-deploy instead of running the custom function to find an unused sub interface ID it will use the value in the operational leaf service_data.
Is this possible or is it recommended?
