Re: [CCAMP] Opsdir last call review of draft-ietf-ccamp-alarm-module-07

stefan vallin <stefan@wallan.se> Wed, 20 March 2019 07:50 UTC

Return-Path: <stefan@wallan.se>
X-Original-To: ccamp@ietfa.amsl.com
Delivered-To: ccamp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 25E62130F86 for <ccamp@ietfa.amsl.com>; Wed, 20 Mar 2019 00:50:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=wallan-se.20150623.gappssmtp.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HJh5h24qAOcS for <ccamp@ietfa.amsl.com>; Wed, 20 Mar 2019 00:50:38 -0700 (PDT)
Received: from mail-lf1-x136.google.com (mail-lf1-x136.google.com [IPv6:2a00:1450:4864:20::136]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 75F70127817 for <ccamp@ietf.org>; Wed, 20 Mar 2019 00:50:38 -0700 (PDT)
Received: by mail-lf1-x136.google.com with SMTP id y18so1134659lfe.1 for <ccamp@ietf.org>; Wed, 20 Mar 2019 00:50:38 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=wallan-se.20150623.gappssmtp.com; s=20150623; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=VNJQQQzzSZxIJMaFnEx1aPKntERkUPdS3qaEZLUcWcA=; b=T/5XXmR/gpVsMrePZJy/8oU8uX+LasUy81tKH6gDwQs5k9z96Wi3kOIcUFL+0LTF2Y 8hLkHFpI7iScz+iryY1BYiX+J4BjpJc0DOqwpMwLaV9Or75EZnbUm4KPg82ZEIpShMi+ h2PdI2N1c4vETQPICsSNZgyZR6cSer+QnAwAW1eC/mF4KqAydL5Dde6kYF/kNAcfNzQ3 VsSowI4VZzLiwGOpkCWjX96OX9AbzJZ58sb8PKY5zV56P+8DPRHkAojEk5tcSvKlg995 8GBchvVzf1XPy5yGRM5S0OR/85ioTOu8PtVPIRnBGNdbY9rSpNIFFV5/v7dJhaKV9Gtl 3rQA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=VNJQQQzzSZxIJMaFnEx1aPKntERkUPdS3qaEZLUcWcA=; b=oI+VPnEYzffCM49uvgLsPbD4HK/J218h2dVHNXSDt0Ykd21XgMK46egaPHrNAdjZmc igDoIDJsN18HzoxjaR0zFhJTfeBxUUYXbP7ktLth/lOdeOv+wIvbrEogLrWKOdMh+9Ht OxTKtS9VZXZtDh856gSb+T9rAZvXePSdSfglbZuu5WkqKdyXzW+kaW+8God0Ei57BLei uzWRM6sJPlnQ/MNKL37J6kNa0V1tI0tjTxR9dzp3f19f8MFQB4sbciPwZ1wXhU652eeU F0/FGy4ogX/aIHw01L6ZSbMh9/A86NSF+zgOdQZWdU0KClcbW867POMjvLk3kiGsvwLK GdWw==
X-Gm-Message-State: APjAAAW56IFnmRTvj9Vu47fOreHAawxf4kyA5pYaPgLT5bIM8KXtn07E DqhQlxmCB00/ORCbn2WEjhG4qw==
X-Google-Smtp-Source: APXvYqyPm41HiNZECiqffDeUUf7JLDC7cQR8PFoiUEgH0Gir9rk5Im1fTdCpIxuf7CdhvXVIUXdHUg==
X-Received: by 2002:a19:6d01:: with SMTP id i1mr15076330lfc.118.1553068236684; Wed, 20 Mar 2019 00:50:36 -0700 (PDT)
Received: from [192.168.72.11] (h95-155-237-105.cust.a3fiber.se. [95.155.237.105]) by smtp.gmail.com with ESMTPSA id r1sm224293lfm.7.2019.03.20.00.50.35 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 20 Mar 2019 00:50:36 -0700 (PDT)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 12.0 \(3445.100.39\))
From: stefan vallin <stefan@wallan.se>
In-Reply-To: <efca66f6-63f0-de8b-69fe-a60e05b9571f@cisco.com>
Date: Wed, 20 Mar 2019 08:50:31 +0100
Cc: ops-dir@ietf.org, draft-ietf-ccamp-alarm-module.all@ietf.org, ccamp@ietf.org, ietf@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <C429E1B3-DDBB-47E1-86C4-67A12F37EB7F@wallan.se>
References: <155292844015.26147.11067773612585181394@ietfa.amsl.com> <22EBF1ED-7CE4-4A4F-A105-C76D17D2F2DA@wallan.se> <15ac10fa-db49-df31-c532-03a3692a2ca2@cisco.com> <556B8CFB-E3E0-44AB-B82B-9E60CE4C0FF5@wallan.se> <0b559129-fc1f-c4b0-eaf6-4a03780e93f1@cisco.com> <425F5BB9-DAF8-401C-A048-5BC00BD9EC23@wallan.se> <91fa8482-9f24-513d-1b37-fba6ff73b6f8@cisco.com> <1A78CDC1-3F04-43DA-A3A4-E8D1C13520C8@wallan.se> <efca66f6-63f0-de8b-69fe-a60e05b9571f@cisco.com>
To: Joe Clarke <jclarke@cisco.com>
X-Mailer: Apple Mail (2.3445.100.39)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ccamp/Yr7KxVlBXPaxZC6wR_EMpAvKqkc>
Subject: Re: [CCAMP] Opsdir last call review of draft-ietf-ccamp-alarm-module-07
X-BeenThere: ccamp@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Discussion list for the CCAMP working group <ccamp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ccamp>, <mailto:ccamp-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ccamp/>
List-Post: <mailto:ccamp@ietf.org>
List-Help: <mailto:ccamp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 20 Mar 2019 07:50:41 -0000

Hi!

> On 19 Mar 2019, at 18:08, Joe Clarke <jclarke@cisco.com>; 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