Mailing-List: contact mahout-user-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: mahout-user@lucene.apache.org
Received-SPF: pass (nike.apache.org: domain of gsiasf@gmail.com designates
 209.85.211.185 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=sender:content-type:mime-version:subject:from:in-reply-to:date
         :content-transfer-encoding:message-id:references:to:x-mailer;
        b=pRyMTEA+KQdZVs82X66gb/YrtykKhzmGsHfD0z4b2hAQlNCDPSMiByP6DE3IgmnDEl
         MDrET/lEF8qQ7SWBFM41iIGc21qxZ6GVdysB+cvVubd6awAXj+yWprDnBNUYi+XynXwl
         3RoxB9YLMWS/ds+jNd6QFFAqDIs8UT2NsJpEY=
Sender: Grant Ingersoll <gsiasf@gmail.com>
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1077)
Subject: Re: Re : Good starting instance for AMI
From: Grant Ingersoll <gsingers@apache.org>
In-Reply-To: <c7d45fc71001181215u2d1fab83ibe34cb08d3ffef36@mail.gmail.com>
Date: Mon, 18 Jan 2010 19:42:54 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <5DEEA81F-7EA8-4024-AC85-88E5F4DBFA08@apache.org>
References: <629059.62746.qm@web26303.mail.ukl.yahoo.com>
 <A4782AD1-9693-459F-B883-DCE2A535F9A2@apache.org>
 <c7d45fc71001181215u2d1fab83ibe34cb08d3ffef36@mail.gmail.com>
To: mahout-user@lucene.apache.org


On Jan 18, 2010, at 3:15 PM, Ted Dunning wrote:

> Is there an important difference between creating an existing AMI or =
using
> an existing AMI with a startup script that populates everything from =
S3?
>=20
> Building an AMI takes a few hours of time and is a total pain in the =
butt.
> My eventual result was that I didn't need to do it at all.
>=20
> I found that I had roughly three levels of variation in my production
> systems:
>=20
> - the OS
> - the infrastructural components like java, hadoop and zookeeeper
> - the application that I wanted to run
>=20
> My initial thought was that the AMI should cover the first two aspects =
of
> variability.  But I also found that I wanted to change the version of =
the
> infrastructure stuff fairly often in development of the AMI and not
> infrequently in production.
>=20
> For Mahout customers, I would imagine that there is a reasonable =
amount of
> variability in desired OS (Ubuntu versus Redhat versus Centos at =
least), JDK
> and Hadoop versions. =20

I only see a need for two: the version in trunk and the one in latest =
release.

This is all well and good, but I have yet to see anyone say:  here's the =
AMI, the download script and the instructions.  So I'm just going to go =
ahead with what I think is useful for my needs, document it, and put it =
up there for people to use or not.  If anything, it will be useful for =
me to do it since I've never setup a Hadoop cluster on EC2 before. =20

-Grant=