[jira] [Commented] (SLIDER-663) Make it easy to develop and deploy application packages that are essentially shell commands
[ https://issues.apache.org/jira/browse/SLIDER-663?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14942863#comment-14942863 ] YONG FENG commented on SLIDER-663: -- Any suggestion? Tnanks > 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)
[jira] [Commented] (SLIDER-663) Make it easy to develop and deploy application packages that are essentially shell commands
[ https://issues.apache.org/jira/browse/SLIDER-663?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14942869#comment-14942869 ] Gour Saha commented on SLIDER-663: -- [~sumitmohanty] can you please comment on this? > 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)
[jira] [Commented] (SLIDER-663) Make it easy to develop and deploy application packages that are essentially shell commands
[ https://issues.apache.org/jira/browse/SLIDER-663?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14933495#comment-14933495 ] Gour Saha commented on SLIDER-663: -- I think this is what you are looking for - https://slider.incubator.apache.org/docs/slider_specs/simple_pkg.html It has reference from the [Creating App Packages|https://slider.incubator.apache.org/docs/slider_specs/index.html] page. > 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)
[jira] [Commented] (SLIDER-663) Make it easy to develop and deploy application packages that are essentially shell commands
[ https://issues.apache.org/jira/browse/SLIDER-663?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=1492#comment-1492 ] YONG FENG commented on SLIDER-663: -- Hi Sumit, Is there a user doc for SLIDER-663 like Docker based application in https://slider.incubator.apache.org/docs/slider_specs/application_pkg_docker.html? Or user could treat the design doc as the user doc? 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)
[jira] [Commented] (SLIDER-663) Make it easy to develop and deploy application packages that are essentially shell commands
[
https://issues.apache.org/jira/browse/SLIDER-663?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=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)
[jira] [Commented] (SLIDER-663) Make it easy to develop and deploy application packages that are essentially shell commands
[ https://issues.apache.org/jira/browse/SLIDER-663?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14933501#comment-14933501 ] YONG FENG commented on SLIDER-663: -- Thanks Gour. I don't know why I missed it :-) > 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)
[jira] [Commented] (SLIDER-663) Make it easy to develop and deploy application packages that are essentially shell commands
[ https://issues.apache.org/jira/browse/SLIDER-663?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14368452#comment-14368452 ] ASF subversion and git services commented on SLIDER-663: Commit 704e81363a72444f0d27b6fe3ab43d46b7791231 in incubator-slider's branch refs/heads/develop from [~sumitmohanty] [ https://git-wip-us.apache.org/repos/asf?p=incubator-slider.git;h=704e813 ] SLIDER-663. Make it easy to develop and deploy application packages that are essentially shell commands (part-I) 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: Task Components: agent-provider, app-package Affects Versions: Slider 0.60 Reporter: Sumit Mohanty Assignee: Sumit Mohanty Priority: Critical 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)
[jira] [Commented] (SLIDER-663) Make it easy to develop and deploy application packages that are essentially shell commands
[ https://issues.apache.org/jira/browse/SLIDER-663?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14368453#comment-14368453 ] ASF subversion and git services commented on SLIDER-663: Commit 210a1c94ca347380f7b22fba807c12dc1e30deff in incubator-slider's branch refs/heads/develop from [~sumitmohanty] [ https://git-wip-us.apache.org/repos/asf?p=incubator-slider.git;h=210a1c9 ] SLIDER-663. Make it easy to develop and deploy application packages that are essentially shell commands (part-II) 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: Task Components: agent-provider, app-package Affects Versions: Slider 0.60 Reporter: Sumit Mohanty Assignee: Sumit Mohanty Priority: Critical 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)
[jira] [Commented] (SLIDER-663) Make it easy to develop and deploy application packages that are essentially shell commands
[ https://issues.apache.org/jira/browse/SLIDER-663?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14366619#comment-14366619 ] ASF subversion and git services commented on SLIDER-663: Commit 704e81363a72444f0d27b6fe3ab43d46b7791231 in incubator-slider's branch refs/heads/feature/package_simplification_II from [~sumitmohanty] [ https://git-wip-us.apache.org/repos/asf?p=incubator-slider.git;h=704e813 ] SLIDER-663. Make it easy to develop and deploy application packages that are essentially shell commands (part-I) 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: Task Components: agent-provider, app-package Affects Versions: Slider 0.60 Reporter: Sumit Mohanty Assignee: Sumit Mohanty Priority: Critical 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)
[jira] [Commented] (SLIDER-663) Make it easy to develop and deploy application packages that are essentially shell commands
[ https://issues.apache.org/jira/browse/SLIDER-663?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14219522#comment-14219522 ] Steve Loughran commented on SLIDER-663: --- + a URL to download a tarball from. ...you could have a meta-app-package whose app config params included URL, commands etc. Hard part would be config generation. 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: Task Components: agent-provider, app-package Affects Versions: Slider 0.60 Reporter: Sumit Mohanty Assignee: Sumit Mohanty Priority: Critical 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)
