You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@whirr.apache.org by "Andrei Savu (Updated) (JIRA)" <ji...@apache.org> on 2012/01/20 01:42:41 UTC
[jira] [Updated] (WHIRR-479) ScriptBasedClusterAction should allow
filtering by role and instance-id
[ https://issues.apache.org/jira/browse/WHIRR-479?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andrei Savu updated WHIRR-479:
------------------------------
Attachment: WHIRR-479.patch
First iteration on this one. I have done a bit of manual testing on aws-ec2 and everything seems to be working to be fine.
I'm planning to add a bunch of dry run tests. Do you think that should be enough or do we also need integration tests?
> ScriptBasedClusterAction should allow filtering by role and instance-id
> -----------------------------------------------------------------------
>
> Key: WHIRR-479
> URL: https://issues.apache.org/jira/browse/WHIRR-479
> Project: Whirr
> Issue Type: Improvement
> Components: core
> Reporter: Andrei Savu
> Assignee: Andrei Savu
> Fix For: 0.7.1
>
> Attachments: WHIRR-479.patch
>
>
> Configure / Start / Stop / Cleanup are all based on ScriptBasedClusterAction. In order to make them even more useful we should be able to filter the nodes by role or by ID. E.g. ./bin/whirr stop-services --config ... --roles hadoop-datanode --instance-id us-east-1/i-231235
--
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