Difference between revisions of "Murano/Documentation/How to create application package"
< Murano | Documentation
(→Step1. Prepare installation scripts) |
(→Step1. Prepare installation scripts) |
||
Line 4: | Line 4: | ||
===Step1. Prepare installation scripts=== | ===Step1. Prepare installation scripts=== | ||
− | It could be any type of scripts which will execute commands and install application components as the result. They called ''execution scripts'. | + | It could be any type of scripts which will execute commands and install application components as the result. They called ''execution scripts''. One of the scripts should be an entry point and should be specified in a resource template file in a ''Scripts''. Besides this ''Scripts'' section the following sectiont must be presented in a resource template file: |
* FormatVersion - version if Murano metadata definition | * FormatVersion - version if Murano metadata definition | ||
* Version - version of template definition syntax | * Version - version of template definition syntax |
Revision as of 13:29, 11 April 2014
Contents
Composing application package manual
Murano is Application catalog that supports types of applications. To deploy an application with the Murano This document intends to make composing application packages easily.
Step1. Prepare installation scripts
It could be any type of scripts which will execute commands and install application components as the result. They called execution scripts. One of the scripts should be an entry point and should be specified in a resource template file in a Scripts. Besides this Scripts section the following sectiont must be presented in a resource template file:
- FormatVersion - version if Murano metadata definition
- Version - version of template definition syntax
- Name - name of resource
- Parameters - parameters required by execution scripts
- Body - YAQL statement ...
- Scripts - provide section, that can be returned from Body with detailed information about execution process, such as Type, EntryPoint and required Files. Note that specified files should be exist under Resource/scripts directory and path to them can be nested.
Example"
FormatVersion: 2.0.0 Version: 1.0.0 Name: Deploy Telnet Parameters: appName: $appName Body: | return deploy(args.appName).stdout Scripts: deploy: Type: Application Version: 1.0.0 EntryPoint: deployTelnet.sh Files: - <installer.sh> - <common.sh> Options: captureStdout: true captureStderr: false
Step2. Prepare MuranoPL class definitions
MuranoPL classes control application deployment workflow execution. Full information about MuranoPL classes can be found here.