Github user sigmoidanalytics commented on the pull request:
https://github.com/apache/spark/pull/681#issuecomment-63060313
LibCloud looks decent for launching machine across datacenters providers,
but to modify build scripts to either do installation from scratch (means
longer install times than spark ec2) or keep slightly baked
AMI's/equivalents in each datacenter of each provider. Both are sizable
amount of effort.
If the purpose of script is for development support then we can choose some
locations & start there before going all out. Another possibility is to
keep this all-datacenter script separate with longer launch times on vanila
AMI for those who want to use other datacenters apart from those supported
by spark-ec2. That way general launch times dont increase & still a
solution for those who dont want to use AWS.
On Fri, Nov 14, 2014 at 4:39 PM, Andrew Ash <[email protected]>
wrote:
> Correction, please use SPARK-1422
>
> â
> Reply to this email directly or view it on GitHub
> <https://github.com/apache/spark/pull/681#issuecomment-63045363>.
>
--
Regards,
Mayur Rustagi
Ph: +1 (760) 203 3257
http://www.sigmoidanalytics.com
@mayur_rustagi <http://www.twitter.com/mayur_rustagi>
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
