Re: [Rtg-yang-coord] IETF draft -> YANG module extraction -> compilation

Benoit Claise <bclaise@cisco.com> Thu, 26 March 2015 20:00 UTC

Return-Path: <bclaise@cisco.com>
X-Original-To: rtg-yang-coord@ietfa.amsl.com
Delivered-To: rtg-yang-coord@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EF8ED1B2E2B for <rtg-yang-coord@ietfa.amsl.com>; Thu, 26 Mar 2015 13:00:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.51
X-Spam-Level:
X-Spam-Status: No, score=-14.51 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4-Ei78frNoQy for <rtg-yang-coord@ietfa.amsl.com>; Thu, 26 Mar 2015 13:00:56 -0700 (PDT)
Received: from rcdn-iport-3.cisco.com (rcdn-iport-3.cisco.com [173.37.86.74]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 770D31B2E28 for <rtg-yang-coord@ietf.org>; Thu, 26 Mar 2015 13:00:54 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=10835; q=dns/txt; s=iport; t=1427400054; x=1428609654; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to; bh=fLBwLWcTKFwz1o9RYTS9geMASIguiPz/5abbtvUlcsU=; b=DugJTNbeJPA69SXYJOFAZ10EkYuqrM4mfOUZPcCm5SPZr9Jx0ZjLDmAK Ftb16sDRjnreJxWU/zxP2w6IeiDmwE4Jys59k00IdxWeF3ERKqkXdeqzF ABhqX97EOilPW0b4N8hurSbkUW25pXkK0M6eX4M6AE/mFMAjqi8sB8U+Q w=;
X-IronPort-AV: E=Sophos;i="5.11,474,1422921600"; d="scan'208,217";a="406968621"
Received: from rcdn-core-7.cisco.com ([173.37.93.143]) by rcdn-iport-3.cisco.com with ESMTP; 26 Mar 2015 20:00:54 +0000
Received: from [10.82.235.27] (rtp-vpn5-792.cisco.com [10.82.235.27]) by rcdn-core-7.cisco.com (8.14.5/8.14.5) with ESMTP id t2QK0r9L010966; Thu, 26 Mar 2015 20:00:53 GMT
Message-ID: <55146574.3020100@cisco.com>
Date: Thu, 26 Mar 2015 15:00:52 -0500
From: Benoit Claise <bclaise@cisco.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.5.0
MIME-Version: 1.0
To: Anees Shaikh <aashaikh@google.com>
References: <5514198F.8030006@cisco.com> <55142CE4.8070304@cisco.com> <CAJK7ZqJhf6ZVV4B_EBK4H7qOBuoDn9_kY5Ji4H6uTT7qmvgKZw@mail.gmail.com>
In-Reply-To: <CAJK7ZqJhf6ZVV4B_EBK4H7qOBuoDn9_kY5Ji4H6uTT7qmvgKZw@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------000904050100070802060009"
Archived-At: <http://mailarchive.ietf.org/arch/msg/rtg-yang-coord/-9jcQdLLi7T1OgkWkm251hONTuQ>
Cc: "Rtg-yang-coord@ietf.org" <rtg-yang-coord@ietf.org>, "Jan Medved \(jmedved\)" <jmedved@cisco.com>
Subject: Re: [Rtg-yang-coord] IETF draft -> YANG module extraction -> compilation
X-BeenThere: rtg-yang-coord@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "\"List to discuss coordination between the Routing related YANG models\"" <rtg-yang-coord.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtg-yang-coord>, <mailto:rtg-yang-coord-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rtg-yang-coord/>
List-Post: <mailto:rtg-yang-coord@ietf.org>
List-Help: <mailto:rtg-yang-coord-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtg-yang-coord>, <mailto:rtg-yang-coord-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 26 Mar 2015 20:00:59 -0000

Hi Anees,
> Benoit, Jan, thanks for putting this together -- should be useful to 
> improve submitted YANG modules.
>
> Regarding room for improvement, before making this part of idnits, 
> etc.  I'd suggest (i) we don't want to fail modules that don't use an 
> IETF namespace until the corresponding draft becomes a WG draft, gets 
> renamed, etc., and
wrt to "fail modules", there are two types of failures: pyang and idnits
pyang: should report this as a failure
idnits: I don't believe that a pyang error should prevent someone from 
posting a draft.

Expressed differently, I don't feel like evaluating every single pyang 
error, and arbitrarily selecting which ones should allow/prevent posting.

> (ii) need a way to follow dependencies on modules in other namespaces.
Right. As far as I know, there are not even tools to follow dependencies 
within the same namespace. Would be happy to stand corrected...

>
> Per Carl's suggestion, I will try to copy these into issues in the 
> github when the code is posted.
Great. thanks

Benoit
>
> thanks again.
> -- Anees
>
> On Thu, Mar 26, 2015 at 10:59 AM, Benoit Claise <bclaise@cisco.com 
> <mailto:bclaise@cisco.com>> wrote:
>
>     On 26/03/2015 09:37, Benoit Claise wrote:
>>     Dear all,
>>
>>     Part of the IETF 92 hackathon, Jan Medved and I developed a tool
>>     for YANG modules extraction and compilation.
>>     The outcome is right now on my private web site at
>>     http://www.claise.be/IETFYANGPageCompilation.html, but you should
>>     really bookmark
>>     http://www.ietf.org/iesg/directorate/yang-model-coordination-group.html
>>     and follow the WIKI link.
>>
>>     Please make sure your YANG modules compile. Btw, don't forget the
>>     pyang --ietf option.
>>     Some numbers:
>>
>>       * Number of YANG models in IETF drafts that passed compilation:
>>         28/113
>>       * Number of all YANG models in IETF drafts (good, bad, example,
>>         badly formatted, etc. ): 189
>>
>     Improved code + just run with the latest set of drafts
>
>       * Number of YANG models in IETF drafts that passed compilation:
>         28/118
>       * Number of all YANG models in IETF drafts (good, bad, example,
>         badly formatted, etc. ): 212
>
>     Regards, Benoit
>
>>     There is room for improvement.
>>     Some of the draft authors have been notified about specific
>>     mistakes in their module
>>
>>     Next steps:
>>         - include this tool part of the idnits
>>         - cron job to create this page
>>         - post the code (currently polishing it)
>>         - produce a similar page for opendaylight
>>
>>     Regards, Benoit
>>
>>
>>     _______________________________________________
>>     Rtg-yang-coord mailing list
>>     Rtg-yang-coord@ietf.org  <mailto:Rtg-yang-coord@ietf.org>
>>     https://www.ietf.org/mailman/listinfo/rtg-yang-coord
>
>
>     _______________________________________________
>     Rtg-yang-coord mailing list
>     Rtg-yang-coord@ietf.org <mailto:Rtg-yang-coord@ietf.org>
>     https://www.ietf.org/mailman/listinfo/rtg-yang-coord
>
>
>
>
> _______________________________________________
> Rtg-yang-coord mailing list
> Rtg-yang-coord@ietf.org
> https://www.ietf.org/mailman/listinfo/rtg-yang-coord