[
https://issues.apache.org/jira/browse/WHIRR-150?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tom White updated WHIRR-150:
----------------------------
Attachment: WHIRR-150.patch
Here's a simple approach, which just writes information about the instances in
the cluster to a tab-delimited plain text file called
{{~/.whirr/<cluster>/instances}}. It should be easy to use unix tools to parse
this file and operate on instances in the cluster. Here's an example of the
file for a Hadoop cluster:
{noformat}
us-east-1/i-54cbe839 tt,dn ec2-67-202-4-185.compute-1.amazonaws.com
10.240.61.238
us-east-1/i-0ecbe863 jt,nn ec2-72-44-46-97.compute-1.amazonaws.com
10.240.62.31
{noformat}
The columns represent ID, roles, public address, private address.
> Allow retrieval of instance roles
> ---------------------------------
>
> Key: WHIRR-150
> URL: https://issues.apache.org/jira/browse/WHIRR-150
> Project: Whirr
> Issue Type: Improvement
> Components: core
> Reporter: Tom White
> Fix For: 0.3.0
>
> Attachments: WHIRR-150.patch
>
>
> After a cluster has been launched there is no way to access the roles running
> on particular instances. It would be useful to find the workers in a Hadoop
> cluster, so you could operate on them (e.g. restarting the daemons on them).
> How this is implemented is probably different for different clouds. E.g. on
> EC2 it could be accomplished using tags, on other platforms a local file
> might be sufficient, and a blobstore might be another way.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
