diff options
author | Jan Srnicek <jsrnicek@cisco.com> | 2017-09-28 13:31:17 +0200 |
---|---|---|
committer | Jan Srnicek <jsrnicek@cisco.com> | 2017-09-28 13:31:17 +0200 |
commit | 8c31963654d126fa1b670c3d10c0ee81f445166a (patch) | |
tree | 1492d8e3dddf11364d8844571a4579895cb34705 /routing/routing-api/src/main/yang/vpp-routing@2016-12-14.yang | |
parent | 1ccfb17154bf025ac320ffea3433cd62bedc221c (diff) |
HC2VPP-232 - Secondary table lookup support
Ietf models now contains case table-lookup to be able to define
lookup to secondary table. It must be separated to dedicated case
as combining secondary-vrf and other next hop types(simple,multi,special)
does not make sense, its either you define lookup to table,
or you specify next hop of some kind.
This patch works properly only for write,
as read is affected by VPP-994/VPP-995.
Read at this state can detect that route is using table lookup,
but can't detect table that is used for that lookup.
Also, HC2VPP-237 must be done in future
Change-Id: Ia6976b35c6c1712d8add60beea7b0edbc4536974
Signed-off-by: Jan Srnicek <jsrnicek@cisco.com>
Diffstat (limited to 'routing/routing-api/src/main/yang/vpp-routing@2016-12-14.yang')
-rw-r--r-- | routing/routing-api/src/main/yang/vpp-routing@2016-12-14.yang | 66 |
1 files changed, 0 insertions, 66 deletions
diff --git a/routing/routing-api/src/main/yang/vpp-routing@2016-12-14.yang b/routing/routing-api/src/main/yang/vpp-routing@2016-12-14.yang deleted file mode 100644 index 5acda3976..000000000 --- a/routing/routing-api/src/main/yang/vpp-routing@2016-12-14.yang +++ /dev/null @@ -1,66 +0,0 @@ -module vpp-routing{ - - namespace "urn:ietf:params:xml:ns:yang:vpp-routing"; - prefix "vpp-routing"; - description "General extensions for routes to be able to use VPP route defining apis"; - - revision 2016-12-14 { - description "Initial revision."; - } - - import yang-ext { - prefix "ext"; - } - - import vpp-classifier { - prefix "classifier"; - } - - import hc2vpp-ietf-routing { - prefix "ietf-r"; - } - - typedef vni-reference{ - type uint32; - description "Vrf index reference"; - } - - grouping vpp-route-attributes { - //lookup_in_vrf - leaf secondary-vrf{ - type vni-reference; - description "Optional secondary vrf used to lookup in"; - } - - leaf classify-table{ - // classify_table_index + is_classify flag - type classifier:classify-table-ref; - description "Optional reference to classify table"; - } - } - - grouping vpp-routing-protocol-attributes{ - //vrf_id - leaf primary-vrf{ - type vni-reference; - mandatory true; - description "Main vrf associated to route"; - } - } - - augment /ietf-r:routing/ietf-r:routing-instance/ietf-r:routing-protocols/ietf-r:routing-protocol{ - ext:augment-identifier "routing-protocol-vpp-attr"; - container vpp-protocol-attributes { - presence "Config attributes"; - uses vpp-routing-protocol-attributes; - } - } - - augment /ietf-r:routing-state/ietf-r:routing-instance/ietf-r:routing-protocols/ietf-r:routing-protocol{ - ext:augment-identifier "routing-protocol-state-vpp-attr"; - container vpp-protocol-state-attributes { - presence "Operational attributes"; - uses vpp-routing-protocol-attributes; - } - } -}
\ No newline at end of file |