Great Circle Associates Network-Automation
(April 2005)
 

Indexed By Date: [Previous] [Next] Indexed By Thread: [Previous] [Next]

Subject: Re: available network automation tools
From: Daniel Hagerty <hag @ linnaean . org>
Date: Wed, 13 Apr 2005 00:29:56 -0400
To: Andrew Fort <andrew . fort @ gmail . com>
Cc: Georg Magschok <gio @ epygi . de>, network-automation @ greatcircle . com
In-reply-to: <7654d9d05041218025152a9e5@mail.gmail.com>
References: <p06210220be80b9bcf8de@66.92.48.19><002101c53f38$d186d480$1500140a@EPYGI.DE><7654d9d05041218025152a9e5@mail.gmail.com>
Reply-to: Daniel Hagerty <hag @ linnaean . org>

 > A common point I've noticed in recent replies to this thread is "yeah
 > so maybe we don't need to store/manage every last minute detail
 > centrally.  But, we need to know enough to _configure the network_".
 > And that's the important point.  We have to be able to configure it

    One of the evil details that shows up in this part, at least for
more generalized system administration, is that what is and is not
minute detail changes from day to day.

    As I said on lssconf at one point:

Today, me having to explictly model every chunk of my syslog.conf
would be massive overspecification.  Tommorow, I have to explictly
model every chunk of my syslog.conf so that I can prove that I'm
meeting my logging conformance requirements to my auditors.


Follow-Ups:
References:
Indexed By Date Previous: Re: available network automation tools
From: Andrew Fort <andrew.fort@gmail.com>
Next: Re: available network automation tools
From: Andrew Fort <andrew.fort@gmail.com>
Indexed By Thread Previous: Re: available network automation tools
From: Andrew Fort <andrew.fort@gmail.com>
Next: Re: available network automation tools
From: Andrew Fort <andrew.fort@gmail.com>

Google
 
Search Internet Search www.greatcircle.com