1. TOSCA-Metadata (directory )
JAR
Desc
CSAR
Notes
A package file format typically used to aggregate many Java class files and associated metadata and resources (text, images, etc.) into one file for distribution.
JAR files are archive files that include a Java-specific manifest file. They are built on the ZIP format and typically have a .jar file extension.
TOSCA Simple Profile definitions along with all accompanying artifacts (e.g. scripts, binaries, configuration files) can be packaged together in a CSAR file
META-INF
There can be only one manifest file in an archive and it must be at that location.
TOSCA-Metadata (directory )
contains the TOSCA.meta metadata file that provides entry information for a TOSCA orchestrator processing the CSAR file.
Manifest.mf
A manifest file is a metadata file contained within a JAR.
TOSCA.meta
Provides entry information for a TOSCA orchestrator processing the CSAR file
Manifest-Version
(e.g., 1.0)
conforms to version 1.0 of the manifest specification.
TOSCA-Meta-File-Version
Note: We do not have a separate CSAR spec.
should we?
rules for version increments?
Main-Class:
(e.g., com.example.MyClassName)
the JVM (for an exec. JAR)needs to know the application's entry point.
An entry point is any class with a public static void main(String[] args) method
Entry-Definitions
[0,1]
any TOSCA definitions files besides the one denoted by the Entry-Definitions keyword can be found by a TOSCA orchestrator by processing respective imports statements in the entry definitions file (or in recursively imported files).
Class-Path:
(e.g., . pkg1.jar path/to/pkg2.jar)
used to specify all the classes that must be loaded for an application to be able to run.
? <other-definitions>
[0,N]