[jira] [Resolved] (SPARK-5627) Enhance spark-ec2 to return machine-readable output

["Sean Owen (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/SPARK-5627?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Sean Owen resolved SPARK-5627.
------------------------------
    Resolution: Won't Fix

I'm guessing this is WontFix given the lack of activity, and that EC2 support is finally moving out of Spark

> Enhance spark-ec2 to return machine-readable output
> ---------------------------------------------------
>
>                 Key: SPARK-5627
>                 URL: https://issues.apache.org/jira/browse/SPARK-5627
>             Project: Spark
>          Issue Type: Improvement
>          Components: EC2
>            Reporter: Nicholas Chammas
>            Priority: Minor
>
> There are some cases where users may want to programmatically invoke {{spark-ec2}} to manage clusters. For example, we might want to programmatically launch clusters as part of a {{spark-perf}} run and then destroy them once the performance testing is done.
> We should support some of these use cases, perhaps with the explicit caveat that we are not offering API stability for this access.
> A good way to offer this might be to follow [the Packer model|https://www.packer.io/docs/command-line/machine-readable.html] and add a {{--machine-readable}} option to spark-ec2.
> It would be a lot of work to support such an option for everything that spark-ec2 does, and it probably isn't relevant for most things anyway.
> Still, we can phase it in for select things like [returning the version|SPARK-5628] and [describing clusters|SPARK-5629].



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org