From 665d1c5bdb24aa0aef79405dc2f2962b930fb9b3 Mon Sep 17 00:00:00 2001 From: Thomas Mangin Date: Tue, 3 Mar 2020 20:01:56 +0100 Subject: vrf: T31: initial support for a VRF backend in XML/Python This is a work in progress to complete T31 whoever thought it was less than 1 hour of work was ..... optimistic. Only VRF vreation and show is supported right now. No interface can be bound to any one VRF. --- interface-definitions/include/interface-vrf.xml.i | 12 +++++ interface-definitions/vrf.xml.in | 58 +++++++++++++++++++++++ 2 files changed, 70 insertions(+) create mode 100644 interface-definitions/include/interface-vrf.xml.i create mode 100644 interface-definitions/vrf.xml.in (limited to 'interface-definitions') diff --git a/interface-definitions/include/interface-vrf.xml.i b/interface-definitions/include/interface-vrf.xml.i new file mode 100644 index 000000000..7e880e6ee --- /dev/null +++ b/interface-definitions/include/interface-vrf.xml.i @@ -0,0 +1,12 @@ + + + VRF instance name + + vrf name + + + + + VRF name not allowed or to long + + diff --git a/interface-definitions/vrf.xml.in b/interface-definitions/vrf.xml.in new file mode 100644 index 000000000..e270e8b90 --- /dev/null +++ b/interface-definitions/vrf.xml.in @@ -0,0 +1,58 @@ + + + + + VRF configuration + + 210 + + + + + Disable services running on the default VRF from other VRF (ssh, bgp, ...) + + + + + + Enable binding across all VRF domains for IPv4 + + + + + + + Virtual Routing and Forwarding + + + + VRF name not allowed or to long + + name + the vrf name must not contain '/' and be 16 characters or less + + + + + + The routing table to associate to this VRF + + + + Invalid kernel table number + + number + the VRF must be a number between 1 and 2^31-1 + + + + + + Description of the VRF role + + + + + + + \ No newline at end of file -- cgit v1.2.3