Hey, that could be a good first step, but I personally think that we should provide something with more meat, ie. solve the deployment and architecture-related problems that are related to EC2. An example of this is creating a tomcat session clustering instance that has a simple config file with the location and deployment characteristics of the webapps that need to be active after a node starts (possibly by integrating with S3). Another thing to consider is providing a solution for backing up the TC server's data to S3 since Amazon doesn't guarantee that data on the EC2 instance's virtual disk is preserved over system failures and such. This of course also should consider a restoration process for when the worse does indeed come to happen.
In a second phase I'd love to integrate some system monitoring wachdog that is able to automatically start and stop EC2 instances, based on the load of the cluster. What do you think? On 12 Sep 2007, at 20:49, Orion Letizi wrote: > I found a public AMI of CentOS that I'm using as a starting point. > I was going to have it start up some of the web demos on boot... > > --Orion -- Geert Bevin Terracotta - http://www.terracotta.org Uwyn "Use what you need" - http://uwyn.com RIFE Java application framework - http://rifers.org Music and words - http://gbevin.com _______________________________________________ tc-dev mailing list [email protected] http://lists.terracotta.org/mailman/listinfo/tc-dev
