@lmanor
Thanks, for the link to the transaction slides. The part I am stuck on is when the registered path is changed and the subscriber kicks off it will only handle one commit change at a time before moving on to the next one.
Say user A makes a commit to the registered path, it kicks off the subscriber, gets iterated and starts the post_iterate.
Then user B commits a change to the registered path a min later, subscriber sees the change and iterates the change, but waits to run post_iterate until user A's post_iterate is done.
What I am looking for is if the subscriber has the ability to run both users A request and user B request in post_iterate at the same time in different threads.
In the below user B's request makes it to the iterate function but will not be processed until user A has finished post_iterate function write_result.
Wondering if this isn't the right way to be kicking something like this off, the problem is it upgrades the router, reloads and waits for it to come back to do some post checks in the write_result function within post_iterate. Which causes user B's request to the /iosxe-upgrade/request/device to sit until post_iterate finishes the first one which could be 20-25 mins.
class IosxeUpgrade(Subscriber):
def init(self):
self.register('/iosxe-upgrade/request/device')
def pre_iterate(self):
return []
def iterate(self, kp, op, oldval, newval, state):
if op is ncs.MOP_VALUE_SET:
self.log.info('New IOS upgrade request: %s' % (str(kp[1:])))
state.append((newval, str(kp[1:])))
return ncs.ITER_RECURSE
def post_iterate(self, state):
for request in state:
self.write_result(ios_upgrade(self.log, request[0], request[1]), request[1])
def should_post_iterate(self, state):
return state != []I read over the API for subscriber but it's either not possible or I am missing something with getting post_iterate to run per request.
Thanks
