Add docs on how to setup the whole process [#1847838]

Here is what I know!

1) Add remote_import to your provision drush command like explained in the README.
2) Add hosting_remote_import to your aegir frontend

Here is what I like to know!

3) Setup a server - What options should be chosen in the different checkboxes? - guessing I should just check remote import / hostmaster
4) How is the key verification process setup - I read this http://community.aegirproject.org/node/30, but it seems that it is only aimed at regular aegir installs. I've got Barracuda Octopus instances. So how should it be done then?

Comments

Comment #1

omega8cc commented 23 November 2012 at 13:48

You may want to check BOA docs: http://drupalcode.org/project/barracuda.git/blob/HEAD:/docs/REMOTE.txt

But note that there is now an issue we are working on: #1594588: Remote import of sites - does it work?

Comment #2

lsolesen commented 23 November 2012 at 06:32

@omega8cc Thanks. However it seems that I need the same file structure on both the source and target server. I wanted to have just a regular aegir using aegir-up on my local development VM and being able to do remote imports from several barracuda instances to that one aegir instance.

Comment #3

omega8cc commented 23 November 2012 at 13:01

You don't need the same files/dirs structure. You just need to run Registry Rebuild after importing the site (BOA does it for you automatically).

Hmm, after reading #1503712: Allow for custom usernames and ports on remote connections it seems that it should work when Aegir system user is different on source and target. We will need to revisit BOA docs then, but it should be a good start for you anyway.

Comment #4

lsolesen commented 23 November 2012 at 13:26

Tried setting up the key verification. However, I cannot figure out how to get my LOCAL octopus on a vagrant created VM (which is not available to the internet) into known hosts. I think that is why the key verification process fails with code 255.

The external command could not be executed due to an application error.
Undefined offset: 1 backend.inc:163
Undefined variable: output backend.inc:170
The command could not be executed successfully (returned: Host key verification failed. , code: 255)
The specified server is not an Aegir master server.

Or do I need to do something specific to make it a MASTER server?

Comment #5

steven jones commented 23 November 2012 at 13:45

If host key verification failed, then you likely need to ssh to the server manually from the command line first, using the aegir user. This will ask you to confirm the host key, check that it is what you expect and then accept it, and then Aegir should be able to connect to your remote master server correctly.

Comment #6

lsolesen commented 23 November 2012 at 16:18

Thanks both for trying to help out. I copied the id_rsa.pub to the production server by using ssh-copy-id, and it seemed to work well. However, I still cannot login without a password. I suspect that it is because the key belongs to o1@aegir.local, which is not accessible by the internet. I am probably missing a lot of things in this passwordless stuff.

Comment #7

lsolesen commented 23 November 2012 at 17:03

And the revelation came to me after visiting #openssh channel:

Permissions was to high.

.ssh should be 700
.ssh/* should be 600

Now I could verify the site.

Comment #8

omega8cc commented 23 November 2012 at 18:04

Note that the ssh-keyscan will not work for localhost hostname:

server:~# ssh-keyscan -t rsa -H aegir.local >> ~/.ssh/known_hosts
getaddrinfo aegir.local: Name or service not known
server:~#

This is why you need to attempt to connect from localhost to the remote server to give it a chance to ask you to add it to the known_hosts, as Steven explained in #5 above.

Comment #9

lsolesen commented 23 November 2012 at 19:30

@emega8cc Yes. I did that. And I was able to connect. When I tried it with another server, however, I get a strange error:

Initialized Drupal 6.26 root directory at /data/disk/o1/aegir/distro/002
The drush command '@ provision-verify' could not be found.
Could not find a Drupal settings.php file at ./sites/default/settings.php.

As my process is not scripted I cannot be certain, but I think I did exactly the same things on the second walk-through. Except one thing, I forgot, namely removing remote_import on the source server as explained here http://drupalcode.org/project/barracuda.git/blob/HEAD:/docs/REMOTE.txt#l22. I have done that now.

I tried re-verifying my first site, and it worked correctly, but my second site gives the error above? Is that one of the odd things, you've also experienced.

Comment #10

lsolesen commented 24 November 2012 at 21:41

And if you run into similar problems (which is likely caused by forgetting to remove the remote_import directory on the source server), you should just delete the drush alias in ~/.drush for that particular server. I was now able to verify the server.

Comment #11

ar-jan commented 15 December 2012 at 20:40

Any other things that may cause this? I followed the REMOTE.txt guidelines, and have two VPS instances set up. (Both are available over the internet). The only thing that's different is that I cannot ssh-keyscan from my source-host, the known_hosts file remains empty. This seems expected, since the source-host isn't supposed to ssh into the target-host, right? (So should this step be in the docs?)

But I can ssh into my source-host from my target-host without using a password, and the fingerprint has been added to known_hosts. But I still get the following when I try to verify the server (source-host) that I added to my o1 control panel on the target-host:

cdn has no server config file
Running: ssh -o PasswordAuthentication=no 'o1'@'boa.example.com' 'drush @hostmaster '\''status'\'' --backend 2>&1' 2>&1
The external command could not be executed due to an application error.
Undefined offset: 1 backend.inc:163
Undefined variable: output backend.inc:170
The command could not be executed successfully (returned: Host key verification failed. , code: 255)
The specified server is not an Aegir master server.