Keyname Required Type Description capability no The optional reserved keyname used to provide the name of either a: Capability definition within a target node template that can fulfill the requirement. Capability Type that the provider will use to select a target node template to fulfill the requirement at runtime. node no The optional reserved keyname used to identify the target node of a relationship. specifically, it is used to provide either a: Node Template name that can fulfill the target node requirement. Node Type name that the provider will use to select a node template to fulfill the requirement at runtime. relationship no The optional reserved keyname used to provide the name of either a: Relationship Template to use to relate the source node to the (capability in the) target node when fulfilling the requirement. Relationship Type that the provider will use to select a relationship template to relate the source node to the target node at runtime. node_filter no The optional filter definition that TOSCA orchestrators or providers would use to select a type-compatible target node that can fulfill the associated abstract requirement at runtime. The following is the list of recognized keynames for a TOSCA requirement assignment’s relationship keyname which is used when Property assignments need to be provided to inputs of declared interfaces or their operations: Keyname Required Type Description type no The optional reserved keyname used to provide the name of the Relationship Type for the requirement assignment’s relationship keyname. properties no list of The optional reserved keyname used to reference declared interface definitions of the corresponding Relationship Type in order to provide Property assignments for these interfaces or operations of these interfaces. Grammar Named requirement assignments have one of the following grammars: Short notation: The following single-line grammar may be used if only a concrete Node Template for the target node needs to be declared in the requirement: <>: <> This notation is only valid if the corresponding Requirement definition in the Node Template’s parent Node Type declares (at a minimum) a valid Capability Type which can be found in the declared target Node Template. A valid capability definition always needs to be provided in the requirement declaration of the source node to identify a specific capability definition in the target node the requirement will form a TOSCA relationship with.
Keyname Required Type Description capability no The optional reserved keyname used to provide the name of either a: Capability definition within a target node template that can fulfill the requirement. Capability Type that the provider will use to select a target node template to fulfill the requirement at runtime. node no The optional reserved keyname used to identify the target node of a relationship. specifically, it is used to provide either a: Node Template name that can fulfill the target node requirement. Node Type name that the provider will use to select a node template to fulfill the requirement at runtime. relationship no The optional reserved keyname used to provide the name of either a: Relationship Template to use to relate the source node to the (capability in the) target node when fulfilling the requirement. Relationship Type that the provider will use to select a relationship template to relate the source node to the target node at runtime. node_filter no The optional filter definition that TOSCA orchestrators or providers would use to select a type-compatible target node that can fulfill the associated abstract requirement at runtime. The following is the list of recognized keynames for a TOSCA requirement assignment’s relationship keyname which is used when Property assignments need to be provided to inputs of declared interfaces or their operations: Keyname Required Type Description type no The optional reserved keyname used to provide the name of the Relationship Type for the requirement assignment’s relationship keyname. properties no list of The optional reserved keyname used to reference declared interface definitions of the corresponding Relationship Type in order to provide Property assignments for these interfaces or operations of these interfaces. Grammar Named requirement assignments have one of the following grammars: Short notation: The following single-line grammar may be used if only a concrete Node Template for the target node needs to be declared in the requirement: <>: <> This notation is only valid if the corresponding Requirement definition in the Node Template’s parent Node Type declares (at a minimum) a valid Capability Type which can be found in the declared target Node Template. A valid capability definition always needs to be provided in the requirement declaration of the source node to identify a specific capability definition in the target node the requirement will form a TOSCA relationship with.
TOSCA-Simple-Profile-YAML-v1.1-csprd02.docx