[Infrastructures] using IA methodologies to build network element configuration

[Kysh]

On Tue, 29 Mar 2005, Adam S. Moskowitz wrote:

> Aaron Glenn <aaron.glenn@gmail.com> wrote:
> > Perhaps Joel just wants to run CVS/SVN/(your favorite version control
> > software here) *natively* on his network elements?
> 
> And for this we should run a general-purpose O/S on a router? I think
> not.
> 
> > I find vendor c's handling of configuration files abysmal
> 
> I claim that it's not the router's job to "handle" configuration
> *files*. And, if you think about it, the Unix kernel does not, in and of
> itself, handle configuration *files* per se. So why should IOS -- which
> isn't, or at least shouldn't, be much more than a kernel -- handle them?
> 
> I claim you run CVS et al. on a general-purpose computer (running *BSD
> or Linux or even WinXP if that's your cup of tea) and then transfer a
> *configuration* to the router in whatever native form is necessary.
> File? That's just a convenient way to store a configuration.

<AOL> Me too </AOL>;

Seriously, though, I'm with Adam M. I don't want network devices to be
any more intelligent or capable than the bare necessity to do their job
and be maintained as appropriate*. 
Web administration console? Reasonable. Apache+tomcat+a billion packages
so that you can show a dial in the corner of the page? No 'way'. 'Full
featured multi-tasking OS on a router'?? 

Not on my router! :> 

Same goes for any production boxes I run. Bare necessities and that's
it.

'Nifty' has no place in the datacenter. 

-Kysh
* As appropriate means, obviously, that in the case of routers,
  switches, firewalls, etc that the configuration is maintained on a
  central repository, rather than 'intelligently maintained' on the box
  itself-- But wait, why does this sound familiar? ;> 
-- 
This is my signature. There are many like it, but this one is mine.