Re: [lmap] draft-ietf-lmap-information-model-05: Controller timeout

Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de> Tue, 12 May 2015 14:20 UTC

Return-Path: <j.schoenwaelder@jacobs-university.de>
X-Original-To: lmap@ietfa.amsl.com
Delivered-To: lmap@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F29471A87CC for <lmap@ietfa.amsl.com>; Tue, 12 May 2015 07:20:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.86
X-Spam-Level:
X-Spam-Status: No, score=-3.86 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_MED=-2.3, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 VesUJNHMBxp8 for <lmap@ietfa.amsl.com>; Tue, 12 May 2015 07:20:10 -0700 (PDT)
Received: from atlas3.jacobs-university.de (atlas3.jacobs-university.de [212.201.44.18]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 624741A87AB for <lmap@ietf.org>; Tue, 12 May 2015 07:20:10 -0700 (PDT)
Received: from localhost (demetrius5.irc-it.jacobs-university.de [10.70.0.222]) by atlas3.jacobs-university.de (Postfix) with ESMTP id 2D489842; Tue, 12 May 2015 16:20:09 +0200 (CEST)
X-Virus-Scanned: amavisd-new at jacobs-university.de
Received: from atlas3.jacobs-university.de ([10.70.0.220]) by localhost (demetrius5.jacobs-university.de [10.70.0.222]) (amavisd-new, port 10030) with ESMTP id RII81POCrRhM; Tue, 12 May 2015 16:20:04 +0200 (CEST)
Received: from hermes.jacobs-university.de (hermes.jacobs-university.de [212.201.44.23]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "hermes.jacobs-university.de", Issuer "Jacobs University CA - G01" (verified OK)) by atlas3.jacobs-university.de (Postfix) with ESMTPS; Tue, 12 May 2015 16:20:08 +0200 (CEST)
Received: from localhost (demetrius4.jacobs-university.de [212.201.44.49]) by hermes.jacobs-university.de (Postfix) with ESMTP id 2FA9E2002B; Tue, 12 May 2015 16:20:08 +0200 (CEST)
X-Virus-Scanned: amavisd-new at jacobs-university.de
Received: from hermes.jacobs-university.de ([212.201.44.23]) by localhost (demetrius4.jacobs-university.de [212.201.44.32]) (amavisd-new, port 10024) with ESMTP id JGrflMRKlxbF; Tue, 12 May 2015 16:20:07 +0200 (CEST)
Received: from elstar.local (elstar.jacobs.jacobs-university.de [10.50.231.133]) by hermes.jacobs-university.de (Postfix) with ESMTP id 2EFEA20013; Tue, 12 May 2015 16:20:07 +0200 (CEST)
Received: by elstar.local (Postfix, from userid 501) id 6FBF33331837; Tue, 12 May 2015 16:20:06 +0200 (CEST)
Date: Tue, 12 May 2015 16:20:06 +0200
From: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
To: "Carey, Timothy (Timothy)" <timothy.carey@alcatel-lucent.com>
Message-ID: <20150512142006.GB57299@elstar.local>
Mail-Followup-To: "Carey, Timothy (Timothy)" <timothy.carey@alcatel-lucent.com>, "lmap@ietf.org" <lmap@ietf.org>
References: <9966516C6EB5FC4381E05BF80AA55F77BA2612C2@US70UWXCHMBA05.zam.alcatel-lucent.com> <20150512100724.GC26662@elstar.local> <9966516C6EB5FC4381E05BF80AA55F77BA2616F5@US70UWXCHMBA05.zam.alcatel-lucent.com> <20150512124209.GC41964@elstar.local> <9966516C6EB5FC4381E05BF80AA55F77BA261858@US70UWXCHMBA05.zam.alcatel-lucent.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <9966516C6EB5FC4381E05BF80AA55F77BA261858@US70UWXCHMBA05.zam.alcatel-lucent.com>
User-Agent: Mutt/1.4.2.3i
Archived-At: <http://mailarchive.ietf.org/arch/msg/lmap/cv0fQKgK521ZnV2dATQUxwqhGrM>
Cc: "lmap@ietf.org" <lmap@ietf.org>
Subject: Re: [lmap] draft-ietf-lmap-information-model-05: Controller timeout
X-BeenThere: lmap@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
List-Id: Large Scale Measurement of Access network Performance <lmap.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/lmap>, <mailto:lmap-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/lmap/>
List-Post: <mailto:lmap@ietf.org>
List-Help: <mailto:lmap-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/lmap>, <mailto:lmap-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 12 May 2015 14:20:13 -0000

On Tue, May 12, 2015 at 01:04:49PM +0000, Carey, Timothy (Timothy) wrote:

> So does that now mean we need to have a operational status now for a
> scheduled task? I can see it now as attribute with values like:
> enabled, disabled, suppressed and errored or possibly a conditions
> object?

I think there two questions here:

a) If I loose connectivity, do I disable all schedules (and thus
   implicitely all actions) or do I disable scheduled tasks? My idea
   was to simply disable all schedules (and as such the schedules have
   their state changed to disabled).

   The suppression mechanism can suppress both a list of tasks and a
   list of schedules and it is configurable what is being suppressed.

   One option is that loss of connectivity simply causes suppression
   to be activated. Another option is that loss of connectivity
   supresses all tasks that are not essential for communication with a
   controller and house keeping. Another option is that loss of
   connectivity suppresses all schedules. We need to select one.

b) Do we expose the internal state that is maintained? Right now, we
   do not expose any operational state for schedules. But we do expose
   operational state for tasks. If loss of connectivity means we
   disable all tasks that are not essential for communication with a
   controller and house keeping, than exposing that information would
   be a rather minor change to the information and data model.

   A task state would then be enabled (default), suppressed or
   disabled. Error information is already covered in the last-failed
   attributes of a task. (And this is useful in situations where tasks
   fail occasionally so you can get information about the last failure
   even though the task is working fine right now).

/js

-- 
Juergen Schoenwaelder           Jacobs University Bremen gGmbH
Phone: +49 421 200 3587         Campus Ring 1 | 28759 Bremen | Germany
Fax:   +49 421 200 3103         <http://www.jacobs-university.de/>