[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Deja vu Again
Hi -
> Message-Id: <5.1.0.14.2.20020626155354.02ddf2b0@127.0.0.1>
> Date: Wed, 26 Jun 2002 15:56:30 -0700
> To: Rob Austein <sra+xmlconf@hactrn.net>, xmlconf@ops.ietf.org
> From: "David T. Perkins" <dperkins@dsperkins.com>
> Subject: Re: Deja vu Again
> In-Reply-To: <20020626143532.5E4721D14@thrintun.hactrn.net>
> References: <102509064401@mx05.gis.net>
> <5.1.0.14.2.20020625141310.032656a0@127.0.0.1>
> <5.1.0.14.2.20020625152723.041c33b0@127.0.0.1>
> <3D1982B9.2060801@cisco.com>
> <102509064401@mx05.gis.net>
> X-Spam-Status: No, hits=-2.4 required=5.0
> tests=IN_REP_TO,RCVD_IN_MULTIHOP_DSBL,X_RCVD_IN_UNCONFIRMED_DSBL,
> FUDGE_MULTIHOP_RELAY
> version=2.30
>
> HI,
>
> Say the below is the goal. What is to be "standardized"?
> Is there a standard for cisco config?
> Another standard for Juniper config?
> Yet another standard for each of vendors X, Y, and Z?
Just being able to suck it out of a box and spit it back into
the same or another box from the same vendor of the same type
is a big step forward.
Being able to break it up into identifiable bits and pieces
(e.g., per interface) would be another step forward.
To be able to intelligently display and edit this stuff with
a single tool would be another step forward.
To be able to use the same configuration data for like things
from different vendors would be another step forward. This can
mean simple replay, or data-driven templates like some operators
already use to plaster over vendor-specific differences.
There's a strong temptation to solve all of these at once, but
for some systems even the first step (dump config / load config
consistent (but possibly opaque) format) would be a big improvement.
> At 10:35 AM 6/26/2002 -0400, Rob Austein wrote:
> >At Wed, 26 Jun 2002 07:25:51 -0400, Jon Saperia wrote:
> >>
> >> On the other hand if one wanted to create an XML based flat file
> >> represenation of configuration information, regardless of how one got it
> >> to the box in the first place, or even if it is on the intended device,
> >> then that would be something that I think has some real value.
> >
> >Bingo! This was my understanding of the goal.
>
> Regards,
> /david t. perkins
...
------------------------------------------------------
Randy Presuhn BMC Software, Inc. 1-3141
randy_presuhn@bmc.com 2141 North First Street
Tel: +1 408 546-1006 San José, California 95131 USA
------------------------------------------------------
My opinions and BMC's are independent variables.
------------------------------------------------------
--
to unsubscribe send a message to xmlconf-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://ops.ietf.org/lists/xmlconf/>