remote db servers installs and upgrades support [#973910]

Comment #1

anarcat CreditAttribution: anarcat commented 16 November 2010 at 23:30

Status:	Active	» Needs work
Issue tags:		+aegir-0.4, +installer

dealing with installs first.

I have pushed the branch dev-multiserver-install for provision which does the first half (the backend).

for the second half, I wonder if I should check master_db or if we shouldn't just drop master_db and rely on the dbserver associated with the @hostmaster site?

either way, the frontend profile needs to be changed to create a new node if the dbserver is different from the master server.

this should be around hostmaster.profile:77.

Log in or register to post comments

Comment #2

anarcat CreditAttribution: anarcat commented 17 November 2010 at 00:10

i guess what I mean regarding master_db is that it doesn't seem to be the right way to pass that information around. In fact, I believe it *shouldn't* be passed to the frontend at all in this case. But maybe that would break the edition of this server.

Either way, I've always been quite unconfortable with storing the mysql root password(s) in the frontend DB. But that's a separate issue.

Log in or register to post comments

Comment #3

anarcat CreditAttribution: anarcat commented 17 November 2010 at 17:02

FWIW, i have setup a new hostmaster instance with the above patches and the only problem is that the DB server is not created in the frontend. The install is otherwise fully functional and manually creating the node fixes the problem completely.

Log in or register to post comments

Comment #4

anarcat CreditAttribution: anarcat commented 17 November 2010 at 17:55

Status:

Needs work

» Needs review

Created the branch on hostmaster, we now create the DB node if it's different from master. I just need some testing now.

Log in or register to post comments

Comment #5

anarcat CreditAttribution: anarcat commented 17 November 2010 at 19:28

So I have now completed the frontend: the last commit had a small bug... But now a node is created for the DB server in the frontend if it doesn't already exist.

I have tested this repeatedly with the following:

drush @hostmaster provision-delete
drush hostmaster-install --aegir_db_host=localhost --working-copy --client_email=anarcat@koumbit.org --makefile=/var/aegir/makefiles/aegir-koumbit.make --debug

I would like somebody to test this and the "normal" install. miguel? Once that is proven as working in most cases, mark this as RTBC and i'll merge on master.

Thanks!

Log in or register to post comments

Comment #6

sfyn CreditAttribution: sfyn commented 17 November 2010 at 20:15

I am attempting an install in a vbox with some unusual symptoms, using hostmaster-install:

drush hostmaster-install --aegir_db_host=localhost --working-copy --debug

And I am consistently generating the same errors:

PROVISION_SITE_INSTALLED [22 sec, 4.96 MB]                                         [error]
An error occurred at function : drush_provision_drupal_provision_install_validate  [error]
[22 sec, 4.96 MB]
Command dispatch complete [22 sec, 4.96 MB]                                           [notice]
Peak memory usage was 5.78 MB [22 sec, 4.96 MB]                                       [memory]
Running: /usr/bin/php /var/aegir/drush/drush.php --php=/usr/bin/php  @hostmaster     [command]
provision-verify --backend [22 sec, 4.87 MB]
The external command could not be executed due to an application error. [22.21 sec,[error]
4.9 MB]

Vhost configuration and such appear to be completing correctly, except that for whatever reason, I am consistently getting garbage characters inserted at the beginning of my server url.

Any thoughts?