[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: Range type: upper_bound constraint to be "greater than or equal to" instead of "greater than"?
+1 Regards Shitao åää: tosca@lists.oasis-open.org [mailto:tosca@lists.oasis-open.org]
äè
Arturo Martin De Nicolas Hello Gabor, Yes, I agree with you. In fact it is not only SOL001 using it. Even the very TOSCA spec uses [ 1, 1] as the default range for requirements occurrences: The following is the list of recognized keynames for a TOSCA requirement definition:
It should be fixed. BR, Arturo From:
tosca@lists.oasis-open.org <tosca@lists.oasis-open.org>
On Behalf Of Marton, Gabor (Nokia - HU/Budapest) Dear TOSCA Experts, we ran into this issue recently. The specs (both v1.2 and pre-v1.3) says: 3.3.3.1 Grammar TOSCA range values have the following grammar:
In the above grammar, the pseudo values that appear in angle brackets have the following meaning:
Â
lower_bound: is a required integer value that denotes the lower boundary of the range.
Â
upper_bound: is a required integer value that denotes the upper boundary of the range. This value MUST be
greater than
lower_bound. Instead of âgreater thanâ, the constraint should better be âgreater than or equal toâ as a range like â[ 1, 1 ]â is a valid range. It is also used in the ETSI NFV SOL001 specifications, e.g.: tosca.nodes.nfv.Vdu.Compute: derived_from: tosca.nodes.Root description: Describes the virtual compute part of a VDU which is a construct supporting the description of the deployment
and operational behavior of a VNFC properties: .. capabilities: virtual_compute: type: tosca.capabilities.nfv.VirtualCompute occurrences:
[ 1, 1 ] .. .. Do you agree with the conclusion? Kind regards, GÃbor |
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]