[
https://issues.apache.org/jira/browse/SLIDER-663?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14933519#comment-14933519
]
YONG FENG commented on SLIDER-663:
----------------------------------
Hi Gour,
The design doc mentioned use could customize the command to start, stop, check
status ... components of application as follows. However I did not find the
related info in user doc. Is it missed in user doc or has not been implemented
yet?
"commands": [
{
"command": {
"exec": "script for configure",
"name": "CONFIGURE",
"type": "PYTHON",
}
},
{
"command": {
"exec": "command for Start",
"name": "START",
"type": "SHELL",
}
}
]
Thanks,
> Make it easy to develop and deploy application packages that are essentially
> shell commands
> -------------------------------------------------------------------------------------------
>
> Key: SLIDER-663
> URL: https://issues.apache.org/jira/browse/SLIDER-663
> Project: Slider
> Issue Type: New Feature
> Components: agent-provider, app-package
> Affects Versions: Slider 0.60
> Reporter: Sumit Mohanty
> Assignee: Sumit Mohanty
> Priority: Critical
> Fix For: Slider 0.80
>
> Attachments: PackagingSimplificationandCreateEnhancements.pdf
>
>
> Slider app packages require several artifacts for completeness such as a
> metainfo.xml, a python script to read config and a python script for life
> cycle commands, a tarball, etc.
> A simple application can be modeled as a shell command or as a java
> application that just needs a jar and some system properties. So the
> application requirement can be summarized as:
> * a jar
> * a command
> * a small set of properties
> While it is possible to model these as an application package (e.g.
> memcached) it is also evident that there are a lot of common patterns that
> need to be duplicated.
> Slider should provide a way to pass these parameters in the create call
> itself rather than having to create a full application package.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
