Add next-hop-group to local-routing-network-instance.

[dplore]

Change Scope

This is a follow up to #1324, refactoring of yang model groupings for openconfig-local-routing. This moves the static/next-hop-group grouping into the local-routing-network-instances module, allowing it to be reusable in modules that do not include network-instances.

No paths are changed, just the module in which they are contained.

         |     +--rw static-routes
         |     |  +--rw static* [prefix]
         |     |     +--rw prefix            -> ../config/prefix
         |     |     +--rw config
         |     |     |  +--rw prefix?        inet:ip-prefix
         |     |     |  +--rw set-tag?       oc-pt:tag-type
         |     |     |  +--rw description?   string
         |     |     +--ro state
         |     |     |  +--ro prefix?        inet:ip-prefix
         |     |     |  +--ro set-tag?       oc-pt:tag-type
         |     |     |  +--ro description?   string
-        |     |     +--rw next-hop-group
+        |     |     +--rw oc-loc-rt-netinst:next-hop-group
        |     |        +--rw oc-loc-rt-netinst:config
-        |     |     |  |  +--rw name?   -> /network-instances/network-instance/static/next-hop-groups/next-hop-group/name
+        |     |        |  +--rw oc-loc-rt-netinst:name?   -> ../../../../../../../oc-ni:static/next-hop-groups/next-hop-group/config/name
        |     |        +--ro oc-loc-rt-netinst:state
-        |     |     |  |  +--rw name?   -> /network-instances/network-instance/static/next-hop-groups/next-hop-group/name
+        |     |        |  +--rw oc-loc-rt-netinst:name?   -> ../../../../../../../oc-ni:static/next-hop-groups/next-hop-group/config/name

[OpenConfigBot]

Major YANG version changes in commit 301eb3c:
openconfig-local-routing.yang: 3.0.0 -> 4.0.0

[ghananigans]

To confirm, is this a breaking change for the overall OC model?

I see the previous change wasn't considered a breaking change, but this change had the breaking label.

[dplore]

To confirm, is this a breaking change for the overall OC model?

I see the previous change wasn't considered a breaking change, but this change had the breaking label.

This change is in the same category. We make a breaking change in the OC models and reflect that in the yang module versions. But the OC Release will not have breaking changes because the leaves we broke were not yet present in any OpenConfig public release. The forthcoming OC public release will only increment v5.2.0 to v5.3.0.