Re: [lmap] LMAP Result Correlation

["Carey, Timothy (Nokia - US)" <[e-mail]>]

Juergen,

Oh - I am sorry then - I missed that this point. 
I wouldn't have an issue with a correlation point on the scheduled action - that is where the options are.

BR,
Tim

-----Original Message-----
From: EXT Juergen Schoenwaelder [mailto:[e-mail]] 
Sent: Monday, February 01, 2016 1:37 PM
To: Carey, Timothy (Nokia - US)
Cc: Ron Stana; [e-mail]; [e-mail]
Subject: Re: [lmap] LMAP Result Correlation

On Mon, Feb 01, 2016 at 06:47:49PM +0000, Carey, Timothy (Nokia - US) wrote:
> Juergen and Ron,
> 
> My comments in line <TAC>
> 
> 
> > If this understanding is correct, then to retrieve the results from 
> > the collector for either Schedule A or Schedule B seems to require 
> > unique tag to be specified with the schedule instead of the task.  The 'options'
> > object for the schedule could be used, however it would be more 
> > symmetrical to allow a tag for the schedule since the value would be 
> > sent to the collector in the 'tag' object of the report.
> 
> I agree that we should allow the definition of additional tags in the action configuration. Tim might have suggested this as well but I was not sure, see my other email.
> 
> 
> <TAC> Again it is the schedule action that would have the option - I am looking at draft-07 of the information framework section 3.7.2.
> The report has the scheduled action options in the ma-report-task-object section 3.6.2 so I don't understand the comment for the need in the schedule...
>

Tim,

we are talking about tags, not options. A tag is the YANG representation of what is called the cycle-id in the information model. In contrast to the information model, the YANG model allows a set of tags and not just a single one.

  The ma-task-obj has a ma-task-cycle-id of type string in the
  information model. In the YANG data model, we have instead a list of
  tags (and one of the tags can carry a cycle identifier. This allows
  us to have multiple tags for a given task.

  The ma-report-task-obj has a matching ma-report-task-cycle-id in the
  information model. In the YANG data model, we have again a list of
  tags.

  In order to distinguish reports from a given task kicked by different
  actions, the proposal was made to have the ability to define a tag or
  cycle-id in addition as part of the ma-action-obj.

I suggest to align the information model here with the YANG data model.

/js

-- 
Juergen Schoenwaelder           Jacobs University Bremen gGmbH
Phone: [phone]         Campus Ring 1 | 28759 Bremen | Germany
Fax:   [phone]         <http://www.jacobs-university.de/>