You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@spark.apache.org by "Sean Owen (JIRA)" <ji...@apache.org> on 2015/03/28 18:38:52 UTC

[jira] [Resolved] (SPARK-6588) Private VPC's and subnets currently don't work with the Spark ec2 script

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

Sean Owen resolved SPARK-6588.
------------------------------
    Resolution: Duplicate

Also SPARK-5246, SPARK-6220. Have a look at the existing JIRAs and see if you can resolve one of them to this effect.

> Private VPC's and subnets currently don't work with the Spark ec2 script
> ------------------------------------------------------------------------
>
>                 Key: SPARK-6588
>                 URL: https://issues.apache.org/jira/browse/SPARK-6588
>             Project: Spark
>          Issue Type: Improvement
>          Components: EC2
>    Affects Versions: 1.3.0
>            Reporter: Michelangelo D'Agostino
>            Priority: Minor
>
> The spark_ec2.py script currently references the ip_address and public_dns_name attributes of an instance.  On private networks, these fields aren't set, so we have problems.
> The solution, which I've just finished coding up, is to introduce a --private-ips flag that instead refers to the private_ip_address attribute in both cases.



--
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