OASIS
TOSCA Implementer’s Recommendation:
Script Invocation Conventions
Frank Leymann
Thomas Spatzier
1. Introduction
The current interoperability use case based on SugarCRM provides simple scripts as Implementation Artifacts for lifecycle operations of Node Types. In order to invoke those scripts in an interoperable manner, conventions need to be followed by the different TOSCA container implementations.
For example, it has to be defined how references to individual scripts in a CSAR are made, how parameters are passed between a script and an invoker, how such parameters are identified in a service template etc..
Each script language will require the definition of such a “binding”. Because the interoperability use case only makes use of bash scripts, this recommendation at hand describes conventions for bash scripts only.
2. Script Artifact Definitions
The following Artifact Type called ScriptArtifact defines the type of artifacts that are scripts:
Script Artifact
The ScriptArtifactProperties element is defined as follows, specifying that a script always has a script language and a primary script:
The actual value of the ScriptLanguage element has impact on the invocation convention, parameters passing, etc. The PrimaryScript specifies the “entry script” to be invoked in cases where multiple files are referenced by an ArtifactTemplate (e.g. if the main script brings with it additional helper or library files).
By referring to the ScriptArtifact Artifact Type in its type attribute, the following defines an Artifact Template that is a script:
................
................
In order to avoid copyright disputes, this page is only a partial summary.
To fulfill the demand for quickly locating and searching documents.
It is intelligent file search solution for home and business.