[Yang] Add Yang Model and tests for VNET_ROUTE_TUNNEL table - v2

[miatttao]

Why I did it

Added YANG model and tests for VNET_ROUTE_TUNNEL table to provide schema validation and testing capabilities for VNET route tunnel configurations.

Work item tracking

• Microsoft ADO (number only):

How I did it

• Edit the existing sonic-vnet.yang model to define the VNET_ROUTE_TUNNEL table schema
• Added comprehensive test cases covering both valid and invalid configurations
• Implemented validation for:
  • Mandatory endpoint field
  • MAC address format
  • VXLAN ID range
  • Name format (vnet_name:prefix)

How to verify it

1. Review the YANG model against the config_db schema
2. cd src/sonic-yang-models && python3 setup.py test

Test Cases Validated

Yang Model Validated (assertionError can be ignored)

Which release branch to backport (provide reason below if selected)

• 201811
• 201911
• 202006
• 202012
• 202106
• 202111
• 202205
• 202211
• 202305

Tested branch (Please provide the tested image version)

Description for the changelog

Link to config_db schema for YANG module changes

https://github.com/Azure/sonic-buildimage/blob/master/src/sonic-yang-models/doc/Configuration.md/VNET_ROUTE_TUNNEL

[linux-foundation-easycla]

The committers listed above are authorized under a signed CLA.

• ✅ login: miatttao (fec860e, 6db2d16, a650a9b, 8367814, 770841c, 9edb03d, 5e394d9, 163f363, c9f8488, cebfe3c, 06b9d19, ba92d31, a0be257, f7e11e2, 0ea4746, 1c517ba, c1535ee, a68a9ab, bc04f3f, 065726e)

[mssonicbld]

/azp run Azure.sonic-buildimage

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[mssonicbld]

/azp run Azure.sonic-buildimage

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[mssonicbld]

/azp run Azure.sonic-buildimage

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[mssonicbld]

/azp run Azure.sonic-buildimage

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[mssonicbld]

/azp run Azure.sonic-buildimage

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[mssonicbld]

/azp run Azure.sonic-buildimage

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[mssonicbld]

/azp run Azure.sonic-buildimage

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[mssonicbld]

/azp run Azure.sonic-buildimage

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[miatttao]

03/06: Merged the latest changes from master to rerun the auto-cancelled pipeline.

[mssonicbld]

/azp run Azure.sonic-buildimage

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[miatttao]

03/07 a0be257 passed all pipeline checks.
Changed ip_address type

[anish-n]

could you change this to vni. Upon checking sonic-swss I see that this should be called vni:
https://github.com/sonic-net/sonic-swss/blob/master/orchagent/vnetorch.cpp#L2733

@prsunny should we update the HLD https://github.com/sonic-net/SONiC/blob/gh-pages/doc/vxlan/Vxlan_hld.md to say that the tunnel route field is vni vs vxlandid?

[miatttao]

Hi Anish, for a specific vnet_route_tunnel, can the vni in VNET_ROUTE_TABLE overwrite the base vni in VNET_TABLE? Or do they have to be the same? See below for reference. Thanks!

[anish-n]

The vni in VNET_ROUTE_TUNNEL_TABLE overrides the base vni in VNET_TABLE for any traffic destined to the IP of prefix in VNET_ROUTE_TUNNEL_TABLE. It is also an optional field, so if none is provided the default VNET_TABLE vni is used for the traffic.