Faster netlab up and create frr.conf as files? #2674
Replies: 1 comment 5 replies
-
This is how daemons (like bird or dnsmasq) work. One of these days I have to write a daemons documentation ;)
It would definitely work for control-plane daemons configured through FRR, but how do you currently set IP addresses on interfaces? I know I tried to use "ip address" commands in FRR and it did not end well (at least not when I was testing it). Other daemons might not even have the ip command available in the container, so we do initial configuration from the outside, using ip netns exec commands on the host to configure container networking features. Also, there are tons of other data-plane features that FRR does not configure, so we have to use other Linux commands to get things like VLANs or VXLAN up and running. Any ideas on how to solve these minor details? 😎 |
Beta Was this translation helpful? Give feedback.

Uh oh!
There was an error while loading. Please reload this page.
-
So netlab has the frr.ospvX Jinja files / it has to create at some point the configuration for those devices.
What I was wondering about is the idea for frr devices to create those configs as files (for clab in the clab_files directory)
and eventually bind them into the clab.yml file directly?
This would allow to just use clab up and have them instantly configured without needing later ansible configurations.
(Maybe I could have done my scripts better in searching for the frr.conf creation function in netlabs codebase and use it directly.)
Or just allow to create the config files only with an argument without destroying netlabs original workflow?
I think that could be useful.
Anyways I would still like to make the netlab up command become faster :D
Maybe we could discuss on that?
Beta Was this translation helpful? Give feedback.
All reactions