===========================================
Minutes from NPM NM-WG Object Model Meeting
EGEE JRA4 Face to Face (July 2005)
===========================================

Date:  13th July 2005
Venue: NeSC, Edinburgh

Present:
  DANTE: Loukik Kudarimoti (LK)
  DL:    Mark Leese (ML)
  UEDIN: Ahmed Abdelrahim (AA), Ratnadeep Abrol (RA),
         Kostas Kavoussanakis (KK), Alistair Phipps (AKP)

Apologies:
  DFN:   Robert Stoy (RS)


Glossary
========

DT    = Diagnostic Tool
f2f   = face 2 face
MP    = monitoring point
PS    = PerfSONAR (GN2:JRA1 tool)
TL    = Translation Layer (to GN2:JRA1)
TLS   = Transport Level Security
wrt   = with respect to
WS    = Web Service


Actions
=======

[AKP] Add accessors/mutators for tolerance to TimeInterval

[AKP] Add "unlisted" Characteristic Type

[AKP] Rename StatisticInterval to IntervalStatistic and
      StatisticPercentile to PercentileStatistic

[RA] Take note of the fact that the "optional" part of parameters
     relates to whether they MUST be honored by frameworks rather
     than whether they must be filled in by the user.

[AKP] Check if PacketSize units are definable or always bytes.

[AKP] Add "unlisted" Metric Type

[AKP] Send mark slide of characteristics.

[ML] Tell AKP which parameters map to which characteristics.

[LK] Work on object model for NM-WGv2, but only do so for those
     objects that will be used in GN2:JRA1.

[AKP/LK] Merge LK's NM-WGv2 object model with AKP's object model. 

[KK] Find out from TNLC/SA2 who is responsible for signing data
     disclosure declarations in EGEE wrt NPM data from NRENs.


Decisions
=========

* Keep DSCP as parameter as it will be in PS.

* List of statistics/characteristics should be limited to
  those that are going to be available for EGEE-1.


General Discussion
==================

Purpose of object model is to provide an abstraction layer that
insulates main logic of components from how the requests/responses are
communicated to components (i.e. away from XML and Axis generated
beans).

Mappers are used to convert to and from object model.

This allows communication technologies to change without effecting all
logic code - will only effect Mappers.

The object model should not be tied to a particular NM-WG schema but
it should be possible to convert it to any existing version of the
NM-WG schema that we use.

The object model will evolve as the needs of network performance
monitoring evolves.


Address
-------

RA:  Possible to have more than two addresses. As we're not allowing
     hop lists is this correct?
AKP: <convincing argument that I can't remember>
RA:  OK is only a minor issue not worth spending time on.


TimeInterval
------------

RA: should have accessors and mutators for time tolerance as will be
    useful for users (esp. DT).

Units: double milliseconds.


CharacteristicType
------------------

Add "unlisted" characteristic type that takes a string value. It is up
to mappers to decide what to do with "unlisted" types - they should
attempt to map the string value associated with this type.

The list of characteristics should be limited to those that will be
available in EGEE-1.

Statistic
---------

Rename StatisticInterval to IntervalStatistic
Rename StatisticPercentile to PercentileStatistic

The list of statistics should be limited to those that will be
available in EGEE-1.



RA 15/07/2005