I have a package, called 'service1', in NSOv4.6 which is using resource-manager v3.3.0 to allocate id. In service1, my main.py looks like :
..some code.. # Create an allocation request.
# After calling this function, you have to call response_ready
# to check the availability of the allocated ID.
# Returns the allocated ID or None
my_index = id_allocator.id_read(username=tctx.username,
if not my_index:
self.log.info('Index not YET allocated')
return ..some code..
Now I need to push my service using three flags : commit-queue async, no-out-of-sync-check and atomic false. Unfortunately, if I perform a commit with those flags (in cli), it doesn't work : my id is well allocated but my service (service1) is not pushed to my device. There is an heritage problem of flags I think.
So how to handle this issue (if it is one, maybe it was done on purpose) ?
SW upgrade or migration is something you never can escape from so it's better to make it part of your process. The remaining challenge is to determine when to give up what has been working to secure your future needs. Martin and the NSO team will guide y...
There is not a single golden tool that fits all purposes simply because development processes and needs are different. Instead, pick the tooling you need from the Smörgåsbord and build your environment to suit your needs. Shashidhar will guide you throug...
How Verizon Streamlined NSO Development with Continuous Integration
This is a customer success story of how Verizon ITNUC builds a CI chain to streamline the NSO development process. The containerized NSO makes testing several NSO packages in para...
It is best practice to avoid storing your secrets (e.g., passwords and shared keys) in plain text, either on NSO or on the device. In NSO, we support multiple encrypted data types that are encrypted using a local key. Similarly, many devices such as Cisco...