Charles Reiss created MESOS-500:
-----------------------------------
Summary: EC2 scripts are out-of-date
Key: MESOS-500
URL: https://issues.apache.org/jira/browse/MESOS-500
Project: Mesos
Issue Type: Bug
Components: ec2
Reporter: Charles Reiss
Assignee: Charles Reiss
The EC2 scripts appear to be unable to deploy a recent version of Mesos.
They have the old github repo hardcoded instead of a reference to an Apache
repo. They also cannot build trunk even if they were pointed to it because
they, e.g., depend on frameworks/hadoop-0.20.2 existing in the Mesos source
tree. They, by default, point to an AMI which was last updated in December
2011. (The AMI is also presumably under a RAD Lab EC2 account, which is
probably not good for an Apache project.)
I think we should update the scripts to work on an empty Linux AMI, building
both Hadoop (with support for Hadoop MapReduce to run on Mesos) and a current
Mesos on it, and the option to start with an AMI that already has Hadoop+Mesos
and Mesos built.
Long-term, we might consider replacing the EC2 scripts with Apache Whirr
support for Mesos.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
