[FROG] new config

[Donald Sharp]

The way I think of it:
/etc/frr/frr.conf is the saved config
vtysh -c "show running"  is the running config

frr-reload.py wants to take the config file specified and make it the
running config, not the saved config.  frr-reload.py also does not make any
attempt to have a new saved config in /etc/frr/frr.conf.  Nor does it
attempt to start/stop daemons that may need to run.  This is done by other
scripting, we expose frr-reload.py to allow for people to mix-n-match as
they please.  Having said that `systemctl reload frr` does attempt to do
that, in that it expects you to put the new frr.conf file in
`/etc/frr/frr.conf` and it will automatically load that file and start/stop
the appropriate daemons for the new running config.  This also has the
effect of after running reload the running config is the same as the saved
config.  For me I just put the changes in /etc/frr/frr.conf and issue a
`systemctl reload frr`

donald

On Mon, Aug 12, 2024 at 8:19 PM Randy Bush <randy at psg.com> wrote:

> > i manage/generate router configs centrally and push/expect them out to
> > devices.  first time sorting how to do this with frr.
> >
> > my mental model would be to rsync a new `/etc/frr/frr.conf` to the
> > target and ask it to be loaded in some way.  but reading the page on
> > `frr-reload.py`, that does not seem to be the expected model.  so what
> > is the expected model?
> >
> > do i essentially push to new config to, e.g. `/etc/frr/frr.new` and
> > then run `frr-reload.py --reload /etc/frr/frr.new`, and it will update
> > `/etc/frr/frr.conf`?
>
> this is all frustratingly conplex; or, more likely, i am just confused.
>
> what i am used to is some command to just load from a canonic unified
> configuration file `load override <foo>`
>
> when i have the major config issues sorted, i am sure i will appreciate
> the deamons having and retaining a lot of state.  while i am trying to
> get the basics working, not so much.  i can not be sure if a change is
> unsatisfactory because the config is still incorrect or if there is
> some sticky state.
>
> randy
>
> _______________________________________________
> frog mailing list
> frog at lists.frrouting.org
> https://lists.frrouting.org/listinfo/frog
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.frrouting.org/pipermail/frog/attachments/20240812/3eed46b7/attachment.htm>