I've had a fairly massive hack attack over the last couple of days on automating the instantiation and startup of a Terracotta EC2 cluster. Here's what I've been working on:
https://svn.terracotta.org/repo/forge/projects/labs/ec2utils/trunk It's still kind of broken right now (the current problem is a NPE in TCPProxy that I'm using as a load balancer a la the spring webflow sample) and it's not done by any stretch of the imagination, but some of you (Geert, especially) have expressed interest in working on this kind of thing. Well... I've made my start. It's still pretty experimental, and I'm amenable to throwing it all away and starting from scratch with new ideas. But, I know a bit more about the issues involved now than I did when I started. I documented some of the issues in FAQ.TXT and TODO.TXT, but I haven't fully documented the thing. Also, there's no public AMI, yet. There's a number of thorny things to work out (licensing and security, not the least) before we pull the trigger on that. Anyway... fresh hot experimental ec2 goo, come and get it. --Orion _______________________________________________ tc-dev mailing list [email protected] http://lists.terracotta.org/mailman/listinfo/tc-dev
