You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@mesos.apache.org by "Matei Zaharia (Updated) (JIRA)" <ji...@apache.org> on 2012/03/16 02:52:34 UTC
[jira] [Updated] (MESOS-146) EC2 scripts should find the latest AMI
from a known URL
[ https://issues.apache.org/jira/browse/MESOS-146?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Matei Zaharia updated MESOS-146:
--------------------------------
Attachment: MESOS-146.patch
Here's a small patch that does this. It also adds a second, bigger change: the ability to launch AMIs where most of the deployed scripts are already *on the machine image* as opposed to in a deploy directory in the user's Mesos installation. This is necessary because the OS versions, library locations (Java home, etc), and Mesos command line parameters will change in future AMIs. With this change, only a single script is uploaded with some environment variables, and the AMI configures the Hadoop config files, Mesos config files, etc based on those. This deployment mode is now marked as the "generic" OS type in the EC2 script, which is hopefully the last OS type we'll need to support
The use of latest AMIs isn't enabled by default in this patch, however, because we're still fairly far away from having a decent AMI. In particular, we need to make sure that the Mesos API is finalized and that Spark works with it, because most Mesos-EC2 users are Spark users. Once that happens we can commit a small config change that sets the default AMI to "latest" and the default OS to "generic". However, the changes do work right now with a new AMI that I created.
I also thought about removing support for the old AMIs, but I don't want to do it because I think that some users will want the old Mesos and Spark versions for a while, as well as the Hypertable support we had in some AMIs.
> EC2 scripts should find the latest AMI from a known URL
> -------------------------------------------------------
>
> Key: MESOS-146
> URL: https://issues.apache.org/jira/browse/MESOS-146
> Project: Mesos
> Issue Type: New Feature
> Components: ec2
> Reporter: Matei Zaharia
> Assignee: Matei Zaharia
> Priority: Minor
> Attachments: MESOS-146.patch
>
>
> This is a small change that would make the scripts easier to use and would let us "patch" the AMI after a release of Mesos comes out.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira