On Feb 19, 2013, at 1:30 AM, Paul Hoadley <pa...@logicsquad.net> wrote:
> On 19/02/2013, at 10:23 AM, Pascal Robert <prob...@macti.ca> wrote: > >> Le 2013-02-18 à 18:47, Paul Hoadley <pa...@logicsquad.net> a écrit : >> >>> I think they're just different. The instructions here: >>> >>> http://wiki.wocommunity.org/display/documentation/Deploying+on+Amazon+EC2 >>> >>> are about being able to bring an appserver up from scratch using scripts. >>> Eyeballing that page right now, it might be a little incomplete and/or >>> light on detail, but it's certainly an approach I like, for what that's >>> worth. With a bit of effort, you can turn wo-install.sh into something >>> just right for your own purposes—we've evolved it into something that >>> allows us to bring up an appserver on a new instance with a single local >>> command without even needing to log in. >> >> What are the advantages of doing this over building a template or a AMI? > > They're just different points along a bootstrapping spectrum. WOlastic was > way up the pre-baked end, where (if I recall correctly—I never tried it) the > idea was you'd fire up an instance from the WOlastic AMI and you'd be > essentially ready to go. This gives basically no flexibility (all the myriad > arbitrary choices are fixed in the AMI), and would require creating a new AMI > for every software upgrade or security fix you wanted to make. Your approach > with packages is somewhere in the middle, though I presume you'll > periodically find yourself needing to update those packages as well. And > then the scripted approach is heading towards the other end, starting with a > vanilla AMI like Amazon Linux, and adding all the pieces on the fly, > including grabbing the latest wotaskd and JavaMonitor from the community > build server. There are trade-offs at every move along the spectrum, and > whether you see them as advantages or disadvantages will depend on your > particular business case. > > > -- > Paul Hoadley > http://logicsquad.net/ Would there be merit to the community supporting a public WebObjects AMI? There's a small cost (which I've not estimated), but if we had an AMI, I could play instead of work for two hours today! _______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-deploy mailing list (Webobjects-deploy@lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/webobjects-deploy/archive%40mail-archive.com This email sent to arch...@mail-archive.com
