[169470] in North American Network Operators' Group
Re: Managing IOS Configuration Snippets
daemon@ATHENA.MIT.EDU (Simon Knight)
Thu Feb 27 16:46:25 2014
In-Reply-To: <530FA8AB.6090905@buh.org>
From: Simon Knight <simon.knight@gmail.com>
Date: Thu, 27 Feb 2014 13:45:38 -0800
To: Erik Muller <erikm@buh.org>
Cc: "nanog@nanog.org" <nanog@nanog.org>
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
Definitely. Depends what form the database takes - I don't think SQL
is the right answer here. Sticking with flat files and perl scripts as
much as possible is good guidance.
I'm biased, but I'd go with Python: http://www.youtube.com/watch?v=EGK5jjyUBCQ
--Simon
On 27 February 2014 13:05, Erik Muller <erikm@buh.org> wrote:
> On 2/27/14, 15:52 , Joe Abley wrote:
>>
>> This is not any kind of sensible answer to the original question, but
>> the general approach "give ops people a shell on a box with a rancid
>> repository, encourage them to write scripts that do stuff" has the
>> potential to cause all kinds of good things to happen faster than the
>> time taken to organise a conference call to discuss requirements
>> gathering for a "production" system.
>
>
> +1000. And that applies equally to the backend. I have yet to meet a
> fancy, integrated, database-driven configuration management system that can
> beat a bunch of flat files and a few perl scripts. Hackability of a system
> can be a definite virtue here.
> -e
>
>
