[rancid] Adding more commands during Rancid / Development
jason at biel-tech.com
Wed Sep 18 00:36:04 UTC 2013
Understood, but even when in a dev environment, what is the best way to
test changes to file for added commands? For example, I want to add new
commands to jrancid, but I am not 100% sure on the sub routine
configuration for parsing output. I suppose I can make the changes, use
rancid-run, and just keep tweaking until the output in the configs/
directory is what I want
I'm trying to mentally build out a process of adding commands for the
different devices we use without just shotgunning it.
On Tue, Sep 17, 2013 at 9:34 AM, Alan McKinnon <alan.mckinnon at gmail.com>wrote:
> On 17/09/2013 13:00, Jason Biel wrote:
> > While I understand the basics of adding additional commands to RANCID,
> > what is the ideal way to be testing new commands as I am debugging
> > them? Are most people running a dev RANCID install for testing?
> Most definitely :-)
> In any kind of real-life scenario, your rancid data in configs/
> naturally evolves into a very critical data source. Almost nothing else
> out there is capable of documenting real life systems to the extent
> rancid can. This is great for your ego, but also means you can't fiddle
> with it so much.
> I keep 2 dev installs for different purposes and follow the classic
> dev/test/debug/deploy strategy.
> There's a second reason why this is a good idea - it is very common for
> sysadmins to maintain their own little patchset to customize rancid
> behaviour (mostly to account for quirks between device models) and then
> repatch new releases if your tweaks didn't make it into the codebase. A
> dev setup makes this process so much easier.
> Alan McKinnon
> alan.mckinnon at gmail.com
> Rancid-discuss mailing list
> Rancid-discuss at shrubbery.net
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Rancid-discuss