4 title: YES-API-PROVIDER modules of RestConf (RFC8040)
7 url: http://www.apache.org/licenses/LICENSE-2.0.html
9 - url: https://yes-api-provider.orbit-lab.org/
11 /restconf/yang-based-event-stream:event-history:
13 description: 'The root container of an event log. '
14 summary: GET - YES-API-PROVIDER - yang-based-event-stream - event-history
16 - mounted YES-API-PROVIDER yang-based-event-stream
22 $ref: '#/components/schemas/yang-based-event-stream_event-history_TOP'
29 Base identity for the event domain. A unique identification of the
32 This identity is abstract and MUST NOT be used for domains.
34 - o1-notify-pnf-registration
39 Base identity for the event type. A unique identification of the
42 This identity is abstract and MUST NOT be used for event types.
47 - guest-operating-system
48 - physical-network-function
49 - host-operating-system
51 yang-based-event-stream_event-history_event_header:
54 $ref: '#/components/schemas/domain-id'
56 description: The event key that is unique to the event source.
62 A unique event name. A names space ensures the uniqueness
63 between the data-models.
64 default: Some event-name
67 $ref: '#/components/schemas/event-type-id'
69 description: The latest time aka epoch time associated with the event from any component.
72 default: '1970-01-01T00:00:00.000Z'
76 The network function component type, aligned with vfc naming
79 TODO: Add a reference to the VFC naming standard.
85 The network function type, aligned with network-function (NF)
88 TODO: Add a reference to the NF naming standard.
93 description: Network function vendor IANA private enterprise number.
97 description: Network function vendor name according to IANA Private Enterprise Numbers
100 description: The event priority to control the processing of the event.
109 description: The entity reporting the event, for example an OAM VM.
113 reporting-entity-name:
115 The name of the entity reporting the event, for example, an EMS
116 name; may be the same as 'source-name'.
121 description: Ordering of events communicated by an event source instance or 0, if not needed.
125 description: UUID identifying the entity experiencing the event issue.
130 description: The name of the entity experiencing the event issue,
134 The earliest time aka epoch time associated with the event from
138 default: '1970-01-01T00:00:00.000Z'
146 - reporting-entity-name
151 title: yang-based-event-stream_event-history_event_header
153 This contains all the parameters which are common to all
155 o1-notify-pnf-registration:
159 The name of the object class describing a PNF in the context of
163 default: managed-function
166 description: Reference to the object representing the PNF.
168 notification-identifier:
169 description: An notification identifier of this event as defined in ITU-T Rec. X.733.
172 $ref: '#/components/schemas/domain-id'
175 The earliest time aka epoch time associated with the event from
179 default: '1970-01-01T00:00:00.000Z'
181 system-distinguished-name:
182 description: Distinguished Name of the management service provider of the notification
183 default: Some system-distinguished-name
185 o1-specification-version:
186 description: The version of the O1 Specification defining the format of this PNF registration notification
192 description: The serial number of the network function.
197 description: Network function vendor IANA private enterprise number.
201 description: Network function vendor name according to IANA Private Enterprise Numbers
205 The m-plane fully qualified domain name (host) or IP address to
206 be used by the manager to contact the PNF.
209 description: The port number the PNF listens for OAM commands..
214 description: The MAC address of OAM interface of the network function in Colon-Hexadecimal notation.
219 description: The general type of hardware.
224 description: Name for the network function
229 description: Version of the network function from the vendor.
234 description: The active software version running on the network function.
239 description: The reason the network function restarted.
244 description: Manufacture date of the network function.
247 default: '1970-01-01T00:00:00.000Z'
250 description: Date when the field operation stuff way on-side.
253 default: '1970-01-01T00:00:00.000Z'
256 description: Defines the security protocol for NETCONF
263 description: The username for the connection.
268 description: The user's password for the SSH session.
274 BASE-64 encoded public key which is used by the network-function
275 during the connection.
279 Key identifier inside the NETCONF server's keystore.
280 It is used during two-way TLS authentication.
282 reconnect-on-changed-schema:
284 Defines if the NETCONF client should reconnect to the network
285 function, if new YANG capabilities are exposed.
290 Defines the NETCONF client timeout to indicate that the connection
295 max-connection-attempts:
297 Defines the number of attempts by the NETCONF client to connect
298 to the NETCONF server, before the automated connection function, by
299 the NETCONF client is switched off. The value 0 means 'infinity'.
303 between-attempts-timeout:
305 Defines the first delay time in milliseconds to try a new reconnect
306 by the NETCONF client. For the next attempts the values is
307 multiplied with the 'sleep-factor'.
312 description: Defines the factor to increase the reconnect attempt.
317 Defines the time in seconds between two 'empty' NETCONF request to
318 check if the NETCONF server is functional or can be reached. The
319 value 0 turns of such function.
326 - notification-identifier
329 - system-distinguished-name
330 - o1-specification-version
334 title: o1-notify-pnf-registration
336 A single object for specific parameters, used for the registration of
337 physical network functions (PNF).
338 yang-based-event-stream_event-history_event:
341 $ref: '#/components/schemas/yang-based-event-stream_event-history_event_header'
342 o1-notify-pnf-registration:
343 $ref: '#/components/schemas/o1-notify-pnf-registration'
345 title: yang-based-event-stream_event-history_event
346 description: This contains the set of asynchronous messages.
347 yang-based-event-stream_event-history:
349 maximum-number-of-entries:
351 The maximum number of item in the event list supported by
359 $ref: '#/components/schemas/yang-based-event-stream_event-history_event'
360 description: This contains the set of asynchronous messages.
362 title: yang-based-event-stream_event-history
363 description: 'The root container of an event log. '
364 yang-based-event-stream_event-history_TOP:
368 $ref: '#/components/schemas/yang-based-event-stream_event-history'
369 title: yang-based-event-stream_event-history_TOP