Great Circle Associates Network-Automation
(April 2005)
 

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

Subject: Re: available network automation tools
From: Kirby Files <ksfiles @ gmail . com>
Date: Tue, 12 Apr 2005 11:06:49 -0400
To: Daniel Hagerty <hag @ linnaean . org>
Cc: Brent Chapman <Brent @ GreatCircle . COM>,Aaron Glenn <aaron . glenn @ gmail . com>,network-automation @ greatcircle . com
In-reply-to: <16987.57280.24606.129390@perdition.linnaean.org>
References: <Pine.GSO.4.33.0504081252130.26766-100000@darksun.binsh.com> <42573546.7050503@gmail.com> <18f60194050409174575ada600@mail.gmail.com> <42593FE4.7030901@gmail.com> <p0621021fbe80b5cb0c76@[66.92.48.19]> <425BD965.5020306@gmail.com> <16987.57280.24606.129390@perdition.linnaean.org>
User-agent: Mozilla Thunderbird 1.0.1 (X11/20050309)

Daniel Hagerty wrote on 04/12/2005 10:48 AM:
>  > Not only that, but also to define new types of devices and connections
>  > for the model itself.
> 
>     And in doing this, you start to approach the realm of the semantic
> problem.    The give away words in what you say are "new types".  What
> is a new type?

It is only a semantic problem if you're looking for a
one-size-fits-all universal taxonomy of networking. I believe in a
system with a small set of primitives with well-defined semantics,
which can be used to define a network model of anything from an X.25
financial system to a Tier1 backbone provider, to a heterogeneous mesh
network.

In my use of it here, a "type", or "element type" is a grouping of
elements that share common attributes, functions, and similar roles in
the network hierarchy. We have "types" that include "interface",
"card", "connection" (sub-typed by vlan, lsp, etc.), and even
higher-level constructs of "qos policy" and "edge router".

Each of these types has well-defined semantics (interfaces can be
connected to one or more interfaces via connnections; cards can be
interchanged in slots, etc.) that are true despite vendor or model
differences.

Thanks,
  --kirby files


Follow-Ups:
References:
Indexed By Date Previous: Re: available network automation tools
From: Daniel Hagerty <hag@linnaean.org>
Next: Re: available network automation tools
From: Daniel Hagerty <hag@linnaean.org>
Indexed By Thread Previous: Re: available network automation tools
From: Daniel Hagerty <hag@linnaean.org>
Next: Re: available network automation tools
From: Daniel Hagerty <hag@linnaean.org>

Google
 
Search Internet Search www.greatcircle.com