1 module yes-pnf-registration {
3 namespace "urn:opnfv:params:xml:ns:yang:yes-pnf-registration";
6 import yang-based-event-stream {
9 "wiki.opnfv.org/display/ves/VES+goes+YES";
14 "wiki.opnfv.org/display/ves/VES+goes+YES";
16 import ietf-inet-types {
19 "RFC 6991: YANG data types for Internet addresses and related
22 import ietf-yang-types {
25 "RFC 6991: Common YANG Data Types.";
29 "Open Platform for NFV (OPNFV) - Virtual Event Streaming (VES) project";
31 "wiki.opnfv.org/display/ves";
33 "This module is inspired by VES 7.1.1 but uses YANG concepts and types to
34 describe the exchanged data format.
35 The module yes-pnf-registration is only required, if the network function
36 does not support NETCONF CALL HOME but RESTCONF asynchronous messages.
38 Copyright 2020 highstreet technologies GmbH and others.
40 Licensed under the Apache License, Version 2.0 (the 'License');
41 you may not use this file except in compliance with the License.
42 You may obtain a copy of the License at
44 http://www.apache.org/licenses/LICENSE-2.0
46 Unless required by applicable law or agreed to in writing, software
47 distributed under the License is distributed on an 'AS IS' BASIS,
48 WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
49 See the License for the specific language governing permissions and
50 limitations under the License.";
56 "ONAP SDN-R: wiki.onap.org/display/DW/SDN-R
57 VES: wiki.opnfv.org/display/ves/VES+Home
58 docs.onap.org/en/frankfurt/submodules/dcaegen2.git/docs/sections/services/ves-http
59 YES: wiki.opnfv.org/display/ves/VES+goes+YES";
65 identity pnf-registration {
68 "Indicates, that the event body contains pnf-registration asynchronous
75 grouping pnf-registration-grp {
76 // TODO align with ietf-hardware, ONAP AAI, ONF manufactured-thing
77 leaf last-service-date {
78 type yang:date-and-time;
80 "Date when the field operation stuff way on-side.";
83 type yang:mac-address;
85 "The MAC address of OAM interface of the network function.";
87 leaf manufacture-date {
88 type yang:date-and-time;
90 "Manufacture date of the network function.";
97 "Version of the network function from vendor.";
102 "The m-plane fully qualified domain name (host) or IP address to
103 be used by the manager to contact the PNF.";
106 type inet:port-number;
108 "The port number the PNF listens for OAM commands..";
115 "The serial number of the network function.";
117 leaf software-version {
122 "The active software version running on the network function.";
129 "The general type of hardware.";
131 leaf network-function-type {
136 "Vendor name for the network function";
143 "The company name of manufacturer.";
146 "An object class containing pnf-registration specific parameters.";
150 * Augmentation of YES
152 augment "/yes:event-history/yes:event" {
153 when "derived-from-or-self(/yes:event-history/yes:event/yes:header/yes:domain, 'ypr:pnf-registration')" {
155 "The event header must indicate 'pnf-registration'.";
157 if-feature yes:event-history;
158 container pnf-registration {
159 uses pnf-registration-grp;
161 "A single object for specific parameters, used for the registration of
162 physical network functions (PNF).";
165 "Adds to YES the specifics of pnf-registration notifications.";
168 augment "/yes:yang-based-event-stream/yes:event" {
169 when "derived-from-or-self(/yes:yang-based-event-stream/yes:event/yes:header/yes:domain, 'ypr:pnf-registration')" {
171 "The event header must indicate 'pnf-registration'.";
173 container pnf-registration {
174 uses pnf-registration-grp;
176 "A single object for specific parameters, used for the registration of
177 physical network functions (PNF).";
180 "Adds to YES the specifics of pnf-registration notifications.";