Re: [tosca] "occurrences" in requirement assignments

Hi Tal,

Tried to explain my understanding, does it make sense?

Please see inline.

BR/C

From: <tosca@lists.oasis-open.org> on behalf of Tal Liron <tliron@redhat.com>
Date: Thursday, 28 May 2020 at 19:45
To: "tosca@lists.oasis-open.org" <tosca@lists.oasis-open.org>
Subject: [tosca] "occurrences" in requirement assignments

This keyword was added in TOSCA 1.3, in section 3.8.2.1.

We've discussed it several times in the ad hoc meetings, in relation to ... many topics, most notably the instance model. But it remains for me a feature I simply cannot implement in Puccini.

In Puccini, "occurrences" in requirement definitions are interpreted to mean exactly how many times the requirement can/must be assigned in the node template, with the additional understanding that the sequenced list notation is there exactly in order to allow multiple assignments. I think this interpretation makes sense in many practical ways. Note that this has nothing to do with the instance model: this is all about TOSCA grammar and how many times you are allowed to specify something. (Puccini uses a similar design-time interpretation for "occurrences" in capabilities, for which it specifies how many times the capability can/must satisfy a requirement.)

[CC] fully agree.

But, with that understanding, I have no idea what "occurrences" could mean in the requirement assignment. It seems the thinking here is that "occurrences" has something to do with the instance model. So, for now, Puccini parses this keyword as proper syntax, but never does anything with it.

[CC] For requirements: In the assignment the occurrences itsâs only relevant if we use node-filters to connect to several nodes. Then if the same node filter should be reused, itâs easier to just put occurrences to â3â instead of repeating 3 times the requirement assignment

[CC] For capabilities: Itâs the final decision of how many connections to that capability are allowed. In the type we can specify a range, but in the end a final number needs to be chosen. Note, that this does not require a fixed number of connections, but fixes the maximum number of connections that can be supported. Of course, if no assignment is provided, the orchestrator could automatically choose (say the max of the interval from the type).

Indeed, for TOSCA 2.0 I've suggested several times that we should remove this keyword everywhere. If it's a design-time feature then it's rather narrow and hard to imagine as being very useful (and should probably be renamed to "assignments"). If it's a runtime feature, referring to the instance model, well that's a whole can of worms that we've discussed at length. I'll likely continue to argue that TOSCA should not have an opinion on the structure, and if it does then a simple counting of "how many runtime relationships" seems woefully insufficient.

But, I do want to open this up more on the email list, perhaps someone can shed some light on the confusion? Also, what do you think I should do in Puccini if it's impossible to "support" this keyword in requirement assignments?

tosca message