-
Notifications
You must be signed in to change notification settings - Fork 1
/
yang-catalog.yang
858 lines (830 loc) · 30.8 KB
/
yang-catalog.yang
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
module yang-catalog {
yang-version 1.1;
namespace "urn:ietf:params:xml:ns:yang:yang-catalog";
prefix yc;
import ietf-yang-types {
prefix yang;
}
import ietf-yang-library {
prefix yanglib;
}
import ietf-inet-types {
prefix inet;
}
organization
"yangcatalog.org";
contact
"Benoit Claise <bclaise@cisco.com>
Joe Clarke <jclarke@cisco.com>";
description
"This module contains metadata pertinent to each YANG module, as
well as a list of vendor implementations for each module. The
structure is laid out in such a way as to make it possible to
locate metadata and vendor implementation on a per-module basis
as well as obtain a list of available modules for a given
vendor's platform and specific software release.";
revision 2018-04-03 {
description
"Bump the YANG version number to 1.1 for the deref XPath
function.";
reference "YANG Catalog <https://yangcatalog.org>";
}
revision 2018-01-23 {
description
"* Add leafs to track expire modules
* Correct a bug with leafref dereferencing";
reference "YANG Catalog <https://yangcatalog.org>";
}
revision 2017-09-26 {
description
"* Add leafs for tracking dependencies and dependents
* Simplify the generated-from enumerated values
* Refine the type for compilation-result to be an inet:uri
* Add leafs for semantic versioning";
reference "YANG Catalog <https://yangcatalog.org>";
}
revision 2017-08-18 {
description
"* Reorder organization to be with the other module keys
* Add a belongs-to leaf to track a submodule's parent";
reference "YANG Catalog <https://yangcatalog.org>";
}
revision 2017-07-28 {
description
"* Revert config false nodes as we need to be able to set these via <edit-config>
* Make conformance-type optional as not all vendors implement yang-library
* Re-add the path typedef";
reference "YANG Catalog <https://yangcatalog.org>";
}
revision 2017-07-26 {
description
"A number of improvements based on YANG Doctor review:
* Remove references to 'server' in leafs describing YANG data
* Fold the augmentation module leafs directly under /catalog/modules/module
* Use identities for protocols instead of an emumeration
* Make some extractable fields 'config false'
* Fix various types
* Normalize enums to be lowercase
* Add a leaf for module-classification
* Change yang-version to be an enum
* Add module conformance, deviation and feature leafs under the implementation branches";
reference "YANG Catalog <https://yangcatalog.org>";
}
revision 2017-07-14 {
description
"Modularize some of the leafs and create typedefs so they
can be shared between the API input modules.";
reference "YANG Catalog <https://yangcatalog.org>";
}
revision 2017-07-03 {
description
"Initial revision.";
reference
"
YANG Catalog <https://yangcatalog.org>";
}
/*
* Identities
*/
identity protocol {
description
"Abstract base identity for a YANG-based protocol.";
}
identity netconf {
base protocol;
description
"Protocol identity for NETCONF as described in RFC 6241.";
}
identity restconf {
base protocol;
description
"Protocol identity for RESTCONF as described in RFC 8040.";
}
typedef email-address {
type string {
pattern "[a-zA-Z0-9.!#$%&'*+/=?^_`{|}~-]+@[a-zA-Z0-9-]+([.][a-zA-Z0-9-]+)*";
}
description
"This type represents a string with an email address.";
}
/*
* Typedefs
*/
typedef path {
type string {
pattern '([A-Za-z]:|[\w-]+(\.[\w-]+)*)?(([/\\][\w@.-]+)+)';
}
description
"This type represents a string with path to the file.";
}
typedef semver {
type string {
pattern '[0-9]+\.[0-9]+\.[0-9]+';
}
description
"A semantic version in the format of x.y.z, where:
x = the major version number
y = the minor version number
z = the patch version number
Changes to the major version number denote backwards-incompatible
changes between two revisions of the same module.
Changes to the minor version number indicate there have been new
backwards-compatible features introduced in the later version of
a module.
Changes to the patch version indicate bug fixes between two
versions of a module.";
reference "Semantic Versioning 2.0.0 <http://semver.org/>";
}
container catalog {
description
"Root container of yang-catalog holding two main branches -
modules and vendors. The modules sub-tree contains all the modules in
the catalog and all of their metadata with their implementations.
The vendor sub-tree holds modules for specific vendors, platforms,
software-versions, and software-flavors. It contains reference to a
name and revision of the module in order to reference the module's full
set of metadata.";
container modules {
description
"Container holding the list of modules";
list module {
key "name revision organization";
description
"Each entry represents one revision of one module
for one organization.";
uses yang-lib-common-leafs;
leaf organization {
type string;
description
"This statement defines the party responsible for this
module. The argument is a string that is used to specify a textual
description of the organization(s) under whose auspices this module
was developed.";
}
uses organization-specific-metadata;
leaf namespace {
type inet:uri;
mandatory true;
description
"The XML namespace identifier for this module.";
}
uses yang-lib-schema-leaf;
uses catalog-module-metadata;
list submodule {
key "name revision";
description
"Each entry represents one submodule within the
parent module.";
uses yang-lib-common-leafs;
uses yang-lib-schema-leaf;
}
list dependencies {
key "name";
description
"Each entry represents one dependency.";
uses yang-lib-common-leafs;
uses yang-lib-schema-leaf;
}
list dependents {
key "name";
description
"Each entry represents one dependent.";
uses yang-lib-common-leafs;
uses yang-lib-schema-leaf;
}
leaf semantic-version {
type yc:semver;
description
"The formal semantic version of a module as provided by the module
itself. If the module does not provide a semantic version, this leaf
will not be specified.";
}
leaf derived-semantic-version {
type yc:semver;
description
"The semantic version of a module as compared to other revisions of
the same module. This value is computed algorithmically by ordering
all revisions of a given module and comparing them to look for backwards
incompatible changes.";
}
container implementations {
description
"Container holding lists of per-module implementation details.";
list implementation {
key "vendor platform software-version software-flavor";
description
"List of module implementations.";
leaf vendor {
type string;
description
"Organization that implements this module.";
}
leaf platform {
type string;
description
"Platform on which this module is implemented.";
}
leaf software-version {
type string;
description
"Name of the version of software. With respect to most network device appliances,
this will be the operating system version. But for other YANG module
implementation, this would be a version of appliance software. Ultimately,
this should correspond to a version string that will be recognizable by
the consumers of the platform.";
}
leaf software-flavor {
type string;
description
"A variation of a specific version where
YANG model support may be different. Depending on the vendor, this could
be a license, additional software component, or a feature set.";
}
uses shared-implementation-leafs;
uses yang-lib-implementation-leafs;
}
}
}
}
container vendors {
description
"Container holding lists of organizations that publish YANG modules.";
list vendor {
key "name";
description
"List of organizations publishing YANG modules.";
leaf name {
type string;
description
"Name of the maintaining organization -- the name should be
supplied in the official format used by the organization.
Standards Body examples:
IETF, IEEE, MEF, ONF, etc.
Commercial entity examples:
AT&T, Facebook, <Vendor>
Name of industry forum examples:
OpenConfig, OpenDaylight, ON.Lab";
}
container platforms {
description
"Container holding list of platforms.";
list platform {
key "name";
description
"List of platforms under specific vendor";
leaf name {
type string;
description
"Name of the platform";
}
container software-versions {
description
"Container holding list of versions of software versions.";
list software-version {
key "name";
description
"List of version of software versions under specific vendor, platform.";
leaf name {
type string;
description
"Name of the version of software. With respect to most network device appliances,
this will be the operating system version. But for other YANG module
implementation, this would be a version of appliance software. Ultimately,
this should correspond to a version string that will be recognizable by
the consumers of the platform.";
}
container software-flavors {
description
"Container holding list of software flavors.";
list software-flavor {
key "name";
description
"List of software flavors under specific vendor, platform, software-version.";
leaf name {
type string;
description
"A variation of a specific version where
YANG model support may be different. Depending on the vendor, this could
be a license, additional software component, or a feature set.";
}
container protocols {
description
"List of the protocols";
list protocol {
key "name";
description
"YANG-based protocol that is used on the device. New identities
are expected to be added to address other YANG-based protocols.";
leaf name {
type identityref {
base yc:protocol;
}
description
"Identity of the YANG-based protocol that is supported.";
}
leaf-list protocol-version {
type string;
description
"Version of the specific protocol.";
}
leaf-list capabilities {
type string;
description
"Listed name of capabilities that are
supported by the specific device.";
}
}
}
container modules {
description
"Container holding list of modules.";
list module {
key "name revision organization";
description
"List of references to YANG modules under specific vendor, platform, software-version,
software-flavor. Using these references, the complete set of metadata can be
retrieved for each module.";
leaf name {
type leafref {
path "/catalog/modules/module/name";
}
description
"Reference to a name of the module that is contained in specific vendor, platform,
software-version, software-flavor.";
}
leaf revision {
type leafref {
path "deref(../name)/../revision";
}
description
"Reference to a revision of the module that is contained in specific vendor,
platform, software-version, software-flavor.";
}
leaf organization {
type leafref {
path "deref(../revision)/../organization";
}
description
"Reference to the authoring organization of the module for the implemented
module.";
}
uses shared-implementation-leafs;
uses yang-lib-implementation-leafs;
}
}
}
}
}
}
}
}
}
}
}
grouping catalog-module-metadata {
uses shared-module-leafs;
leaf compilation-status {
type enumeration {
enum passed {
description
"All compilers were able to compile this YANG module without
any errors or warnings.";
}
enum passed-with-warnings {
description
"All compilers were able to compile this YANG module without
any errors, but at least one of them caught a warning.";
}
enum failed {
description
"At least one of compilers found an error while
compiling this YANG module.";
}
enum pending {
description
"The module was just added to the catalog and compilation testing is still
in progress.";
}
enum unknown {
description
"There is not sufficient information about compilation status. This Could
mean compilation crashed causing it not to complete fully.";
}
}
description
"Status of the module, whether it was possible to compile this YANG module or
there are still some errors/warnings.";
}
leaf compilation-result {
type inet:uri;
description
"Link to the result of the compilation explaining specifically what error or
warning occurred. This is not existing if compilation status is PASSED.";
}
leaf prefix {
type string;
description
"Statement of yang that is used to define the prefix associated with
the module and its namespace. The prefix statement's argument is
the prefix string that is used as a prefix to access a module. The
prefix string MAY be used to refer to definitions contained in the
module, e.g., if:ifName.";
}
leaf yang-version {
type enumeration {
enum 1.0 {
description
"YANG version 1.0 as defined in RFC 6020.";
}
enum 1.1 {
description
"YANG version 1.1 as defined in RFC 7950.";
}
}
description
"The optional yang-version statement specifies which version of the
YANG language was used in developing the module.";
}
leaf description {
type string;
description
"This statement takes as an argument a string that
contains a human-readable textual description of this definition.
The text is provided in a language (or languages) chosen by the
module developer; for the sake of interoperability, it is RECOMMENDED
to choose a language that is widely understood among the community of
network administrators who will use the module.";
}
leaf contact {
type string;
description
"This statement provides contact information for the module.
The argument is a string that is used to specify contact information
for the person or persons to whom technical queries concerning this
module should be sent, such as their name, postal address, telephone
number, and electronic mail address.";
}
leaf module-type {
type enumeration {
enum module {
description
"If YANG file contains module.";
}
enum submodule {
description
"If YANG file contains sub-module.";
}
}
description
"Whether a file contains a YANG module or sub-module.";
}
leaf belongs-to {
when "../module-type = 'submodule'" {
description
"Include the module's parent when it is a submodule.";
}
type yang:yang-identifier;
description
"Name of the module that includes this submodule.";
}
leaf tree-type {
type enumeration {
enum split {
description
"This module uses a split config/operational state layout.";
}
enum nmda-compatible {
description
"This module is compatible with the Network Management Datastores
Architecture (NMDA) and combines config and operational state nodes.";
}
enum transitional-extra {
description
"This module is derived as a '-state' module to allow for transitioning
to a full NMDA-compliant tree structure.";
}
enum openconfig {
description
"This module uses the Openconfig data element layout.";
}
enum unclassified {
description
"This module does not belong to any category or can't be determined.";
}
enum not-applicable {
description
"This module is not applicable. For example, because the YANG module only contains typedefs, groupings, or is a submodule";
}
}
description
"The type of data element tree used by the module as it relates to the
Network Management Datastores Architecture.";
reference "draft-dsdt-nmda-guidelines Guidelines for YANG Module Authors (NMDA)";
}
leaf yang-tree {
when "../module-type = 'module'";
type inet:uri;
description
"This leaf provides a URI that points to the ASCII tree format of the module in
draft-ietf-netmod-yang-tree-diagrams format.";
reference "See draft-ietf-netmod-yang-tree-diagrams.";
}
leaf expires {
type yang:date-and-time;
description
"Date and time of when this module expires (if it expires). This will typically be used for
modules that have not been fully ratified.";
}
leaf expired {
type union {
type boolean;
type enumeration {
enum not-applicable {
description
"This module is not and will not be expired.";
}
}
}
default "false";
description
"Whether or not this module has expired. If the current date is beyond the expires date, then expired
should be true.";
}
description
"Grouping of YANG module metadata that extends the common list defined in the YANG
Module Library (RFC 7895).";
}
grouping organization-specific-metadata {
container ietf {
when "../organization = 'ietf'" {
description
"Include this container specific metadata of the IETF.";
}
leaf ietf-wg {
type string;
description
"Working group that authored the document containing this module.";
}
description
"Include this container for the IETF-specific organization metadata.";
}
description
"Any organization that has some specific metadata of the yang module and want them add to the
yang-catalog, should augment this grouping. This grouping is for any metadata that can`t be used for
every yang module.";
}
grouping yang-lib-common-leafs {
leaf name {
type yang:yang-identifier;
description
"The YANG module or submodule name.";
}
leaf revision {
type union {
type yanglib:revision-identifier;
type string {
length "0";
}
}
description
"The YANG module or submodule revision date.
A zero-length string is used if no revision statement
is present in the YANG module or submodule.";
}
description
"The YANG module or submodule revision date.
A zero-length string is used if no revision statement
is present in the YANG module or submodule.";
reference "RFC7895 YANG Module Library : common-leafs grouping";
}
grouping yang-lib-schema-leaf {
leaf schema {
type inet:uri;
description
"Contains a URL that represents the YANG schema
resource for this module or submodule.
This leaf will only be present if there is a URL
available for retrieval of the schema for this entry.";
}
description
"These are a subset of leafs from the yang-library (RFC 7895) that provide some
extractable fields for catalog modules. The module-list grouping cannot be
used from yang-library as modules themselves cannot have conformance without
a server.";
reference "RFC7895 YANG Module Library : schema-leaf grouping";
}
grouping yang-lib-implementation-leafs {
leaf-list feature {
type yang:yang-identifier;
description
"List of YANG feature names from this module that are
supported by the server, regardless of whether they are
defined in the module or any included submodule.";
}
list deviation {
key "name revision";
description
"List of YANG deviation module names and revisions
used by this server to modify the conformance of
the module associated with this entry. Note that
the same module can be used for deviations for
multiple modules, so the same entry MAY appear
within multiple 'module' entries.
The deviation module MUST be present in the 'module'
list, with the same name and revision values.
The 'conformance-type' value will be 'implement' for
the deviation module.";
uses yang-lib-common-leafs;
}
leaf conformance-type {
type enumeration {
enum implement {
description
"Indicates that the server implements one or more
protocol-accessible objects defined in the YANG module
identified in this entry. This includes deviation
statements defined in the module.
For YANG version 1.1 modules, there is at most one
module entry with conformance type 'implement' for a
particular module name, since YANG 1.1 requires that,
at most, one revision of a module is implemented.
For YANG version 1 modules, there SHOULD NOT be more
than one module entry for a particular module name.";
}
enum import {
description
"Indicates that the server imports reusable definitions
from the specified revision of the module but does
not implement any protocol-accessible objects from
this revision.
Multiple module entries for the same module name MAY
exist. This can occur if multiple modules import the
same module but specify different revision dates in
the import statements.";
}
}
// Removing the mandatory true for now as not all vendors may have
// this information if they do not implement yang-library.
//mandatory true;
description
"Indicates the type of conformance the server is claiming
for the YANG module identified by this entry.";
}
description
"This is a set of leafs extracted from the yang-library that are
specific to server implementations.";
reference "RFC7895 YANG Module Library : module-list grouping";
}
grouping shared-implementation-leafs {
leaf os-version {
type string;
description
"Version of the operating system using this module. This is primarily useful if
the software implementing the module is an application that requires a specific
operating system.";
}
leaf feature-set {
type string;
description
"An optional feature of the software that is required in order to implement this
module. Some form of this must be incorporated in software-version or
software-flavor, but can be broken out here for additional clarity.";
}
leaf os-type {
type string;
description
"Type of the operating system using this module. This is primarily useful if
the software implementing the module is an application that requires a
specific operating system.";
}
description
"Grouping of non-key leafs to be used in the module and vendor sub-trees.";
}
grouping shared-module-leafs {
leaf generated-from {
type enumeration {
enum mib {
description
"Module generated from Structure of Management Information (SMI)
MIB per RFC6643.";
}
enum not-applicable {
description
"Module was not generated but it was authored manually.";
}
enum native {
description
"Module generated from platform internal,
proprietary structure, or code.";
}
}
default "not-applicable";
description
"This statement defines weather the module was generated or not.
Default value is set to not-applicable, which means that module
was created manualy and not generated.";
}
leaf maturity-level {
type enumeration {
enum ratified {
description
"Maturity of a module that is fully approved (e.g., a standard).";
}
enum adopted {
description
"Maturity of a module that is actively being developed by a organization towards ratification.";
}
enum initial {
description
"Maturity of a module that has been initially created, but has no official
organization-level status.";
}
enum not-applicable {
description
"The maturity level is not used for vendor-supplied models, and thus all vendor
modules will have a maturity of not-applicable";
}
}
description
"The current maturity of the module with respect to the body that created it.
This allows one to understand where the module is in its overall life cycle.";
}
leaf document-name {
type string;
description
"The name of the document from which the module was extracted or taken;
or that provides additional context about the module.";
}
leaf author-email {
type yc:email-address;
description
"Contact email of the author who is responsible for this module.";
}
leaf reference {
type inet:uri;
description
"A string that is used to specify a textual cross-reference to an external document, either
another module that defines related management information, or a document that provides
additional information relevant to this definition.";
}
leaf module-classification {
type enumeration {
enum network-service {
description
"Network Service YANG Module that describes the configuration, state
data, operations, and notifications of abstract representations of
services implemented on one or multiple network elements.";
}
enum network-element {
description
"Network Element YANG Module that describes the configuration, state
data, operations, and notifications of specific device-centric
technologies or features.";
}
enum unknown {
description
"In case that there is not sufficient information about how to classify the module.";
}
enum not-applicable {
description
"The YANG module abstraction type is neither a Network Service YANG Module
nor a Network Element YANG Module.";
}
}
mandatory true;
description
"The high-level classification of the given YANG module.";
reference "RFC8199 YANG Module Classification";
}
description
"These leafs are shared among the yang-catalog and its API.";
}
grouping online-source-file {
leaf owner {
type string;
mandatory true;
description
"Username or ID of the owner of the version control system repository.";
}
leaf repository {
type string;
mandatory true;
description
"The name of the repository.";
}
leaf path {
type yc:path;
mandatory true;
description
"Location within the repository of the module file.";
}
leaf branch {
type string;
description
"Revision control system branch or tag to use to find the module. If this is not
specified, the head of the repository is used.";
}
description
"Networked version control system location of the module file.";
}
}