[166457] in North American Network Operators' Group
Re: Network configuration archiving
daemon@ATHENA.MIT.EDU (Eric A Louie)
Fri Oct 25 00:51:35 2013
Date: Thu, 24 Oct 2013 21:51:22 -0700 (PDT)
From: Eric A Louie <elouie@yahoo.com>
To: Job Snijders <job.snijders@hibernianetworks.com>,
"nanog@nanog.org" <nanog@nanog.org>
In-Reply-To: <20131024212526.GC14735@Eleanor.local>
Reply-To: Eric A Louie <elouie@yahoo.com>
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
I know you said open source, but we're using Solarwinds Cattools with very =
good results.=A0 We also have Rancid running in the background.=0A=0A=0A=0A=
=0A=0A>________________________________=0A> From: Job Snijders <job.snijder=
s@hibernianetworks.com>=0A>To: nanog@nanog.org =0A>Sent: Thursday, October =
24, 2013 2:25 PM=0A>Subject: Network configuration archiving=0A> =0A>=0A>De=
ar all,=0A>=0A>I am unsure what we as networkers have done in the past, but=
I am sure =0A>we've done our fair share of atonement and don't have to kee=
p using =0A>RANCID.=0A>=0A>Some might say "it took ages to get rancid to do=
kinda what we want!", =0A>but not all software ages well. One might work i=
n environments where =0A>archived configurations are needed to even start p=
rovisioning, one =0A>might desire a separation between actual config and tr=
anscient data. =0A>=0A>As I am evaluating our path forward, I've compiled a=
small list of open =0A>source projects with some biased highlights. Your f=
eedback is most =0A>welcome, maybe I missed some interesting projects or de=
velopments. I =0A>would also be very interested in what other operators see=
k in a network =0A>config/state archive tool.=0A>=0A>RANCID - http://www.sh=
rubbery.net/rancid/=0A>=A0 =A0 * Support for a wild variery of devices and =
operating systems=0A>=A0 =A0 * complex perl code base [1]=0A>=A0 =A0 * no c=
entral developer team, the internet is littered with forks=0A>=0A>Oxidized =
- https://github.com/ytti/oxidized=0A>=A0 =A0 * modern & sexy approach with=
queue & workers=0A>=A0 =A0 * RESTful API (example: can bump devices to the=
head of the queue)=0A>=A0 =A0 * small user & developer base=0A>=A0 =A0 * w=
ritten in that ruby language=0A>=0A>Gerty - https://github.com/ssinyagin/ge=
rty=0A>=A0 =A0 * Seems easier to extend than RANCID=0A>=A0 =A0 * perl...=0A=
>=A0 =A0 * small user & developer base=0A>=0A>punc - https://code.google.co=
m/p/punc/=0A>=A0 =A0 * written in python, based on notch [2]=0A>=A0 =A0 * n=
o recent developments (although 2011 was a good wine year)=0A>=0A>[1] - htt=
p://honestnetworker.wordpress.com/2013/06/28/adding-new-device-support-to-r=
ancid/=0A>[2] - https://code.google.com/p/notch/=0A>=0A>Kind regards,=0A>=
=0A>Job=0A>=0A>=0A>=0A>
