CNC 4.0 - support NSO LSA: Hi,One of the CNC 4.0 features is to support NSO LSA. For that, NSO is expected to continue supporting same functionality as previous non-LSA NSO.This is for confirming that it is be supported transparently.F107608 CNC-114: Must support NSO LSA for large scale deployments:"CNC needs to be deployable in a single NSO server configuration, where the CFS and RFS functionalities co-reside on a single server."Not in scope:...Multiple top-level NSO serversSome of the main dependencies of CNC on NSO, is for the Upper NSO(CFS node) to response on all services/resources, for listing, fetching payloads and notifications.Notice CNC depends on NSO services, as well as resources such as sid-list.Restconf APIs/data for fetching service payloads and more.limit and offset parameters.content parameter.Restconf service-state-changes stream with replay-support for plan notification changes.JSON-RPC APIsloginChanges notifications via start_subscription, subscribe_changesquery - some paths and /ncs:packages/packageget_system_setting methodOther dependencies are listed as described below:NSO adoption for CNC - CNC NSO requirements and dependencies:Thanks
LSA Architecture intends for the large scale. So CFS and RFS should be deployed in seperate nodes. The ask for installing both on the same node defeat the original purpose. Is there any use-case that you ask for this support?Hi Linh,Thanks for the reply.What you wrote is not our request.For CNC 4.0, request is for NSO is expected to continue supporting same functionality as previous non-LSA NSO. This is for confirming that it is be supported transparently.CNC 4.0 services are ietf-l2vpn-ntw etc', as well as resources such as sid-list, and possible customer custom FPs.Some of the main use cases:Expecting the Upper NSO(CFS node) to response on all CNC 4.0 services/resources, for listing, fetching payloads and notifications.Some CNC used services/resources paths:ietf-l2vpn-ntw:l2vpn-ntw/vpn-services/vpn-serviceoietf-l2vpn-ntw:l2vpn-ntw/vpn-services/vpn-service-planietf-l3vpn-ntw:l3vpn-ntw/vpn-services/vpn-servicecisco-flat-L2vpn-fp:l2vpn-route-policycisco-flat-L3vpn-fp:l3vpn-route-policycisco-sr-te-cfp:sr-te/cisco-sr-te-cfp-sr-policies:policies/policycisco-sr-te-cfp:sr-te/cisco-sr-te-cfp-sr-odn:odn/odn-templateresource-allocator:resource-pools/id-allocator:id-poolcisco-sr-te-cfp:sr-te/cisco-sr-te-cfp-sr-policies:policies/sid-listietf-l2vpn-ntw:l2vpn-ntw/id-poolsietf-l3vpn-ntw:l3vpn-ntw/vpn-profiles/valid-provider-identifiers/routing-profile-identifierietf-te:te/tunnels/tunnelcisco-flat-L2vpn-fp:flat-L2vpncisco-flat-L3vpn-fp:flat-L3vpnocisco-flat-L3vpn-fp:flat-L3vpn-planAnother aspect:since CNC CAT communicates only with CFS node in the NSO LSA cluster, what is the expectation in case of failure of the CFS node ? For such cases when NSO LSA CFS/UI node is temporary down etc'. In this case, only retry mechanism ? or other NSO node/instance takes its place ?Hi Liran,I deploy all tsdn services through cfs node, then tested all requested service/resource path through cfs. They all worked as expected. The services are still there in Van's CFS. If you are interested in seeing them, please contact Van for the server info.About CFS failure question, in the real production scenarios, it is recommend to set HA for CFS, if the primary CFS is down, the secondary CFS would take it over.Thanks,-LinhWe reviewed it in Van's setup, looking good, thank you.We do have some follow-up questions for understanding, will add it on email.it works as expected