Re: [devel] [PATCH 2 of 2] clm: add ETF file for CLMD [#848]

2014-04-29 Thread Mathivanan Naickan Palanivelu
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
 Subject: RE: [PATCH 2 of 2] clm: add ETF file for CLMD [#848]
 
 
 
 Nice start.
 
 
 
 Like Bertil commented, yes CLMNA should also be part of the same ETF
 for the CLM ‘software’!
 
 [Hans] sure this was just an RFC, the same or another file?
 

I don't know which is better, i.e. ETF per middleware service or ETF per 
middleware component.
I'm inclining towards ETF per middleware service!

The SMF spec talks of ETF w.r.t software bundles, not sure if it
should be seen as ETF 'per' software bundle!

To quote: 
When a software vendor provides a new software bundle, an entity types file 
describ-
ing the content of the software bundle shall be supplied with the bundle.
...One entity types file may refer to multiple software bundles, each of which 
must
be identified according to the XML schema



 And,
 
 
 
 What about the below, will they be part of some OpenSAF common ETF?
 
 +xs:element name=SUType++
 
 +xs:element name=SGType-+---
 
 +xs:element name=AppType++
 
 +xs:element name=CSType++
 
 +xs:element name=ServiceType
 
 [Hans] I currently don’t see any need for that.
 
 

The SMF spec/schema already defines which elements should be
mandatory element, optional or alternative.
We could use that as the guideline!


 
 And did you not think of the need for defining any appropriate item
 from below?
 
 [Hans] Sorry I don’t get this list, what exactly is missing from this
 ETF to generate the same imm.xml as today
 

While there is a rule/guideline from the SMF spec, it also depends
on the scope for the tool that is going to use this ETF file.
I'm not sure about the scope of this activity(patch request)!?

You could weigh all your comments below w.r.t the guideline for ETF from the 
SMF spec.

 
 
 -xs:element name=swBundle maxOccurs=unbounded minOccurs=0
 
 +xs:element name=removal++--
 
 +xs:element name=installation-+ /xs:sequence
 
 [Hans] I currently don’t see a need for the bundle part
 
 
 
 +xs:element name=quiescingComplete type=BoundedTimeT-
 
 [Hans] already in there
 
 +xs:element name=numInstances type=UnsignedInt32T-
 
 +xs:element name=numMaxStandbyCsi type=BoundedUInt32T-
 
 [Hans] could add that
 
 +xs:element name=instantiateCmd--
 
 [Hans] already in there
 
 +xs:element name=numMaxActiveCsi type=BoundedUInt32T-
 
 [Hans] could add that
 
 +xs:attributeGroup name=valueRange-
 
 +xs:complexType name=UnsignedInt32T-
 
 +xs:complexType name=BoundedUInt32T-
 
 +xs:complexType name=BoundedTimeT-
 
 +xs:complexType name=callbackOptionsT--
 
 +xs:complexType name=ProbationT-
 
 +xs:simpleType name=SaTimeT-
 
 +xs:simpleType name=SaStringT-
 
 +xs:simpleType name=VersionT--
 
 +xs:simpleType name=SwBundleNameT--
 
 +xs:simpleType name=CompTypeNameT--
 
 +xs:simpleType name=SUTypeNameT--
 
 +xs:simpleType name=SGTypeNameT--
 
 +xs:simpleType name=AppTypeNameT--
 
 +xs:simpleType name=CSTypeNameT--
 
 +xs:simpleType name=SrvTypeNameT--
 
 +xs:simpleType name=RecommendedRecoveryT--
 
 [Hans] already in there
 
 +xs:simpleType name=HealthcheckVariantT--
 
 +xs:simpleType name=RedModelT--
 
 +xs:group name=CompCapability
 
 +xs:group name=CompCallbackTimeouts--
 
 +xs:group name=CliParameters--
 
 +xs:group name=CommonCompAttributes-
 
 [Hans] yes the relevant ones are configured
 
 +xs:group name=ScopeOfImpact
 
 
 
 
 
 Thanks,
 
 Mathi.
 
 
 
 
 
 -Original Message-
 
 From: Hans Feldt [ mailto:hans.fe...@ericsson.com ]
 
 Sent: Thursday, April 24, 2014 7:10 PM
 
 To: bertil.engelh...@ericsson.com ; Mathivanan Naickan Palanivelu
 
 Cc: opensaf-devel@lists.sourceforge.net
 
 Subject: [PATCH 2 of 2] clm: add ETF file for CLMD [#848]
 
 
 
  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 a/osaf/services/saf/clmsv/config/ETF-CLMD.xml
 
 b/osaf/services/saf/clmsv/config/ETF-CLMD.xml
 
 new file mode 100644
 
 --- /dev/null
 
 +++ b/osaf/services/saf/clmsv/config/ETF-CLMD.xml
 
 @@ -0,0 +1,35 @@
 
 +?xml version=1.0 encoding=utf-8?
 
 +entityTypesFile xmlns:xsi= http://www.w3.org/2001/XMLSchema-
 
 instance  name=CLMD provider=OSAF
 
 + AmfEntityType
 
 + CompType name=safCompType=OSAF-CLMD
 
 version=safVersion=1
 
 + providesCSType name=safCSType=OSAF-CLMD
 
 version=safVersion=1
 
 + oneactiveoronestandby/
 
 + /providesCSType
 
 + saAware
 
 + healthCheck
 
 key=safHealthcheckKey=Default
 
 + period lowerBound=2400
 
 

Re: [devel] [PATCH 2 of 2] clm: add ETF file for CLMD [#848]

2014-04-28 Thread Hans Feldt

 -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 (for CLMSV)?
[Hans] I would prefer a separate file for each AMF component. For a tool I 
guess it does not matter. For a human looking to find an ETF for an AMF comp it 
be easier with separate files. What is your preference?

 Should the version of the CS type be set outside (as CT version) or should it 
 be 4.0.0 as before?
[Hans] Maybe the use of 4.0.0 was a mistake. Should these numbers ever change 
and do we need a semantic interpretation like 4.0.0 is promising compared to 
1,2,3 etc?
CS type version is hardcoded now, what do you mean set outside?

 The CT and CS names does not match the current names, this will be a problem 
 if this information
 is used for upgrades of systems with current names.
[Hans] the current names were not good, e.g. contain redundant information: 
safCompType=OpenSafCompTypeCLM
I do agree we need alignment between imm.xml and etf.xml, we cannot have 
different naming. Eventually perhaps a tool should generate imm.xml from the 
ETFs.

Ideally I think we should change the names. We need a fresh start in opensaf 
with the best we can think of now. The problem is change to what?

/Hans

 
 /Bertil
 
 -Original Message-
 From: Hans Feldt
 Sent: den 24 april 2014 15:40
 To: Bertil Engelholm; mathi.naic...@oracle.com
 Cc: opensaf-devel@lists.sourceforge.net
 Subject: [PATCH 2 of 2] clm: add ETF file for CLMD [#848]
 
  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 a/osaf/services/saf/clmsv/config/ETF-CLMD.xml 
 b/osaf/services/saf/clmsv/config/ETF-CLMD.xml
 new file mode 100644
 --- /dev/null
 +++ b/osaf/services/saf/clmsv/config/ETF-CLMD.xml
 @@ -0,0 +1,35 @@
 +?xml version=1.0 encoding=utf-8?
 +entityTypesFile xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; 
 name=CLMD provider=OSAF
 + AmfEntityType
 + CompType name=safCompType=OSAF-CLMD version=safVersion=1
 + providesCSType name=safCSType=OSAF-CLMD 
 version=safVersion=1
 + oneactiveoronestandby/
 + /providesCSType
 + saAware
 + healthCheck key=safHealthcheckKey=Default
 + period lowerBound=2400 
 default=2400/
 + maxDuration lowerBound=1800/
 + /healthCheck
 + quiescingComplete lowerBound=100 
 default=100/
 + independent
 + instantiateCmd
 + 
 commandxxCLCCLIDIRxx/osaf-clmd/command
 + argsinstantiate/args
 + /instantiateCmd
 + cleanupCmd
 + 
 commandxxCLCCLIDIRxx/osaf-clmd/command
 + argscleanup/args
 + /cleanupCmd
 + /independent
 + /saAware
 + disableRestarttrue/disableRestart
 + recoveryOnErrorSA_AMF_NODE_FAILFAST/recoveryOnError
 + defaultClcCliTimeOut lowerBound=100/
 + defaultCallbackTimeOut lowerBound=400/
 + bundleReference name=safSmfBundle=OSAF/
 + /CompType
 + /AmfEntityType
 + AmfEntityType
 + CSType name=safCSType=OSAF-CLMD version=safVersion=1 /
 + /AmfEntityType
 +/entityTypesFile
 diff --git a/osaf/services/saf/clmsv/config/Makefile.am 
 b/osaf/services/saf/clmsv/config/Makefile.am
 --- a/osaf/services/saf/clmsv/config/Makefile.am
 +++ b/osaf/services/saf/clmsv/config/Makefile.am
 @@ -38,6 +38,8 @@ dist_pkgimmxml_svc_DATA += \
   clmsv_pl_template.xml
  endif
 
 +dist_pkgetfxml_svc_DATA = \
 + ETF-CLMD.xml
  endif
 
  install-data-hook:

--
Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE
Instantly run your Selenium tests across 300+ browser/OS combos.  Get 
unparalleled scalability from the best Selenium testing platform available.
Simple to use. Nothing to install. Get started now for free.
http://p.sf.net/sfu/SauceLabs
___
Opensaf-devel mailing list

Re: [devel] [PATCH 2 of 2] clm: add ETF file for CLMD [#848]

2014-04-28 Thread Hans Feldt
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 commented, yes CLMNA should also be part of the same ETF for the 
CLM 'software'!

[Hans] sure this was just an RFC, the same or another file?

And,



What about the below, will they be part of some OpenSAF common ETF?

+xs:element name=SUType++

+xs:element name=SGType-+---

+xs:element name=AppType++

+xs:element name=CSType++

+xs:element name=ServiceType

[Hans] I currently don't see any need for that.



And did you not think of the need for defining any appropriate item from below?

[Hans] Sorry I don't get this list, what exactly is missing from this ETF to 
generate the same imm.xml as today



-xs:element name=swBundle maxOccurs=unbounded minOccurs=0

+xs:element name=removal++--

+xs:element name=installation-+ /xs:sequence

[Hans] I currently don't see a need for the bundle part



+xs:element name=quiescingComplete type=BoundedTimeT-

[Hans] already in there

+xs:element name=numInstances type=UnsignedInt32T-

+xs:element name=numMaxStandbyCsi type=BoundedUInt32T-

[Hans] could add that

+xs:element name=instantiateCmd--

[Hans] already in there

+xs:element name=numMaxActiveCsi type=BoundedUInt32T-

[Hans] could add that

+xs:attributeGroup name=valueRange-

+xs:complexType name=UnsignedInt32T-

+xs:complexType name=BoundedUInt32T-

+xs:complexType name=BoundedTimeT-

+xs:complexType name=callbackOptionsT--

+xs:complexType name=ProbationT-

+xs:simpleType name=SaTimeT-

+xs:simpleType name=SaStringT-

+xs:simpleType name=VersionT--

+xs:simpleType name=SwBundleNameT--

+xs:simpleType name=CompTypeNameT--

+xs:simpleType name=SUTypeNameT--

+xs:simpleType name=SGTypeNameT--

+xs:simpleType name=AppTypeNameT--

+xs:simpleType name=CSTypeNameT--

+xs:simpleType name=SrvTypeNameT--

+xs:simpleType name=RecommendedRecoveryT--

[Hans] already in there

+xs:simpleType name=HealthcheckVariantT--

+xs:simpleType name=RedModelT--

+xs:group name=CompCapability

+xs:group name=CompCallbackTimeouts--

+xs:group name=CliParameters--

+xs:group name=CommonCompAttributes-

[Hans] yes the relevant ones are configured

+xs:group name=ScopeOfImpact





Thanks,

Mathi.





-Original Message-

From: Hans Feldt [mailto:hans.fe...@ericsson.com]

Sent: Thursday, April 24, 2014 7:10 PM

To: bertil.engelh...@ericsson.commailto:bertil.engelh...@ericsson.com; 
Mathivanan Naickan Palanivelu

Cc: 
opensaf-devel@lists.sourceforge.netmailto:opensaf-devel@lists.sourceforge.net

Subject: [PATCH 2 of 2] clm: add ETF file for CLMD [#848]



 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 a/osaf/services/saf/clmsv/config/ETF-CLMD.xml

b/osaf/services/saf/clmsv/config/ETF-CLMD.xml

new file mode 100644

--- /dev/null

+++ b/osaf/services/saf/clmsv/config/ETF-CLMD.xml

@@ -0,0 +1,35 @@

+?xml version=1.0 encoding=utf-8?

+entityTypesFile 
xmlns:xsi=http://www.w3.org/2001/XMLSchema-http://www.w3.org/2001/XMLSchema-instance

instancehttp://www.w3.org/2001/XMLSchema-instance name=CLMD 
provider=OSAF

+   AmfEntityType

+   CompType name=safCompType=OSAF-CLMD

version=safVersion=1

+   providesCSType 
name=safCSType=OSAF-CLMD

version=safVersion=1

+   
oneactiveoronestandby/

+   /providesCSType

+   saAware

+   healthCheck

key=safHealthcheckKey=Default

+   
period lowerBound=2400

default=2400/

+   
maxDuration

lowerBound=1800/

+   /healthCheck

+   quiescingComplete

lowerBound=100 default=100/

+   independent

+   
instantiateCmd

+

 commandxxCLCCLIDIRxx/osaf-clmd/command

+  
 argsinstantiate/args

+   
/instantiateCmd

+

Re: [devel] [PATCH 2 of 2] clm: add ETF file for CLMD [#848]

2014-04-25 Thread Mathivanan Naickan Palanivelu
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 name=AppType++ 

+xs:element name=CSType++ 

+xs:element name=ServiceType

 

And did you not think of the need for defining any appropriate item from below?

 

-xs:element name=swBundle maxOccurs=unbounded minOccurs=0 

+xs:element name=removal++-- 

+xs:element name=installation-+ /xs:sequence

 

+xs:element name=quiescingComplete type=BoundedTimeT- 

+xs:element name=numInstances type=UnsignedInt32T- 

+xs:element name=numMaxStandbyCsi type=BoundedUInt32T- 

+xs:element name=instantiateCmd-- 

+xs:element name=numMaxActiveCsi type=BoundedUInt32T- 

+xs:attributeGroup name=valueRange- 

+xs:complexType name=UnsignedInt32T- 

+xs:complexType name=BoundedUInt32T- 

+xs:complexType name=BoundedTimeT- 

+xs:complexType name=callbackOptionsT-- 

+xs:complexType name=ProbationT- 

+xs:simpleType name=SaTimeT- 

+xs:simpleType name=SaStringT- 

+xs:simpleType name=VersionT-- 

+xs:simpleType name=SwBundleNameT-- 

+xs:simpleType name=CompTypeNameT-- 

+xs:simpleType name=SUTypeNameT-- 

+xs:simpleType name=SGTypeNameT-- 

+xs:simpleType name=AppTypeNameT-- 

+xs:simpleType name=CSTypeNameT-- 

+xs:simpleType name=SrvTypeNameT-- 

+xs:simpleType name=RecommendedRecoveryT-- 

+xs:simpleType name=HealthcheckVariantT-- 

+xs:simpleType name=RedModelT-- 

+xs:group name=CompCapability 

+xs:group name=CompCallbackTimeouts-- 

+xs:group name=CliParameters-- 

+xs:group name=CommonCompAttributes- 

+xs:group name=ScopeOfImpact

 

 

Thanks,

Mathi.

 

 

-Original Message-

From: Hans Feldt [mailto:hans.fe...@ericsson.com]

Sent: Thursday, April 24, 2014 7:10 PM

To: bertil.engelh...@ericsson.com; Mathivanan Naickan Palanivelu

Cc: opensaf-devel@lists.sourceforge.net

Subject: [PATCH 2 of 2] clm: add ETF file for CLMD [#848]

 

 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 a/osaf/services/saf/clmsv/config/ETF-CLMD.xml

b/osaf/services/saf/clmsv/config/ETF-CLMD.xml

new file mode 100644

--- /dev/null

+++ b/osaf/services/saf/clmsv/config/ETF-CLMD.xml

@@ -0,0 +1,35 @@

+?xml version=1.0 encoding=utf-8?

+entityTypesFile xmlns:xsi=HYPERLINK 
http://www.w3.org/2001/XMLSchema-instancehttp://www.w3.org/2001/XMLSchema-

HYPERLINK http://www.w3.org/2001/XMLSchema-instance;instance name=CLMD 
provider=OSAF

+   AmfEntityType

+   CompType name=safCompType=OSAF-CLMD

version=safVersion=1

+   providesCSType 
name=safCSType=OSAF-CLMD

version=safVersion=1

+   
oneactiveoronestandby/

+   /providesCSType

+   saAware

+   healthCheck

key=safHealthcheckKey=Default

+   
period lowerBound=2400

default=2400/

+   
maxDuration

lowerBound=1800/

+   /healthCheck

+   quiescingComplete

lowerBound=100 default=100/

+   independent

+   
instantiateCmd

+

 commandxxCLCCLIDIRxx/osaf-clmd/command

+  
 argsinstantiate/args

+   
/instantiateCmd

+   
cleanupCmd

+

 commandxxCLCCLIDIRxx/osaf-clmd/command

+  
 argscleanup/args

+   
/cleanupCmd

+   /independent

+   /saAware

+   
disableRestarttrue/disableRestart

+

 recoveryOnErrorSA_AMF_NODE_FAILFAST/recoveryOnError

+   defaultClcCliTimeOut 
lowerBound=100/

+

[devel] [PATCH 2 of 2] clm: add ETF file for CLMD [#848]

2014-04-24 Thread Hans Feldt
 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 a/osaf/services/saf/clmsv/config/ETF-CLMD.xml 
b/osaf/services/saf/clmsv/config/ETF-CLMD.xml
new file mode 100644
--- /dev/null
+++ b/osaf/services/saf/clmsv/config/ETF-CLMD.xml
@@ -0,0 +1,35 @@
+?xml version=1.0 encoding=utf-8?
+entityTypesFile xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; 
name=CLMD provider=OSAF
+   AmfEntityType
+   CompType name=safCompType=OSAF-CLMD version=safVersion=1
+   providesCSType name=safCSType=OSAF-CLMD 
version=safVersion=1
+   oneactiveoronestandby/
+   /providesCSType
+   saAware
+   healthCheck key=safHealthcheckKey=Default
+   period lowerBound=2400 
default=2400/
+   maxDuration lowerBound=1800/
+   /healthCheck
+   quiescingComplete lowerBound=100 
default=100/
+   independent
+   instantiateCmd
+   
commandxxCLCCLIDIRxx/osaf-clmd/command
+   argsinstantiate/args
+   /instantiateCmd
+   cleanupCmd
+   
commandxxCLCCLIDIRxx/osaf-clmd/command
+   argscleanup/args
+   /cleanupCmd
+   /independent
+   /saAware
+   disableRestarttrue/disableRestart
+   recoveryOnErrorSA_AMF_NODE_FAILFAST/recoveryOnError
+   defaultClcCliTimeOut lowerBound=100/
+   defaultCallbackTimeOut lowerBound=400/
+   bundleReference name=safSmfBundle=OSAF/
+   /CompType
+   /AmfEntityType
+   AmfEntityType
+   CSType name=safCSType=OSAF-CLMD version=safVersion=1 /
+   /AmfEntityType
+/entityTypesFile
diff --git a/osaf/services/saf/clmsv/config/Makefile.am 
b/osaf/services/saf/clmsv/config/Makefile.am
--- a/osaf/services/saf/clmsv/config/Makefile.am
+++ b/osaf/services/saf/clmsv/config/Makefile.am
@@ -38,6 +38,8 @@ dist_pkgimmxml_svc_DATA += \
clmsv_pl_template.xml
 endif
 
+dist_pkgetfxml_svc_DATA = \
+   ETF-CLMD.xml
 endif
 
 install-data-hook:

--
Start Your Social Network Today - Download eXo Platform
Build your Enterprise Intranet with eXo Platform Software
Java Based Open Source Intranet - Social, Extensible, Cloud Ready
Get Started Now And Turn Your Intranet Into A Collaboration Platform
http://p.sf.net/sfu/ExoPlatform
___
Opensaf-devel mailing list
Opensaf-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-devel


Re: [devel] [PATCH 2 of 2] clm: add ETF file for CLMD [#848]

2014-04-24 Thread Bertil Engelholm
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 systems with current names.

/Bertil

-Original Message-
From: Hans Feldt 
Sent: den 24 april 2014 15:40
To: Bertil Engelholm; mathi.naic...@oracle.com
Cc: opensaf-devel@lists.sourceforge.net
Subject: [PATCH 2 of 2] clm: add ETF file for CLMD [#848]

 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 a/osaf/services/saf/clmsv/config/ETF-CLMD.xml 
b/osaf/services/saf/clmsv/config/ETF-CLMD.xml
new file mode 100644
--- /dev/null
+++ b/osaf/services/saf/clmsv/config/ETF-CLMD.xml
@@ -0,0 +1,35 @@
+?xml version=1.0 encoding=utf-8?
+entityTypesFile xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; 
name=CLMD provider=OSAF
+   AmfEntityType
+   CompType name=safCompType=OSAF-CLMD version=safVersion=1
+   providesCSType name=safCSType=OSAF-CLMD 
version=safVersion=1
+   oneactiveoronestandby/
+   /providesCSType
+   saAware
+   healthCheck key=safHealthcheckKey=Default
+   period lowerBound=2400 
default=2400/
+   maxDuration lowerBound=1800/
+   /healthCheck
+   quiescingComplete lowerBound=100 
default=100/
+   independent
+   instantiateCmd
+   
commandxxCLCCLIDIRxx/osaf-clmd/command
+   argsinstantiate/args
+   /instantiateCmd
+   cleanupCmd
+   
commandxxCLCCLIDIRxx/osaf-clmd/command
+   argscleanup/args
+   /cleanupCmd
+   /independent
+   /saAware
+   disableRestarttrue/disableRestart
+   recoveryOnErrorSA_AMF_NODE_FAILFAST/recoveryOnError
+   defaultClcCliTimeOut lowerBound=100/
+   defaultCallbackTimeOut lowerBound=400/
+   bundleReference name=safSmfBundle=OSAF/
+   /CompType
+   /AmfEntityType
+   AmfEntityType
+   CSType name=safCSType=OSAF-CLMD version=safVersion=1 /
+   /AmfEntityType
+/entityTypesFile
diff --git a/osaf/services/saf/clmsv/config/Makefile.am 
b/osaf/services/saf/clmsv/config/Makefile.am
--- a/osaf/services/saf/clmsv/config/Makefile.am
+++ b/osaf/services/saf/clmsv/config/Makefile.am
@@ -38,6 +38,8 @@ dist_pkgimmxml_svc_DATA += \
clmsv_pl_template.xml
 endif
 
+dist_pkgetfxml_svc_DATA = \
+   ETF-CLMD.xml
 endif
 
 install-data-hook:

--
Start Your Social Network Today - Download eXo Platform
Build your Enterprise Intranet with eXo Platform Software
Java Based Open Source Intranet - Social, Extensible, Cloud Ready
Get Started Now And Turn Your Intranet Into A Collaboration Platform
http://p.sf.net/sfu/ExoPlatform
___
Opensaf-devel mailing list
Opensaf-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-devel