[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: re: [tosca] Groups - clarification on get_property .doc uploaded
|
Hi Arturo I think your analysis makes sense to me. Right now the example I provided is based on the case that the monitoring_paramter will be used in the VNF node template, so it does not
matter whether it is optional or mandatory in the node type. If we can agree on the below principles, then we can give design guidance based on those principles if somebody does not want to present the monitoring_paramter in the VNF node template inside a
NSD service template. Regards shitao åää: Arturo Martin De Nicolas [mailto:arturo.martin-de-nicolas@ericsson.com]
Hello Shitao, Thanks for bringing this up. This is my view: It depends on how the property is defined on VNF node type definition. a) The property is an optional property of the VNF node type. Then if the node template does not include a property assignment it means the node does not have this property and the get_property
function used from another node template should fail. b) The property is mandatory and had a default value defined in the node type definition. In that case, if the node template doesn't include the property assignment, it will take the
default value and the get_property returns this value. The monitoring_parameters is an optional property in the VNF node. From TOSCA perspective a derived node type could define it as mandatory, but I think in SOL001 we have not really
discussed about changing optional properties to mandatory in the derived types, have we? Best regards, Arturo
From:
tosca@lists.oasis-open.org <tosca@lists.oasis-open.org>
On Behalf Of shitao li
|
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]