Mix and mingle solo with EY slices.
We have an app in beta hosted on EY and aren't yet in production. We decided to do a substantial extra round of development. Currently we don't have a staging or testing environment we would like to add that but given the current economics are cost conscious so I wanted to have a solo environment for this new development release without disrupting the current users on the beta which is running on an EY cluster.
So the first part of the question is will I be able to just drop a solo in to host our development environment just by dropping it into the staging task in deploy.rb?
I envisaged having a development solo instance and a staging solo instance so the staging is always there as a mirror of production so we can stage maintenance to the production environment. But when we are doing larger scale development we would like to have a solo instance fired up for say a month or 2 then drop it for a couple etc. Is it ok to do this, and is there any way to persist the /data across the development iterations?
Thanks.
Comments are currently closed for this discussion. You can start a new one.
2 Posted by pbiegaj on 04 Feb, 2009 01:42 AM
Hey James, So the deal is that if you have one environment and say you call it Staging and another that you call Development (names don't matter in terms of behavior). If you destroy that instance at some point, and don't explicitly delete the volumes that were attached to that instance in that environment, then the next time you bring up an instance in that environment it will remount those volumes from the previous instance. You will be charged storage costs for the volumes, but they aren't very great, can't recall them off the top of my head. Hopefully this answers your question, if not feel free to ping me again or just into IRC freenode in the room ey-solo as a bunch of us devs hang out there throughout the day. Cheers,
-Piotr Biegaj
3 Posted by James McCarthy on 04 Feb, 2009 02:24 AM
Thanks Piotr. I'm sold. Thanks for the irc tip too.