Hi everyone,
Happy to say that the Clearwater IMS example is now available on git
master. I know there's been a lot of interest in testing this, and we would
love feedback. Here are instructions:
https://cwiki.apache.org/confluence/display/ARIATOSCA/Clearwater+IMS
Note that work is not complete
The single sentence you mention in the 3.5.13.3 is the only place that
*might* be implying that ad hoc, type-less input assignments are allowed,
but I actually think it could have a different reading. What i meant is:
"...that do not necessarily have a property definition defined in its
In contrary to most of the TOSCA entities, TOSCA does not differentiate
between 'definition' and 'assignment' in the context of operations. There
are only "operation definitions" [3.5.13]. Logically, there is a partial
differentiation [3.5.13.1], where inputs in node type operations are
expected
I will add that if you absolutely need this change for your own testing,
you do not have to use ARIA's built-in NFV CSD04 Profile. You can copy the
files, change them locally, and use a regular "import" for them. (Just make
sure to set "tosca_definitions_version" to "tosca_simple_yaml_1_0"). If
I agree with you, DJ.
Until now, I think we wanted to make sure that the defaults would make
sense for most uses, but indeed I agree that
I suggest that we add another configuration parameter, "remote" (boolean)
to enforce this. If "remote" is not specified, we will use the heuristic.
If it is,
I'm not sure I see a use case of the new properties field that is newly
defined under substitution_mappings in v1.2.
The description is:
"A property mapping allows to map the property of a substituted node type
to a property definition or value (mapped as a constant value property
definition)
Feel free to change the wiki, Ran, to whatever name you find appropriate.
I think what Avia discovered is not new to us and actually doesn't solve
the problem, unfortunately. Let me go over what is clearly allowed and not
allowed in TOSCA, confusing because there are a few levels of inheritance
We indeed removed tosca.capabilities.nfv.VirtualStorage requirement from
the VDU.Compute node since this capability is not defined in csd04, but is
just mentioned by name.
The VirtualLinkable capability was in csd03, but removed from the TOSCA
spec in csd04. It seems as a leftover from csd03 that
