Internal CS policies and VPN services mapping with parent service model: IN CNC UI , We have use-cases to know the mapping between internal policies/services that gets created from different model. Example for Circuit style model, it creates 2 internal SR-policies which has a different service key (Config ID/Name). The pattern we are seeing is '-internal' at the end. To understand and map the parent to the internal, we need to hardcode in our code.Is NSO model has this information available ? If not can this be a new requirement .
I'm not sure what exactly you are asking? Are you asking for the parent service backpointers to be available in the model instead of using the hardcoded service names based on `-internal` suffix?Thats correct. How do we know which parent service created the internal services ?Hi Dedeepya,You should be able to "get-modifications" to get the underlying services and then keep track of the parent services from CNC UI?Thanks,RegiHi,Had a discussion with my team and it seems you are able to get the service-meta-data via restconf which will show the backpointers ( ie parent services ).Command:Output:<div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent"><pre><vpn-services xmlns="urn:ietf:params:xml:ns:yang:ietf-l2vpn-ntw" xmlns:l2vpn-ntw="urn:ietf:params:xml:ns:yang:ietf-l2vpn-ntw">  <vpn-service refcounter="3" backpointer="[ /ietf-nss:network-slice-services/cisco-nss:slice-service-plan[cisco-nss:service-id='L2-ANY-TO-ANY']/cisco-nss:plan/cisco-nss:component[cisco-nss:type='ietf-nss-nano:sdp'][cisco-nss:name='0']/cisco-nss:state[cisco-nss:name='ietf-nss-nano:config-apply'] /ietf-nss:network-slice-services/cisco-nss:slice-service-plan[cisco-nss:service-id='L2-ANY-TO-ANY']/cisco-nss:plan/cisco-nss:component[cisco-nss:type='ietf-nss-nano:sdp'][cisco-nss:name='1']/cisco-nss:state[cisco-nss:name='ietf-nss-nano:config-apply'] /ietf-nss:network-slice-services/cisco-nss:slice-service-plan[cisco-nss:service-id='L2-HUB-SPOKE']/cisco-nss:plan/cisco-nss:component[cisco-nss:type='ietf-nss-nano:shared-slice'][cisco-nss:name='L2-ANY-TO-ANY']/cisco-nss:state[cisco-nss:name='ietf-nss-nano:config-apply'] ]"></pre></div></div>....Thanks,RegiExample you shown is for VPN services. My understanding is this will be same for SR Policy model as well. "backpointer" will reference the CS model instance that created these internal SR polices. Please confirm.Thank you. Hi Dedeepya,Sorry for the late response, but that's correct the service-meta-data is the same for all types of services as this is common information provided by the NSO platform and the our T-SDN CFPs itself.Thanks,Regi