Posted by R-H on December 26, 2009 at 6:10pm
Are there any suggestions for how to be manage updates to the Mercury AMI. Is there a way to update to a more recent AMI instead of having to remove the current AMI and then install the latest.
As well, any suggestions for how to update to the latest Drupal/Pressflow core build? I see that Drupal recently updated to 6.15, but my Mercury install is at 6.14.
Thank you
Comments
None that im aware of .. Id
None that im aware of .. Id like to hear other folks methods. Im keeping backups of all my changed files and using EBS w/snapshots to store mysql and my aegir drupal webroot, I launch a new server, then merge my stuff into it when the time comes, when things look good terminate the old instance & ur done... Its not automated but easy enough, and if something goes wrong you have ur old instance and ebs drives to return to.
Im thinking having the whole thing be an ebs root store might be nice too as you can keep the old setups around longer and not be charged for them aside from cheap storage fees, haven't had time to test ebs root store just yet.
As for drupal/pressflow its the normal procedure as per the upgrade.txt, you can also use Aegir to manage such things if you so choose.
Bazaar
Just wondering if the changes between Mercury releases can be obtained via Bazaar as a simpler way to update Mercury as new releases arrive?
BCFG2
The combination of BCFG2 and launchpad should give us this option. Any change we make to our BCFG2 config will be uploaded to our launchpad page (https://code.launchpad.net/projectmercury). You can then look at the changes, and if you want to incorporate what we've changed, download the BCFG2 config file and BCFG2 will make the change to your system.
The BCFG2 config files can, of course, be downloaded via bzr:
bzr branch lp:projectmercury [folder]
Hope this helps,
Greg
--
Greg Coit
Systems Administrator
http://www.chapterthree.com