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

["Marton, Gabor (Nokia - HU/Budapest)" <gabor.marton@nokia.com>]

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