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 [email protected]
<https://www.yangcatalog.org/yang-search/[email protected]>
- Yang impact analysis for draft-ietf-netmod-rfc7223bis
<https://www.yangcatalog.org/yang-search/impact_analysis.php?modules[][email protected]&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 <[email protected]>
To: [email protected], [email protected], [email protected]
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 <[email protected]> 30 Oct 2017 04:30:27 -0700
The new version is available for installation through SVN checkout, with
'svn checkout https://svn.tools.ietf.org/svn/tools/ietfdb/tags/6.64.0'
For development, copy the new development version instead:
'svn copy https://svn.tools.ietf.org/svn/tools/ietfdb/tags/dev/6.64.1.dev0'
<YOURBRANCH>
Regards,
Henrik
(via the mkrelease script)
.
_______________________________________________
netmod mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/netmod
