Hi Matt, This is interesting. I have a few observations (looking from the perspective of our needs for deriving a VDU node for NFV profile): 1. tosca.capabilities.compute derives from tosca.capabilities.container - but tosca.capabilities.container is empty. What is the point - do you expect to add properties later? 2. tosca.nodes.container node does not exist. There is a tosca.nodes.container.Runtime, a tosca.nodes.container. Application. Is this on purpose, or is something more to come? 3. tosca.nodes.compute derives from tosca.nodes.Abstract.Compute, not from tosca.nodes.container (correct, since tosca.nodes.container is not defined, as per above). 4. tosca.nodes.Abstract.Compute does not have the tosca.capabilities.container, but the tosca.capabilities.compute. In essence, the changes may address a set of issues, but not the issues we have in NFV profile with the VDU.Compute node (which at present is derived from tosca.nodes.compute, with a lot of deprecations and overlaps of capabilities, because what we need to add). Even if we were to derive from tosca.nodes.Abstract.Compute, while there are less deprecations, we still have the issue with inheriting the tosca.capabilities.compute which creates duplication with the capabilities we need to add. I would have been inclined to derive VDU from tosca.nodes.container, if such node would have been defined. Best regards, Michael On Tue, Dec 5, 2017 at 3:57 PM, Matthew Rutkowski <
mrutkows@us.ibm.com > wrote: Document Name : TOSCA-Simple-Profile-YAML-v1. 2-wd02-rev05-csd01-candidate- clean.docx No description provided. Download Latest Revision Public Download Link Submitter : Mr. Matthew Rutkowski Group : OASIS Topology and Orchestration Specification for Cloud Applications (TOSCA) TC Folder : Working Documents Date submitted : 2017-12-05 12:56:50 -- Michael Brenner, Chief Architect NFV M: +1-732-895-5772
http://getcloudify.org @cloudifysource