Trying to move 2 intranet sites from a 1.0-boa-T-5 server, upgrade the server to Squeeze & BOA (edit)1.0.2 2.0.1 and then move the sites back.
As the sites are hosted under the satellite aegir instance, and the add server feature is only available to the aegir master instance, is it possible to escalate the features available to the single BOA satellite user, to add servers - and manage/migrate with them?
Am hoping to add a BOA VM server, then park the sites on the VM until the original tin gets upgraded. As ideally this is simpler than figuring out a more traditional, non-aegir-based export/import method.
Alternatively, maybe there is a way to move the sites from the satellite user to the aegir master instance user on the same machine - as the latter already has the add server feature, but is just missing the platforms. Then move them across AMI users, and end up without a satellite BOA user on the original tin? hmm
Would greatly appreciated any thoughts on what direction is best to pursue.
Thanks for all the progress on BOA, it is great to see this still going so strong. Done numerous BOA installations recently, and (barring user error) they have all worked perfectly!!
P.S. If this works, I can do it for my 'out of memory ing' linode as well. The linode hosts quite a few more complicated sites, would be great if this smaller scale experiment can be tweaked to work out.
P.P.S Best wishes to you and the project for 2012 :)
Comments
Comment #1
omega8cc commentedThe "Add server" feature is available in every Octopus instance - you just need to log in with root user (uid=1) instead of extra admin user, so you can see the admin menu with all features/options available.
For sites migration between Hostmaster instances (it doesn't matter if created by Barracuda or Octopus) you can use brilliant modules:
http://drupal.org/project/remote_import
http://drupal.org/project/hosting_remote_import
We will add both of them to BOA by default in the next release (this weekend).
Note that this new stuff allows for really easy migration only between remote Hostmasters, because Aegir expects both source and target system to use the same Aegir (system) user, while Octopus instances on the same server have all different users (and none of them have 'aegir' as a system user, obviously). I hope we will be able to modify this Aegir default logic and make it possible also to migrate sites between Octopus instances on the same machine - however it is also rather simple to do that manually in a few easy steps, anyway, just move their directories between Octopus instances - or Barracuda instance - and chmod them to use the new instance system user - so o1->o2 etc. Then re-verify new target platform, remove vhost on the old instance, re-verify discovered site and clear all caches - done. But it would be nice to be able to use the same workflow which is now fully possible (and tested by us in production already) between remote servers when their Aegir system users are the same (so aegir->aegir or o1->o1 etc.)
Comment #2
omega8cc commentedOh, and thanks for all good wishes and nice words! Thank you!
Comment #3
mysty commentedThis gives lots of avenues to explore, and as I was half expecting your approaches all seem a lot simpler and more elegant than the dead ends I was banging at.
Have been pootling about with ssh keys for the wrong user today, am bound to break something soon ;)
Thanks very much indeed!
Comment #4
mysty commentedguess I shouldn't have switched the category. Wasn't paying attention to the status change above. Switched back.
Comment #5
omega8cc commentedBOA will do that for you (SSH keys etc.) at least where it has an access, plus there will be a simple how-to included, very similar to standard docs on c.a.o
BTW. this is not a minor issue! :)
Thanks!
Comment #6
drurian commentedI take it it's not in stable yet?
Comment #7
omega8cc commentedNot yet. New stable BOA-2.0.2 should be released today, but it is not guaranteed that it will include above modules, since security upgrades (plus some related tests) have higher priority.
Comment #8
drurian commentedYou rock, thank you!
Comment #9
omega8cc commentedOh, and while we are at this: http://twitter.com/omega8cc/status/166722282532782080
Issues introduced by 6.24 core are pretty serious, so we are still testing patches: http://drupal.org/drupal-7.12#known-issues
Of course we will not wait for 6.25 ;) Instead we will release BOA-2.0.2 even if there will be still some not critical or major issues, because we already delayed our running upgrades on all servers, so we also need this stuff released *now* (in hours). In the meantime we have greatly improved BOA caching logic, added new (but tested already) features and fixed even more issues than expected to get fixed before this release.
Stay tuned!
Comment #10
drurian commentedAll these core updates that break things... It's a good thing I'm using Pressflow 6 (and still on 22 anyway).
By the way, trying to add remote import to BOA 2.0.1 produces errors, so I guess I'm gonna wait.
Comment #11
omega8cc commentedModules and how-to for migration between remote Aegir instances is now in head: http://drupalcode.org/project/octopus.git/commit/1d4e65e
Comment #13
drurian commentedAwesome! When's the next stable release?
Comment #14
omega8cc commentedWhen ready, probably next weekend, as we are waiting for next Drupal 7 release (expected this Wednesday) to include it after some testing.
Comment #15
drurian commentedApparently 7.14 has created some API related issues
http://engineeredweb.com/blog/drupal-7-14-api-incompatible-change/
Comment #16
omega8cc commentedYeah, that is why we use 7.14.1 (our repo with patches for fixing post-release known issues), however it will not help with all possible and not yet discovered issues, so we plan to publish 7.14.2 etc when there will be new important patches but not yet 7.15 released.
Comment #17
omega8cc commentedBOA-2.0.3 has been released!
Comment #18
drurian commentedI can get the list of the sites, but not import them.
Comment #19
omega8cc commentedPlease open new issue.
Comment #19.0
omega8cc commentedcorrected the Target BOA version to 2.0.1