Hi, in a PoC the customer has come up with the following question:   How does NSO handle or can NSO handle multiple versions of the same template? Imagine the following scenario:   We have a NSO test installation and a production installation as well as a given service (e.g. VPN Provisoning). The service template has been changed and tested on the test installation. Now the service with the new template shall be rolled out in production. BUT the service with the new template shall be only productively rolled out in a few locations (with little impact on overall network). Other service instances should not be altered (i.e. use the old template version). Once the rollout in the test locations has been approved the new version of the service can be rolled out network wide.   How does NSO in general handle multiple versions of templates (if at all)?   In the given example how would NSO/Fastmap know how to delete an old service instance (i.e. using old template) if it isn't really aware of the old template anymore (I assume it needs that info to determine which config snippets to undo in case of a DELETE)?   Or would the above scenario have to be implemented by using a copy of the initial service. e.g. an old service "VPN" (old template) and a new service "VPNv2" (new template) with entirely different namespaces as not to affect service instances using the old template?   All help very much appreciated and any additional, more general info on service versioning mechanisms in NSO would also be welcome. Thanks.   P.S.: I have looked at the Service Upgrade example in examples.ncs ( .../examples.ncs/getting-started/14-upgrade-service ) as well as here in the Forum (service upgrade with python) but these examples seem to deal only with changes in the YANG model (from version to version), not with changes in the XML template(s). ... View more

Hi,   I have a problem which I really dont understand. In one case it works, in another it doesnt.   Let's start with what works:   YANG:   leaf-list iphelper { type inet:ipv4-address { } }   The Leaf List is filled with data from WebUI: Template:   <ip> <address> <primary> <address>{/gw_ip}</address> <mask>{/subnetmask_usernet}</mask> </primary> </address> <?foreach {/iphelper}?> <helper-address><!--for each, input list--> <helper-address-list> <address>{/iphelper}</address> </helper-address-list> </helper-address> <?end?> This correctly generates multiple iphelper entries in the config for every item in the list. Like this:   interface Vlan975 ip vrf forwarding db-sus-ri ip address 192.168.2.1 255.255.255.0 ip helper-address 192.168.33.3 ip helper-address 192.168.44.4 ip helper-address 192.168.55.5 no shutdown no autostate exit So far so good. This all works. :) I am now trying to apply the same pattern to a List of IP prefixes:   YANG: leaf-list prefixlist { type inet:ipv4-address { //TODO: type here should be inet:ipv4-prefix (e.g. xxx.xxx.xxx.xxx/xx) } } Here is actually my first problem. If I use the inet:ipv4-prefix data type it is somehow impossible to fill the list from the WebUI (when i click on + an input field opens up and I can enter a prefix but when I click OK the input field closes but it just doesnt show up in the list in the WebUI). Haven't actually tried yet from CLI as customer wants the WebUI and I also believe it should be possible from both. Any ideas on this?   Template:   <ip> <!-- ...here is some vrf config which I left out here... --> <prefix-list><!--foreach seq 50--> <prefixes> <name>PL_{$vrf_name}_bgp2ebgp</name> <seq> <no>5</no> <permit> <ip>0.0.0.0/0</ip> </permit> </seq> </prefixes> <prefixes> <name>PL_{$vrf_name}_ebgp2bgp</name> <seq> <no>5</no> <permit> <ip>10.242.0.0/16</ip> <le>30</le> </permit> </seq> <seq> <no>10</no> <permit> <ip>10.243.0.0/16</ip> <le>30</le> </permit> </seq> <seq> <no>15</no> <permit> <ip>10.244.0.0/16</ip> <le>30</le> </permit> </seq> <seq> <no>20</no> <permit> <ip>10.245.0.0/16</ip> <le>30</le> </permit> </seq> <seq> <no>25</no> <permit> <ip>10.246.0.0/16</ip> <le>30</le> </permit> </seq> <seq> <no>30</no> <permit> <ip>10.247.0.0/16</ip> <le>30</le> </permit> </seq> <seq> <no>35</no> <permit> <ip>10.248.0.0/16</ip> <le>30</le> </permit> </seq> <seq> <no>40</no> <permit> <ip>10.249.0.0/16</ip> <le>30</le> </permit> </seq> <seq> <no>45</no> <permit> <ip>10.250.0.0/16</ip> <le>30</le> </permit> </seq> <?foreach {/prefixlist}?> <seq> <no>50</no> <permit> <ip>{/prefixlist}</ip> <le>30</le> </permit> </seq> <?end?> </prefixes> </prefix-list> </ip> As you can hopefully see the prefix data up to line (<no>) 45 is static and everything after that should be added from the leaf list entries. I get the following error:   Python cb_create error. Unknown error (66): DBS_VPN-template.xml:103 Expression '{/prefixlist}' resulted in an incompatible value '192.168.44.4192.168.55.5192.168.66.6' for /ncs:devices/device{IOSdev0}/config/ios:ip/prefix-list/prefixes{PL_db-sus-ri_ebgp2bgp}/seq{50}/permit/ip   I understand that NSO tries to apply the entire list (concatenated together) as one value, which doesn't work. But why does this work for IP helper? And how else do I access the single items of the list otherwise?   ... View more