You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@whirr.apache.org by "Antonio Piccolboni (Created) (JIRA)" <ji...@apache.org> on 2011/12/09 18:07:39 UTC
[jira] [Created] (WHIRR-448) allow passing of arguments to script
in run-script
allow passing of arguments to script in run-script
--------------------------------------------------
Key: WHIRR-448
URL: https://issues.apache.org/jira/browse/WHIRR-448
Project: Whirr
Issue Type: Improvement
Components: cli
Affects Versions: 0.6.0
Environment: Any
Reporter: Antonio Piccolboni
As it is now, one can pass only a zero-argument script. Which means any slight variation of behavior desired of that script, you need to create a new script, either by hand or by some code generation machinery. Imagine a script to configure something, but the exact configuration depends on the version, only in details though. Wouldn't it be nice to be able to do whirr run-script setup-script 1.41.42 etc.? What is the alternative?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (WHIRR-448) allow passing of arguments to script
in run-script
Posted by "Andrei Savu (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WHIRR-448?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13272516#comment-13272516 ]
Andrei Savu commented on WHIRR-448:
-----------------------------------
I like it. Before committing we need to refactor to remove duplication.
> allow passing of arguments to script in run-script
> --------------------------------------------------
>
> Key: WHIRR-448
> URL: https://issues.apache.org/jira/browse/WHIRR-448
> Project: Whirr
> Issue Type: Improvement
> Components: cli
> Affects Versions: 0.6.0
> Environment: Any
> Reporter: Antonio Piccolboni
> Attachments: WHIRR-448.patch
>
>
> As it is now, one can pass only a zero-argument script. Which means any slight variation of behavior desired of that script, you need to create a new script, either by hand or by some code generation machinery. Imagine a script to configure something, but the exact configuration depends on the version, only in details though. Wouldn't it be nice to be able to do whirr run-script setup-script 1.41.42 etc.? What is the alternative?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Issue Comment Edited] (WHIRR-448) allow passing of
arguments to script in run-script
Posted by "Frank Scholten (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WHIRR-448?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13272706#comment-13272706 ]
Frank Scholten edited comment on WHIRR-448 at 5/10/12 8:18 PM:
---------------------------------------------------------------
Seems we have commands to manage the cluster as a whole and commands that perform actions on one or more nodes based on id and role. So far we have RunScriptCommand and soon the ExecCommand and UploadCommand.
How about pulling up buildFilterPredicate() and runScriptOutput() to AbstractClusterCommand?
was (Author: frankscholten):
Seems we have to commands to manage the cluster as a whole and commands that perform actions on one or more nodes based on id and role. So far we have RunScriptCommand and soon the ExecCommand and UploadCommand.
How about pulling up buildFilterPredicate() and runScriptOutput() to AbstractClusterCommand?
> allow passing of arguments to script in run-script
> --------------------------------------------------
>
> Key: WHIRR-448
> URL: https://issues.apache.org/jira/browse/WHIRR-448
> Project: Whirr
> Issue Type: Improvement
> Components: cli
> Affects Versions: 0.6.0
> Environment: Any
> Reporter: Antonio Piccolboni
> Attachments: WHIRR-448.patch
>
>
> As it is now, one can pass only a zero-argument script. Which means any slight variation of behavior desired of that script, you need to create a new script, either by hand or by some code generation machinery. Imagine a script to configure something, but the exact configuration depends on the version, only in details though. Wouldn't it be nice to be able to do whirr run-script setup-script 1.41.42 etc.? What is the alternative?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (WHIRR-448) allow passing of arguments to script
in run-script
Posted by "Andrei Savu (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WHIRR-448?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13272709#comment-13272709 ]
Andrei Savu commented on WHIRR-448:
-----------------------------------
bq. How about pulling up buildFilterPredicate() and runScriptOutput() to AbstractClusterCommand?
Reusing the code by moving to base class sounds good enough for now.
> allow passing of arguments to script in run-script
> --------------------------------------------------
>
> Key: WHIRR-448
> URL: https://issues.apache.org/jira/browse/WHIRR-448
> Project: Whirr
> Issue Type: Improvement
> Components: cli
> Affects Versions: 0.6.0
> Environment: Any
> Reporter: Antonio Piccolboni
> Attachments: WHIRR-448.patch
>
>
> As it is now, one can pass only a zero-argument script. Which means any slight variation of behavior desired of that script, you need to create a new script, either by hand or by some code generation machinery. Imagine a script to configure something, but the exact configuration depends on the version, only in details though. Wouldn't it be nice to be able to do whirr run-script setup-script 1.41.42 etc.? What is the alternative?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (WHIRR-448) allow passing of arguments to script
in run-script
Posted by "Frank Scholten (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WHIRR-448?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13272335#comment-13272335 ]
Frank Scholten commented on WHIRR-448:
--------------------------------------
This would be nice but I think it's difficult to implement.
> allow passing of arguments to script in run-script
> --------------------------------------------------
>
> Key: WHIRR-448
> URL: https://issues.apache.org/jira/browse/WHIRR-448
> Project: Whirr
> Issue Type: Improvement
> Components: cli
> Affects Versions: 0.6.0
> Environment: Any
> Reporter: Antonio Piccolboni
>
> As it is now, one can pass only a zero-argument script. Which means any slight variation of behavior desired of that script, you need to create a new script, either by hand or by some code generation machinery. Imagine a script to configure something, but the exact configuration depends on the version, only in details though. Wouldn't it be nice to be able to do whirr run-script setup-script 1.41.42 etc.? What is the alternative?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (WHIRR-448) allow passing of arguments to script
in run-script
Posted by "Frank Scholten (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WHIRR-448?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13272706#comment-13272706 ]
Frank Scholten commented on WHIRR-448:
--------------------------------------
Seems we have to commands to manage the cluster as a whole and commands that perform actions on one or more nodes based on id and role. So far we have RunScriptCommand and soon the ExecCommand and UploadCommand.
How about pulling up buildFilterPredicate() and runScriptOutput() to AbstractClusterCommand?
> allow passing of arguments to script in run-script
> --------------------------------------------------
>
> Key: WHIRR-448
> URL: https://issues.apache.org/jira/browse/WHIRR-448
> Project: Whirr
> Issue Type: Improvement
> Components: cli
> Affects Versions: 0.6.0
> Environment: Any
> Reporter: Antonio Piccolboni
> Attachments: WHIRR-448.patch
>
>
> As it is now, one can pass only a zero-argument script. Which means any slight variation of behavior desired of that script, you need to create a new script, either by hand or by some code generation machinery. Imagine a script to configure something, but the exact configuration depends on the version, only in details though. Wouldn't it be nice to be able to do whirr run-script setup-script 1.41.42 etc.? What is the alternative?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (WHIRR-448) allow passing of arguments to script
in run-script
Posted by "Frank Scholten (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WHIRR-448?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Frank Scholten reassigned WHIRR-448:
------------------------------------
Assignee: Frank Scholten
> allow passing of arguments to script in run-script
> --------------------------------------------------
>
> Key: WHIRR-448
> URL: https://issues.apache.org/jira/browse/WHIRR-448
> Project: Whirr
> Issue Type: Improvement
> Components: cli
> Affects Versions: 0.6.0
> Environment: Any
> Reporter: Antonio Piccolboni
> Assignee: Frank Scholten
> Attachments: WHIRR-448.patch
>
>
> As it is now, one can pass only a zero-argument script. Which means any slight variation of behavior desired of that script, you need to create a new script, either by hand or by some code generation machinery. Imagine a script to configure something, but the exact configuration depends on the version, only in details though. Wouldn't it be nice to be able to do whirr run-script setup-script 1.41.42 etc.? What is the alternative?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (WHIRR-448) allow passing of arguments to script
in run-script
Posted by "Frank Scholten (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WHIRR-448?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Frank Scholten updated WHIRR-448:
---------------------------------
Attachment: WHIRR-448.patch
Maybe not so difficult after all. Here is a command which executes a shell command on a single node or group of nodes.
If there is also a command for uploading a file then thuis allows for very flexible scripting. The downside is that we get more types of commands.
WDYT?
> allow passing of arguments to script in run-script
> --------------------------------------------------
>
> Key: WHIRR-448
> URL: https://issues.apache.org/jira/browse/WHIRR-448
> Project: Whirr
> Issue Type: Improvement
> Components: cli
> Affects Versions: 0.6.0
> Environment: Any
> Reporter: Antonio Piccolboni
> Attachments: WHIRR-448.patch
>
>
> As it is now, one can pass only a zero-argument script. Which means any slight variation of behavior desired of that script, you need to create a new script, either by hand or by some code generation machinery. Imagine a script to configure something, but the exact configuration depends on the version, only in details though. Wouldn't it be nice to be able to do whirr run-script setup-script 1.41.42 etc.? What is the alternative?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira