Jan 20th, 2010, 03:10 PM
Cloud Foundry & Cloud Tools plugins - future?
I know this has been asked a little before, but I'm just wondering what the plan is for cloud foundry and cloud tools. When I first saw the cloud foundry plugin I thought that it was pretty awesome, but on digging deeper I see now that it only supports a single instance and only one deployment per Grails application (ie. I am unable to have a beta and a production deployment for instance - both on Amazon) - so it is pretty much useless for a real application. Sure, you can use the web GUI, but without any sort of programmatic API you can't deploy your application automatically (eg. through a continuous integration server)
So, I've fallen back to using simple Cloud Tools - which also looks pretty awesome on the surface. However, it doesn't look like it's been updated in a while and wasn't really surprised to see that it doesn't work with Grails 1.2 (and also has problems on 1.1 from the look of the issues list - haven't tried that myself though)
So, I've fallen back to using just the simple EC2Deploy from a Groovy script, just picking up a pre-built war uploaded to S3. However there are a few gaps - for instance EC2Deploy doesn't have support for other instance types (eg. MEDIUM) - sure I can patch the code, but it would be nice to know that this stuff might be added in future... would hate to see the open source project abandoned.
Also, I am still searching for where I can set the availability zone and startup script (similar to cloud foundry), I'm assuming that these are in ec2deployer somewhere - nothing in documentation on this
Sorry for all the questions - I think you have a great set of tools there, would just be good if we had a bit more visibility what's happening with it. Happy to contribute some doco or even code if needed - assuming cloud tools is going to continue.
Jan 21st, 2010, 05:40 AM
Ok - I worked out how to set the startup script - startupScript entry in the aws.properties file - it was right in front of me.
I'm still hunting for a way to set the availability zone - I can see it hidden in the depths of the cloud tools code, but still trying to track it out to the API.