[quagga-dev 8534] Re: Any interest in "configure replace"?

Stephen Hemminger shemminger at vyatta.com
Thu Feb 24 06:53:41 GMT 2011


On Wed, 23 Feb 2011 22:33:53 -0800
Wei Sun <sun.106 at gmail.com> wrote:

> Hi Roman,
> 
> Thanks for the reply! It's good to know that people also have the same need.
> Thanks a lot also for providing us the details of setting up a git repo! We
> will follow the steps once the code is ready.
> 
> Right now the code is still under development. We also have a formal review
> and test processes internally. It will take some time before we could push
> it out. So please be patient :)
> 
> Thanks and regards,
> 
> Wei
> 
> Hi Wei
> >
> > Reloading the configuration without disrupting any router (ospf, rip and
> > bgp) peerings is a major issue for us and our workaround is a wrapper
> > script that compares old and new configuration and sends the changed
> > config commands to each affected daemon. But over time it became too
> > tedious to cope with every syntax inconsistency (e.g. "address-family"
> > semantically representing an extra level of indentation without actually
> > being indented).
> >
> > So yes, we are interested. Please setup a git repo somewhere (for
> > example on github, like people from Boing did
> > https://github.com/basman/quagga-mtr or use your own), using two
> > branches/remotes: one main branch connected to the official quagga repo
> > and another one containing your configure replace patches. That way you
> > can easily pull updates from mainline, which will be necessary since
> > evolution goes slowly on the quagga planet.
> >
> > Regards,
> > Roman
> >

If it is any help, Vyatta feeds quagga dynamically and never actually
saves the route config in quagga format. The changes are kept in a separate
configuration system and when commit is done the changes are sent
is as vtysh commands.

-- 



More information about the Quagga-dev mailing list