Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cronjob - daily update of yang files. #1488

Merged
merged 1 commit into from
Oct 12, 2023
Merged

Cronjob - daily update of yang files. #1488

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
459 changes: 455 additions & 4 deletions ...-YANG-modules/ietf-bgp-ls@2023-02-27.yang → ...-YANG-modules/ietf-bgp-ls@2023-10-10.yang
View file
Open in desktop

Large diffs are not rendered by default.

5 changes: 2 additions & 3 deletions ...ANG-modules/ietf-bgp-lsdb@2023-02-27.yang → ...ANG-modules/ietf-bgp-lsdb@2023-10-10.yang
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -48,12 +48,13 @@ module ietf-bgp-lsdb {
described in BCP 14 (RFC 2119) (RFC 8174) when, and only when,
they appear in all capitals, as shown here.";

revision 2023-02-27 {
revision 2023-10-10 {
description
"Initial Version";
reference
"RFC XXXX, BGP Model for Link State Distribution.";
}

// Typedefs
typedef lsdb-proto-id-type {
type enumeration {
Expand Down Expand Up @@ -350,7 +351,6 @@ module ietf-bgp-lsdb {
type uint16;
description "Id of the topology object belongs to.";
}

leaf pdu-id {
type uint32;
description
Expand Down Expand Up @@ -447,7 +447,6 @@ module ietf-bgp-lsdb {
container nodes {
description
"List of node objects for a given database.";

list node {
key "handle";

Expand Down
26 changes: 22 additions & 4 deletions experimental/ietf-extracted-YANG-modules/ietf-netconf-txid@2023-03-01.yang
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -61,13 +61,31 @@ module ietf-netconf-txid {
"RFC XXXX: Xxxxxxxxx";
}

feature txid-last-modified {
feature last-modified {
description "Servers implementing this module MUST support the
etag txid mechanism. Servers MAY also support the
last-modified txid mechanism. Support is shown by announcing
this feature.";
}

extension versioned-node {
description "This statement is used by servers to declare that a
the server is maintaining a Txid for the YANG node with this
statement. Which YANG nodes are versioned nodes may be useful
information for clients (especially during development).

Servers are not required to use this statement to declare which
nodes are versioned nodes.

Example of use:

container interfaces {
ietf-netconf-txid:versioned-node;
...
}
";
}

typedef etag-t {
type string {
pattern ".* .*" {
Expand Down Expand Up @@ -122,7 +140,7 @@ module ietf-netconf-txid {
changed.";
}
leaf with-last-modified {
if-feature txid-last-modified;
if-feature last-modified;
type boolean;
description
"Indicates whether the client requests the server to include
Expand All @@ -141,7 +159,7 @@ module ietf-netconf-txid {
"Indicates server's txid value for a YANG node.";
}
leaf last-modified-value {
if-feature txid-last-modified;
if-feature last-modified;
type last-modified-t;
description
"Indicates server's txid value for a YANG node.";
Expand Down Expand Up @@ -195,7 +213,7 @@ module ietf-netconf-txid {
attribute for one mismatching element.";
}
leaf mismatch-last-modified-value {
if-feature txid-last-modified;
if-feature last-modified;
type last-modified-t;
description
"Indicates server's txid value of the last-modified
Expand Down
158 changes: 158 additions & 0 deletions experimental/ietf-extracted-YANG-modules/ietf-tvr-node@2023-10-11.yang
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,158 @@
module ietf-tvr-node {
yang-version 1.1;
namespace "urn:ietf:params:xml:ns:yang:ietf-tvr-node";
prefix tvr-node;

import ietf-yang-types {
prefix "yang";
}

import ietf-tvr-schedule {
prefix "tvr-schd";
}

organization
"IETF TVR - Time Variant Routing Working Group";
contact
"WG Web: <http://datatracker.ietf.org/wg/tvr>
WG List: <mailto:tvr@ietf.org>

Author: Yingzhen Qu
<mailto:yingzhen.ietf@gmail.com>
Author: Acee Lindem
<mailto:acee.ietf@gmail.com>
Author: Marc Blanchet
<mailto:marc.blanchet@viagenie.ca>
Author: Eric Kinzie
<mailto:ekinzie@labn.net>
Author: Don Fedyk
<mailto:dfedyk@labn.net>";

description
"The YANG module defines a schedule for changing
attributes of a single node.

This YANG model conforms to the Network Management
Datastore Architecture (NMDA) as described in RFC 8342.

Copyright (c) 2023 IETF Trust and the persons identified as
authors of the code. All rights reserved.

Redistribution and use in source and binary forms, with or
without modification, is permitted pursuant to, and subject to
the license terms contained in, the Revised BSD License set
forth in Section 4.c of the IETF Trust's Legal Provisions
Relating to IETF Documents
(https://trustee.ietf.org/license-info).

This version of this YANG module is part of RFC XXXX
(https://www.rfc-editor.org/info/rfcXXXX); see the RFC itself
for full legal notices.

The key words 'MUST', 'MUST NOT', 'REQUIRED', 'SHALL', 'SHALL
NOT', 'SHOULD', 'SHOULD NOT', 'RECOMMENDED', 'NOT RECOMMENDED',
'MAY', and 'OPTIONAL' in this document are to be interpreted as
described in BCP 14 (RFC 2119) (RFC 8174) when, and only when,
they appear in all capitals, as shown here.";
reference
"RFC XXXX: YANG Data Model for Scheduled Attributes";

revision 2023-10-11 {
description
"Initial Version";
reference
"RFC XXXX: YANG Data Model for Scheduled Attributes.";
}

container node-schedule {
description
"This container defined time variant attributes
for node's schedule.";

leaf router-id {
type yang:dotted-quad;
description
"A 32-bit number used to identify a router.";
}

list power-schedule {
key "start-date-time";
description
"Power schedule for the node. The node's power is
represented by a boolean value with 'true' indicating
the node is powered on and 'false' indicating the node
is powered off.";
uses tvr-schd:schedule {
augment value-default {
description
"Augment the default power state.";
leaf default-power {
type boolean;
default false;
description
"This indicates the default node power when for
time periods when no interval is defined. If
unspecified, the node is powered down by default.";
}
}
augment base-schedule/intervals/value {
description
"Augmment the scheduled power state.";
leaf power {
type boolean;
description
"Indicates whether the node is powered on.";
}
}
}
}

container interface-schedule {
description
"Container for TVR node interface attributes.";

list interfaces {
key "name";
description
"List of interface with schedules.";
leaf name {
type string;
description
"Name of the interface.
If used with the ietf-interfaces module, the name should
match the name of the interface.";
}

list up-down-schedule {
key "start-date-time";
description
"Scheduled times that the interface is up. This is to
work with the leaf 'enabled' for the configured state
of the interface.";

uses tvr-schd:schedule {
augment value-default {
description
"Augment default interface state.";
leaf default-available {
type boolean;
default false;
description
"By default, the link is not available.";
}
}
augment base-schedule/intervals/value {
description
"Augment scheduled interface state.";
leaf availble {
type boolean;
description
"Link availability.";
}
}
}
}
}
}
}
}
Loading
Loading