Re: [YANG] new pyang errors

"Randy Presuhn" <randy_presuhn@mindspring.com> Wed, 23 January 2008 06:30 UTC

Return-path: <yang-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1JHZ80-0001Ru-Qz; Wed, 23 Jan 2008 01:30:28 -0500
Received: from yang by megatron.ietf.org with local (Exim 4.43) id 1JHZ7z-0001OJ-Rn for yang-confirm+ok@megatron.ietf.org; Wed, 23 Jan 2008 01:30:27 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1JHZ7z-0001LM-Dg for yang@ietf.org; Wed, 23 Jan 2008 01:30:27 -0500
Received: from elasmtp-dupuy.atl.sa.earthlink.net ([209.86.89.62]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1JHZ7z-00013d-3D for yang@ietf.org; Wed, 23 Jan 2008 01:30:27 -0500
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=mindspring.com; b=U/V1WYdTZwpold6OisfIX/5U29QJwaWWuTsemA7TQFX94Ih+m4PRcISLNxgUINLf; h=Received:Message-ID:From:To:References:Subject:Date:MIME-Version:Content-Type:Content-Transfer-Encoding:X-Priority:X-MSMail-Priority:X-Mailer:X-MimeOLE:X-ELNK-Trace:X-Originating-IP;
Received: from [69.3.145.174] (helo=oemcomputer) by elasmtp-dupuy.atl.sa.earthlink.net with esmtpa (Exim 4.67) (envelope-from <randy_presuhn@mindspring.com>) id 1JHZ7w-000456-HS for yang@ietf.org; Wed, 23 Jan 2008 01:30:24 -0500
Message-ID: <000c01c85d89$b114eb20$6801a8c0@oemcomputer>
From: "Randy Presuhn" <randy_presuhn@mindspring.com>
To: <yang@ietf.org>
References: <200801230559.m0N5xoXf020086@idle.juniper.net>
Subject: Re: [YANG] new pyang errors
Date: Tue, 22 Jan 2008 22:32:13 -0800
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1478
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1478
X-ELNK-Trace: 4488c18417c9426da92b9037bc8bcf44d4c20f6b8d69d8885d2a9c731cc89117070de0e6435fc93a1c4a7541bf1e31c8350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 69.3.145.174
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ea4ac80f790299f943f0a53be7e1a21a
X-BeenThere: yang@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: YANG modeling Language for NETCONF <yang.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/yang>, <mailto:yang-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/yang>
List-Post: <mailto:yang@ietf.org>
List-Help: <mailto:yang-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/yang>, <mailto:yang-request@ietf.org?subject=subscribe>
Errors-To: yang-bounces@ietf.org

Hi -

> From: "Phil Shafer" <phil@juniper.net>
> To: "Randy Presuhn" <randy_presuhn@mindspring.com>
> Cc: <yang@ietf.org>
> Sent: Tuesday, January 22, 2008 9:59 PM
> Subject: Re: [YANG] new pyang errors 
...
> >This is sufficient to configure a device, but it's not
> >configuration management.
> 
> I don't follow you here.  Please explain how the alternative
> interpretation of "mandatory" aids in configuration management.
> Is the "with-defaults" view key to a good solution?

For real configuration management, I count among the essentials:
   - the ability to bring a device to a known configuration state
   - the ability to determine exactly what a device's configuration
     state is
   - the ability to store and version this configuration information
   - the ability to create (provision) this information in advance
     of deployment
   - the ability to determine whether a device's actual configuration
     is the same as its desired configuration

The "with-defaults" view sounds like it would help, particulary
if a default-ed value isn't known a priori.

Randy



_______________________________________________
YANG mailing list
YANG@ietf.org
https://www1.ietf.org/mailman/listinfo/yang