description no The optional description string for the associated named operation. implementation no The optional implementation artifact name (e.g., a script file name within a TOSCA CSAR file). inputs no list of The optional list of input properties definitions (i.e., parameter definitions) for operation definitions that are within TOSCA Node or Relationship Type definitions. This includes when operation definitions are included as part of a Requirement definition in a Node Type. no list of The optional list of input property assignments (i.e., parameters assignments) for operation definitions that are within TOSCA Node or Relationship Template definitions. This includes when operation definitions are included as part of a Requirement assignment in a Node Template. The following is the list of recognized keynames to be used with the implementation keyname within a TOSCA operation definition: Keyname Type Description primary no The optional implementation artifact name (i.e., the primary script file name within a TOSCA CSAR file). dependencies no list of The optional ordered list of one or more dependent or secondary implementation artifact name which are referenced by the primary implementation artifact (e.g., a library the script installs or a secondary script). Grammar Operation definitions have the following grammars: Short notation The following single-line grammar may be used when only an operation’s implementation artifact is needed: <>: <> Extended notation for use in Type definitions The following grammar may be used in Node or Relationship Type definitions when additional information about the operation is needed: <>: description: <> implementation: <> inputs: <>
definitions/tosca_elk.yaml This TOSCA.meta file indicates its simplified TOSCA Simple Profile structure by means of the keyword with value 1.1. The Entry-Definitions keyword points to a TOSCA definitions YAML file with the name tosca_elk.yaml which is contained in a directory called definitions within the root of the CSAR file. Archive without TOSCA-Metadata In case the archive doesn’t contains a TOSCA-Metadata directory the archive is required to contains a single YAML file at the root of the archive (other templates may exits in sub-directories). This file must be a valid TOSCA definitions YAML file with the additional restriction that the metadata section (as defined in 3.9.3.2) is required and template_name and template_version metadata are also required. processors should recognized this file as being the CSAR Entry-Definitions file. The CSAR-Version is defined by the template_version metadata section. The Created-By value is defined by the template_author metadata. Example The following represents a valid TOSCA template file acting as the CSAR Entry-Definitions file in an archive without TOSCA-Metadata directory. tosca_definitions_version: tosca_simple_yaml_1_1 metadata: template_name: my_template template_author: OASIS TOSCA TC template_version: 1.0
interfaces: Standard: inputs: db_root_password: { get_property: [ mysql_dbms, root_password ] } create: configure: .sh webserver: type: requirements: - host: server interfaces: Standard: create: server: type: capabilities: host: properties: disk_size: 10 GB num_cpus: { get_input: cpus } mem_size: 4096 MB os: properties: architecture: x86_64 type: linux distribution: fedora version: 17.0 outputs: website_url: description: URL for Wordpress wiki. { get_attribute: [server, public_address] } Sample scripts the referenced implementation scripts in the example above would have the following contents