github-mirror/route0
1
0
Fork 0
mirror of https://github.com/Wojtek242/route0.git synced 2024-12-22 15:44:39 +01:00
Code Issues Packages Projects Releases Wiki Activity

Explain configuration model choice

Browse Source
This commit is contained in:
Wojciech Kozlowski 2019-04-09 00:33:17 +02:00
parent 97728ffe89
commit b327103d44
1 changed files with 20 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

20
README.md
View File

@ -240,6 +240,26 @@ An experiment is simply a particular topology and scenario combination.
Technically this is redundant since scenarios are strictly associated with only
one topology, but using different terminology avoids confusion.
### A note on configuration files
The official FRR documentation recommends using only a single configuration
file `frr.conf` per router. This makes sense if we are only running a single
instance of each protocol on the device as then all the configuration is in one
place. Route 0 does not do that. Using a single configuration file would mean
that a lot of options would need to be repeated between different scenarios,
especially for `zebra` and `staticd`.
Furthermore, separating the config files makes it easier for the python scripts
to know which daemons to start (though of course it could just start all of
them every time or use some additional configuration file).
Finally, one last advantage of the Route 0 configuration model for our use case
is that the we group configurations per protocol, not per device. This makes
no sense if you're running only one instance of a protocol on a given device,
but since we are running multiple instances on multiple virtual nodes on a
single physical device, it makes it easier to inspect and compare the
configurations on a protocol level.
## Contributing
For information on how to contribute see [CONTRIBUTING](CONTRIBUTING.md).