Hi!
> On 19 Mar 2019, at 18:08, Joe Clarke <jclarke@xxxxxxxxx> wrote:
>
> On 3/19/19 13:00, stefan vallin wrote:
>> Hi!
>>>
>>> Not exactly. I saw the life-cycle stuff -- and this edge trigger makes
>>> sense -- but I was asking that if the state is raise, will multiple
>>> notifications be sent for raise (or could multiple, periodic
>>> notifications be sent)? For example, while status is "raise" and
>>> without any other change, send a notification every five minutes.
>> Ah, ok.
>> Notifications are only sent for changes not repeated for same state
>
> Okay. Takes care of that line of thinking.
>
> In general, what about shelving for a time window? Is it envisioned the
> Management System would enable and disable shelving during maintenance
> windows?
>From a user perspective this make sense but it should be controlled by the manager/client.
Shelving is configuration, and configuration that "changes itself”
kind of breaks the NETCONF configuration pattern. No one reconfiguring
the system and still the config has changed.
>
>>>
>>> And now that you call out this text, "change severity" is listed twice :-).
>> Yes, intended :)
>> Could be minor, major, minor, major for example.
>> Imagine a set of thresholds
>
> Ah, it's a sample life-cycle, not a list.
Depends on what you mean :)
+--ro alarm* [resource alarm-type-id alarm-type-qualifier]
| +--ro is-cleared boolean
| +--ro perceived-severity severity
| +--ro alarm-text alarm-text
| +--ro status-change* [time] {alarm-history}?
| | +--ro time yang:date-and-time
| | +--ro perceived-severity severity-with-clear
| | +--ro alarm-text alarm-text
Each alarm has a leaf indicating the last severity level, alarm text and clearance status
And each alarm has a list of status changes.
So an alarm composite state could be:
+ alarm [disc-partition-foo, disc-utilization, “”]
+ is-cleared false
+ perceived-severity major
+ alarm-text “disc utilization high, major threshold”
+ status-change
+ time T3
+ perceived-severity major
+ alarm-text “disc utilization high, major threshold”
+ time T2
+ perceived-severity minor
+ alarm-text “disc utilization high, minor threshold”
+ time T4
+ perceived-severity major
+ alarm-text “disc utilization high, major threshold”
Note well, if the alarm gets cleared it will appear in the status list as well,
and it might be raised again
+ alarm [disc-partition-foo, disc-utilization, “”]
+ is-cleared false <<< (was True at T4)
+ perceived-severity major
+ alarm-text “disc utilization high, major threshold”
+ status-change
+ time T5
+ perceived-severity major
+ alarm-text “disc utilization high, major threshold”
+ time T4
+ perceived-severity cleared
+ alarm-text “disc utilization ok”
+ time T3
+ perceived-severity major
+ alarm-text “disc utilization high, major threshold”
+ time T2
+ perceived-severity minor
+ alarm-text “disc utilization high, minor threshold”
+ time T4
+ perceived-severity major
+ alarm-text “disc utilization high, major threshold”
/s
>
> Joe
