[
https://issues.apache.org/jira/browse/SPARK-5629?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14329940#comment-14329940
]
Florian Verhein commented on SPARK-5629:
----------------------------------------
Agree.
My point was more about avoiding tying `--machine-readable` to a particular
encoding, as adding any more later (if needed, and it appears from this
discussion that this is possible) would then make backwards compatibility
ugly/hard.
My vote would be for json too.
Aside: I saw some value in bash (export variables) because spark_ec2.py is
suited for use via its CLI, so scripting bash around it is natural. However on
further thought I don't think that would be a good idea, because a) its ugly to
implement, and b) once a script gets to the complexity of requiring these
variables, it should really be refactored into something more suitable like
python. Also the existing `--get-master` should be sufficient for most use
cases.
> Add spark-ec2 action to return info about an existing cluster
> -------------------------------------------------------------
>
> Key: SPARK-5629
> URL: https://issues.apache.org/jira/browse/SPARK-5629
> Project: Spark
> Issue Type: Improvement
> Components: EC2
> Reporter: Nicholas Chammas
> Priority: Minor
>
> You can launch multiple clusters using spark-ec2. At some point, you might
> just want to get some information about an existing cluster.
> Use cases include:
> * Wanting to check something about your cluster in the EC2 web console.
> * Wanting to feed information about your cluster to another tool (e.g. as
> described in [SPARK-5627]).
> So, in addition to the [existing
> actions|https://github.com/apache/spark/blob/9b746f380869b54d673e3758ca5e4475f76c864a/ec2/spark_ec2.py#L115]:
> * {{launch}}
> * {{destroy}}
> * {{login}}
> * {{stop}}
> * {{start}}
> * {{get-master}}
> * {{reboot-slaves}}
> We add a new action, {{describe}}, which describes an existing cluster if
> given a cluster name, and all clusters if not.
> Some examples:
> {code}
> # describes all clusters launched by spark-ec2
> spark-ec2 describe
> {code}
> {code}
> # describes cluster-1
> spark-ec2 describe cluster-1
> {code}
> In combination with the proposal in [SPARK-5627]:
> {code}
> # describes cluster-3 in a machine-readable way (e.g. JSON)
> spark-ec2 describe cluster-3 --machine-readable
> {code}
> Parallels in similar tools include:
> * [{{juju status}}|https://juju.ubuntu.com/docs/] from Ubuntu Juju
> * [{{starcluster
> listclusters}}|http://star.mit.edu/cluster/docs/latest/manual/getting_started.html?highlight=listclusters#logging-into-a-worker-node]
> from MIT StarCluster
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org
