Comments inline:
Thanks,
Mathi.
- hans.fe...@ericsson.com wrote:
See inline
Thanks,
Hans
From: Mathivanan Naickan Palanivelu [mailto:mathi.naic...@oracle.com]
Sent: den 25 april 2014 12:08
To: Hans Feldt; Bertil Engelholm
Cc: opensaf-devel@lists.sourceforge.net
-Original Message-
From: Bertil Engelholm
Sent: den 25 april 2014 07:31
To: Hans Feldt; mathi.naic...@oracle.com
Cc: opensaf-devel@lists.sourceforge.net
Subject: RE: [PATCH 2 of 2] clm: add ETF file for CLMD [#848]
What about CLMNA? Should it be in a separate file or in this one
See inline
Thanks,
Hans
From: Mathivanan Naickan Palanivelu [mailto:mathi.naic...@oracle.com]
Sent: den 25 april 2014 12:08
To: Hans Feldt; Bertil Engelholm
Cc: opensaf-devel@lists.sourceforge.net
Subject: RE: [PATCH 2 of 2] clm: add ETF file for CLMD [#848]
Nice start.
Like Bertil
Nice start.
Like Bertil commented, yes CLMNA should also be part of the same ETF for the
CLM 'software'!
And,
What about the below, will they be part of some OpenSAF common ETF?
+xs:element name=SUType++
+xs:element name=SGType-+---
+xs:element
osaf/services/saf/clmsv/config/ETF-CLMD.xml | 35 +
osaf/services/saf/clmsv/config/Makefile.am | 2 +
2 files changed, 37 insertions(+), 0 deletions(-)
Add an ETF file for CLMD. The contents corresponds to what we have in the
IMM XML file.
diff --git
What about CLMNA? Should it be in a separate file or in this one (for CLMSV)?
Should the version of the CS type be set outside (as CT version) or should it
be 4.0.0 as before?
The CT and CS names does not match the current names, this will be a problem if
this information
is used for upgrades of
