- User Since
- Nov 12 2019, 5:38 PM (15 w, 2 d)
Mon, Feb 24
The patch is ready for inclusion.
This work raised an issue with the current pattern of using Interface(..).remove() which is used in VLANIf as it requires Interface to know that EthernetIf can not be deleted (an implementation detail which should remain in EthernetIf).
Thu, Feb 20
This work overtakes T2046, as it implements the same _create/_delete interface. If merged it would replace it.
Wed, Feb 19
We could indeed create the VRF as we parse interfaces, and auto-allocate the VRF number, removing this control from the user.
Tue, Feb 18
Mon, Feb 17
Fri, Feb 14
initial patch released calling for a review / comments ( PR from github.com/thomas-mangin/vyos-1x T2028 branch) - show command not migrated yet.
Wed, Feb 12
> egrep -ri '[^ag]gre[^apens]' . 251ms Wed 12 Feb 13:22:34 2020 ./.git/config:[branch "T2028-GRE"] ./.git/logs/HEAD:1adf2818083c40cf81d7747a4c9d26e85c235a60 1adf2818083c40cf81d7747a4c9d26e85c235a60 Thomas Mangin <email@example.com> 1581513634 +0000 checkout: moving from T2028-GRE to current ./.git/FETCH_HEAD:1adf2818083c40cf81d7747a4c9d26e85c235a60 not-for-merge branch 'T2028-GRE' of github.com:thomas-mangin/vyos-1x ./data/templates/rsyslog/rsyslog.conf:$RepeatedMsgReduction on ./src/op_mode/maya_date.py: August 11, 3114 BC gregorian date. In this case UNIX epoch
Here is a patch to implement VRF. Binding is set to work on all VRF for daemon so that BGP and other protocols will work on all VRF.
while it would be quite nice to have a Cumulus 4.0+ like default management VLAN and make all services management aware (which would quite considerably increase the among of work to get something out), I am proposing instead make sure that all services running on the default VRF are available on VRF as a first step.
Mon, Feb 10
Wed, Feb 5
Identified configuration format change:
I have a use case for VRF / Linux namespace with VyOS and was wondering if there was a way to break this task down, first allowing the manual creation of VRF/namespace using the CLI (without linking the work to BGP). I will be able to contribute the required changes to the vyos-1x repository should I be given enough direction on how you would like to proceed.