+* A new leaf element will be added to neutronvpn-config container in neutronvpn-config.yang to
+ accept inputs for the ``opendaylight-vni-ranges`` pool from the configurator via the
+ corresponding exposed REST API. In case this is not defined, the default value defined in
+ ``netvirt-neutronvpn-config.xml`` will be used to create the ``opendaylight-vni-ranges`' pool.
+
+ .. code-block:: none
+ :caption: neutronvpn-config.yang
+ :emphasize-lines: 5-8
+
+ container neutronvpn-config {
+ config true;
+ ...
+ ...
+ leaf opendaylight-vni-ranges {
+ type string;
+ default "70000:99999";
+ }
+ }
+
+* Provider network-type and provider segmentation-ID need to be propagated to FIB Manager to manipulate
+ flows based on the same. Hence:
+
+ #. A new grouping ``network-attributes`` will be introduced in ``neutronvpn.yang`` to hold
+ network type and segmentation ID. This grouping will replace the leaf-node
+ ``network-id`` in ``subnetmaps`` MD-SAL configuration datastore:
+
+ .. code-block:: none
+ :caption: neutronvpn.yang
+ :emphasize-lines: 1-27
+
+ grouping network-attributes {
+ leaf network-id {
+ type yang:uuid;
+ description "UUID representing the network";
+ }
+ leaf network-type {
+ type enumeration {
+ enum "flat";
+ enum "vlan";
+ enum "vxlan";
+ enum "gre";
+ }
+ }
+ leaf segmentation-id {
+ type uint32;
+ description "Optional. Isolated segment on the physical network.
+ If segment-type is vlan, this ID is a vlan identifier.
+ If segment-type is vxlan, this ID is a vni.
+ If segment-type is flat/gre, this ID is set to 0";
+ }
+ }
+
+ container subnetmaps {
+ ...
+ ...
+ uses network-attributes;
+ }
+
+ #. These attributes will be propagated upon addition of a router-interface or addition of a
+ subnet to a BGPVPN to VPN Manager module via the ``subnet-added-to-vpn`` notification
+ modelled in ``neutronvpn.yang``. Hence, the following node will be added: