RE: Range type: upper_bound constraint to be "greater than or equal to" instead of "greater than"?

[Arturo Martin De Nicolas <arturo.martin-de-nicolas@ericsson.com>]

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:

Keyname	Required	Type	Constraints	Description
capability	yes	string	N/A	The required reserved keyname used that can be used to provide the name of a valid Capability Type  that can fulfill the requirement.
node	no	string	N/A	The optional reserved keyname used to provide the name of a valid Node Type that contains the capability definition that can be used to fulfill the requirement.
relationship	no	string	N/A	The optional reserved keyname used to provide the name of a valid Relationship Type to construct when fulfilling the requirement.
occurrences	no	range of integer	implied default of [1,1]	The optional minimum and maximum occurrences for the requirement. Note: the keyword UNBOUNDED is also supported to represent any positive integer.

 

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)
Sent: Wednesday, April 10, 2019 4:55 PM
To: tosca@lists.oasis-open.org
Subject: [tosca] Range type: upper_bound constraint to be "greater than or equal to" instead of "greater than"?

 

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:

[<lower_bound>, <upper_bound>]  

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