Wagn 0.13+deploy
Wagn 0.13 will require some special handling when it comes time to deploy on our servers.
Procedure
- prepare cluster
- deploy 'wagn_cluster' wagn.
- setup configs
- environment.rb, wagn.rb, amazon_s3.yml, database.yml
- copy from ang & modify.
- using apache config and wagn.rb files as source, build server map table (need more details)
ruby -r config/environment.rb -e 'MultihostMapping.create! :requested_host => "indecks.net", :canonical_host => "indecks.net", :wagn_name =>"wagn"'
- for each wagn:
- cap deploy:s3_setup # setup amazon bucket and config file.
- cap deploy # includes migration to upload images & files to amazon s3
- cap deploy:move_to_cluster # disables existing apache config, copies database into cluster
- For the first few: apache reload && test; if there are problems a2ensite ${wagn}.wagn.org to route back to working install.
Roadmap to release for multihost:
- √implement domain map, using nurture + wagn as test: www vs wagn.wagn.org
- ~restore wagn and nurture wagns to non-cluster, pre-s3 state.
(may be easiest to start over from pinz??) - √run pre-cluster benchmarks against ang, notes in performance & google doc
- √run above Wagn 0.13+deploy+procedure on ang. (note time) -- faster than I thought-- move_to_cluster is fairly fast, maybe an hour for all wagns. cluster preparation & first wagn to test it is easily an hour tho.
- √ rough tests.
- √run post-cluster benchmarks
- √notify Team for testing
- work on followup in parallel with testing
- further migrations within cluster
- deploy:cold to cluster
- standalone wagn setup
- handle problems from testing & rest of release preparation
- when everything else is ready do Release procedure, inserting Wagn 0.13+deploy+procedure at step 10.
PROBLEM: ROLLEDBACK
sandbox: logo broke
recentchangescamp: amazon bucket creation?/uploads failed
CARD-KEY_UNIQUE error in migrations
greencities
sandwagn
--Lewis Hoffman.....Fri Apr 10 17:43:34 -0700 2009