[
https://issues.apache.org/jira/browse/WHIRR-195?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12987762#action_12987762
]
Andrei Savu commented on WHIRR-195:
-----------------------------------
With an experimental version of WHIRR-199:
{code}
$ ./bin/whirr
Usage: whirr COMMAND [ARGS]
where COMMAND may be one of:
version Print the version number and exit.
launch-cluster Launch a new cluster running a service.
destroy-cluster Terminate and cleanup resources for a running cluster.
list-cluster List the nodes in a cluster.
Available roles:
cassandra
hadoop-namenode
hadoop-datanode
hadoop-jobtracker
hadoop-tasktracker
zookeeper
hbase-master
hbase-regionserver
hbase-restserver
hbase-avroserver
hbase-thriftserver
{code}
Should I add some sort of grouping based on the role prefix?
> Display available roles instead of service names when running ./bin/whirr
> -------------------------------------------------------------------------
>
> Key: WHIRR-195
> URL: https://issues.apache.org/jira/browse/WHIRR-195
> Project: Whirr
> Issue Type: Improvement
> Components: cli
> Reporter: Andrei Savu
> Priority: Minor
> Attachments: WHIRR-195.patch
>
>
> Now that service-name is optional I believe that we should display a list of
> the available roles (with a small description) instead of service names.
> Similar to:
> {code}
> $ ./bin/whirr
> Usage: whirr COMMAND [ARGS]
> where COMMAND may be one of:
> version Print the version number and exit.
> launch-cluster Launch a new cluster running a service.
> destroy-cluster Terminate and cleanup resources for a running cluster.
> list-cluster List the nodes in a cluster.
> Available roles for instances:
> nn hadoop name node
> jt hadoop job trackers
> ...
> {code}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
