JAR Desc CSAR Notes JAR 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 ID: 761483
Download Presentation The PPT/PDF document "JAR Desc CSAR Notes JAR A package fil..." is the property of its rightful owner. Permission is granted to download and print the materials on this web site for personal, non-commercial use only, and to display it on your personal computer provided you do not modify the materials and that you retain all copyright notices contained in the materials. By downloading content from our website, you accept the terms of this agreement.
JAR Desc CSAR Notes JAR 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. CSAR 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 Version string Currently, the TOSCA metafile version is tied to the TOSCA spec. version Future work would separate out the CSAR specification into its own independenly versioned entity. 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). E.g., Car (type) E.g., in NFV this is the VNF “Node Type” 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> (name TBD; substitutable-definitions?) [0,N] Not applicable to TOSCA at this time. Future discussion (YAML list) E.g., Ford Truck, Toyota Camry, etc. E.g., in NFV these could be the impls. CSAR/STs