Fwd: YANG module metada and impact analysis links in the datatracker (New datatracker release: v6.64.0)
Benoit Claise <bclaise@cisco.com> Sat, 11 November 2017 16:12 UTC
Return-Path: <bclaise@cisco.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 808A1124319 for <wgchairs@ietfa.amsl.com>; Sat, 11 Nov 2017 08:12:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.519
X-Spam-Level:
X-Spam-Status: No, score=-14.519 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, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
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 XcheQ_kM_m2A for <wgchairs@ietfa.amsl.com>; Sat, 11 Nov 2017 08:12:06 -0800 (PST)
Received: from alln-iport-5.cisco.com (alln-iport-5.cisco.com [173.37.142.92]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 65EDE124217 for <wgchairs@ietf.org>; Sat, 11 Nov 2017 08:12:06 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=26155; q=dns/txt; s=iport; t=1510416726; x=1511626326; h=subject:references:to:cc:from:message-id:date: mime-version:in-reply-to; bh=1ii9u7Z1ZFNiHhNc8ocA1B1/ui99Wph+nvaYc+RYeAU=; b=abC3RUhxHuPvk8pi6NvwbCo7u+y5/23EYTPaxZo0y2AiUTRaBsGXwTKX Da3DEDSHAS2yXWV2Oyw5TLRT1Km+qHNMI/YxSHoovi6UyneAbXSIOOgIz E/PtpYPWzkcW9qc0x5IO8XKyb9bz2TOYMQl5GNU7fTT3Ih+hOo8bE0oXa 8=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0D8BADZIAda/5NdJa1CEAodAQEFAQsBgzVkbiedSIF9llAQggEKHoFjgzoChEZAFwEBAQEBAQEBAWsohR4BAwMnRwIJEBwDAQIkC00CCAYNBgIBAYoeEDOsAjomimYBAQEBAQEBAQEBAQEBAQEBAQEBAQEdgzSCB4FVghILgkE1g0SBGwUBBwsBKxSFWAWMU4UVgRKGGokWh2uDaYkwgnSJCYdFjGiBSodygTkgATYZKUFvNCEIHRVJgmQJglAfGYFbNDYBAQEBh0sNGAeCFgEBAQ
X-IronPort-AV: E=Sophos; i="5.44,378,1505779200"; d="scan'208,217"; a="29565472"
Received: from rcdn-core-11.cisco.com ([173.37.93.147]) by alln-iport-5.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 11 Nov 2017 16:12:05 +0000
Received: from [10.24.18.179] ([10.24.18.179]) by rcdn-core-11.cisco.com (8.14.5/8.14.5) with ESMTP id vABGC3gF025814; Sat, 11 Nov 2017 16:12:04 GMT
Subject: Fwd: YANG module metada and impact analysis links in the datatracker (New datatracker release: v6.64.0)
References: <386c91c0-6d87-0b64-30e8-4a29edb220cc@cisco.com>
To: WG Chairs <wgchairs@ietf.org>
Cc: Henrik Levkowetz <henrik@levkowetz.com>
From: Benoit Claise <bclaise@cisco.com>
X-Forwarded-Message-Id: <386c91c0-6d87-0b64-30e8-4a29edb220cc@cisco.com>
Message-ID: <4d280f8c-b65c-a92a-5830-b76d0b650e2f@cisco.com>
Date: Sun, 12 Nov 2017 00:12:02 +0800
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.4.0
MIME-Version: 1.0
In-Reply-To: <386c91c0-6d87-0b64-30e8-4a29edb220cc@cisco.com>
Content-Type: multipart/alternative; boundary="------------B64F75D68F7D1BA086A90357"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/wgchairs/IWltfWaOr6J5wIBRqf68YAHZsJM>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/wgchairs/>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 11 Nov 2017 16:12:09 -0000
FYI. Regards, Benoit. -------- Forwarded Message -------- Subject: YANG module metada and impact analysis links in the datatracker (New datatracker release: v6.64.0) Date: Sun, 12 Nov 2017 00:11:23 +0800 From: Benoit Claise <bclaise@cisco.com> To: NETMOD Working Group <netmod@ietf.org> CC: Henrik Levkowetz <henrik@levkowetz.com> Dear all, Here are two useful URLs in the datatracker if you care about YANG modules. This was announced in Henrik's email "New datatracker release: v6.64.0", but let me stress this again. If you take for example this draft: draft-ietf-netmod-rfc7223bis The tracker, at https://datatracker.ietf.org/doc/draft-ietf-netmod-rfc7223bis/, provides two "additional URLs": - Yang catalog entry for ietf-interfaces@2017-08-17.yang <https://www.yangcatalog.org/yang-search/module_details.php?module=ietf-interfaces@2017-08-17.yang> - Yang impact analysis for draft-ietf-netmod-rfc7223bis <https://www.yangcatalog.org/yang-search/impact_analysis.php?modules[]=ietf-interfaces@2017-08-17.yang&recurse=0&rfcs=1&show_subm=1&show_dir=dependencies> The first entry provides a list of all metadata in the YANG module for the yangcatalog.org <https://datatracker.ietf.org/doc/draft-clacla-netmod-model-catalog/> | +--rw module* [name revision organization] | +--rw name yang:yang-identifier | +--rw revision union | +--rw organization string | +--rw ietf | | +--rw ietf-wg? string | +--rw namespace inet:uri | +--rw schema? inet:uri | +--rw generated-from? enumeration | +--rw maturity-level? enumeration | +--rw document-name? string | +--rw author-email? yc:email-address | +--rw reference? inet:uri | +--rw module-classification enumeration | +--rw compilation-status? enumeration | +--rw compilation-result? inet:uri | +--rw prefix? string | +--rw yang-version? enumeration | +--rw description? string | +--rw contact? string | +--rw module-type? enumeration | +--rw belongs-to? yang:yang-identifier | +--rw tree-type? enumeration | +--rw submodule* [name revision] | | +--rw name yang:yang-identifier | | +--rw revision union | | +--rw schema? inet:uri | +--rw dependencies* [name] | | +--rw name yang:yang-identifier | | +--rw revision? union | | +--rw schema? inet:uri | +--rw dependents* [name] | | +--rw name yang:yang-identifier | | +--rw revision? union | | +--rw schema? inet:uri | +--rw semantic-version? yc:semver | +--rw derived-semantic-version? yc:semver | +--rw implementations | +--rw implementation* [vendor platform software-version software-flavor] | +--rw vendor string | +--rw platform string | +--rw software-version string | +--rw software-flavor string | +--rw os-version? string | +--rw feature-set? string | +--rw os-type? string | +--rw feature* yang:yang-identifier | +--rw deviation* [name revision] | | +--rw name yang:yang-identifier | | +--rw revision union | +--rw conformance-type? enumeration +--rw vendors +--rw vendor* [name] +--rw name string +--rw platforms +--rw platform* [name] +--rw name string +--rw software-versions +--rw software-version* [name] +--rw name string +--rw software-flavors +--rw software-flavor* [name] +--rw name string +--rw protocols | +--rw protocol* [name] | +--rw name identityref | +--rw protocol-version* string | +--rw capabilities* string +--rw modules +--rw module* [name revision organization] +--rw name -> /catalog/modules/module/name +--rw revision -> /catalog/modules/module/revision +--rw organization -> /catalog/modules/module/organization +--rw os-version? string +--rw feature-set? string +--rw os-type? string +--rw feature* yang:yang-identifier +--rw deviation* [name revision] | +--rw name yang:yang-identifier | +--rw revision union +--rw conformance-type? enumeration I advice you to review the leave definitions at YANG module for the yangcatalog.org <https://datatracker.ietf.org/doc/draft-clacla-netmod-model-catalog/>, to understand the use cases. The most useful leaves to start with are the validation-status and validation-report. The second entry provides the impact analysis. There are thee options: 1. dependents only: only show those modules that depend on the target module(s). use case: you want to see the impacted modules 2. dependencies only: only show those modules that are imported by the target module(s). use case: you want to see the bottleneck for standardization 3. both Enjoy. Regards, Benoit -------- Forwarded Message -------- Subject: New datatracker release: v6.64.0 Date: Wed, 01 Nov 2017 06:36:58 -0700 From: Henrik Levkowetz <henrik@levkowetz.com> To: codesprints@ietf.org, iesg@ietf.org, wgchairs@ietf.org Hi, This is an automatic notification about a new datatracker release, v6.64.0, generated when running the mkrelease script. Release notes: ietfdb (6.64.0) ietf; urgency=medium **Yang resource links on yang draft pages** Drafts containing yang modules now get links pointing to the yang impact analysis, and to module metadata for each module. Support has been added for ad-hoc trac instances, permitting automatic maintenance of role-based admin rights also for other trac instances than the WG, RG, and directorate wikis. The draft submission automation API description is now referenced from the draft submission upload page. 'Additional URLs' for drafts are now sorted, rather than presented in random order. Links pointing from draft review pages to mailing lists, for the full review text, are now validated in order to avoid presenting links to unavailable resources. An issue with parameter expansion in a nomcom template has been fixed, as have various other issues. Details from the commit log: * Tweaked a page cache time to make newly uploaded session agendas visible with less delay. * Added a guard against iterating over None in stats.views.document_stats() * Added draft URLs pointing to Yang resources (impact analysis and model metadata) for submissions containing Yang modules. * Changed the submission checkers to return more information in the checker details json blob; in particular added information about individual extracted code modules associated with a draft. This is used by the yang valididty checker to return a list of extracted yang modules. * Changed the SubmissionCheck.time field to use a default now value, instead of auto_now, to permit migrations without changing the timestamps. * Added some more debugging output for occasional author extraction failures during test. See also [14226]. * Added support for ad-hoc trac instances, with arbitrary names and filesystem paths, but still bound to a particular group's roles for management of trac admin rights. * Display document urls in alphabetical order * Permit document urls to be up to 512 bytes, rather than the default 200 * New settings for adhoc wikis and yang document urls * Added a mention of the submission automation API on the submission upload page. * Added cleaning of review_url from the review completion form, to make sure it's retrievable. * Added some debugging code to help identify random test failures * Added a new field Meeting.days to capture the length of a meeting. This is necessary now that we have previous meetings officially starting Sunday, lasting to Friday, and future meetings starting Saturday, Lasting to Friday. We use Meeting.days to calculate Meeting.end_date(). Meeting.get_ietf_monday() and two cut_off() methods have also been updated to be instance methods instead of class methods, and to not assume that a meeting starts on Sunday. * Updated coverage data * Expanded one of the nomcom tests a bit, and updated a fixture to match the current /nomcom/default/email/feedback_receipt.txt template. * Don't blow up when checking if the logged-in user is a document author, if the user don't have a person record. -- Henrik Levkowetz<henrik@levkowetz.com> 30 Oct 2017 04:30:27 -0700 The new version is available for installation through SVN checkout, with 'svn checkouthttps://svn.tools.ietf.org/svn/tools/ietfdb/tags/6.64.0' For development, copy the new development version instead: 'svn copyhttps://svn.tools.ietf.org/svn/tools/ietfdb/tags/dev/6.64.1.dev0' <YOURBRANCH> Regards, Henrik (via the mkrelease script) .
- Fwd: YANG module metada and impact analysis links… Benoit Claise