Need advice on setting up BOA for multiple servers in order to clone sites between each server easily

We encourage users to post events happening in the community to the community events group on https://www.drupal.org.
sierraoscardelta's picture

Hi there,

I would like some advice on how to best go about achieving a dev-stage-pro workflow using BOA across multiple servers.

I currently have 3 VPS', (2 with Linode, and another with a local provider). I also have a HP Proliant, at home, that i'm wanting to repurpose as a dev server and throw into the mix.

The VPS's each run Ubuntu 12.04, each with their own separate BOA installs, and the dev server runs Debian Squeeze. (Dev server doesn't have a working BOA instance at the moment due to DNS issues.. currently pointing subdomain to the static public IP of my home router, then forwarding with NAT to server...I haven't tried the localhost install on this server yet so maybe thats the go instead of using the public option)

Anyways, the end goal is to create a workflow whereby I can have a BOA instance on my dev server that I use to quickly and easily provision sites. From there I'd love to be able to clone sites to a staging server where I can test and provide customer access. If alls well i'd then like to easily clone from there to a production instance.

Currently each server has its own instance of BOA on it... no server is aware of the other and i rsync or git between them if I need, but it would be much better to be able to log in to a master instance and have complete control of every site on each server, moving them between each other by running a clone task in the queue...I don't know if I ask too much here though so I welcome your comments, suggestions, or thoughts.

cheers

:-)

Comments

I realise now that my issues

sierraoscardelta's picture

I realise now that my issues are probably more related to dns zones than anything BOA related but any advice or comments on the subject are still greatly appreciated.

Be nice, but I wonder...

Anonymous's picture

BOA maintainers will probably not add a feature like this in the foreseeable future. It's basically not one of those features their typical customer would want to pay for. That be more of an enterprise high up-time thing, not to mention a bit outside of the operational reach of most. Aka, bigger budget than the folks will want to pay per month for such a service.

But, in the event that Grace and her team bestows such an awesome feature upon us, disregard the above comments.

Peace and grateful as always for the BOA folks,
Michael Clendening

Look deeper into the docs

Mojah's picture

Look deeper into the docs about importing sites from one BOA server into another. Once you have the instances talking to each other, what you want to achieve is possible. I remember testing this out a while back. I'm unable to give more info right now, but I'm sure what you want is already achievable with BOA. Good luck.

Santhan

If your local server is

ar-jan's picture

If your local server is reachable over the internet, this is possible: http://drupalcode.org/project/barracuda.git/blob/HEAD:/docs/REMOTE.txt.
You can actually skip the mysql steps outlined there.

If your local server is

ar-jan's picture

If your local server is reachable over the internet, this is possible: http://drupalcode.org/project/barracuda.git/blob/HEAD:/docs/REMOTE.txt.
You can actually skip the mysql steps outlined there.

If your local server is

ar-jan's picture

If your local server is reachable over the internet, this is possible: http://drupalcode.org/project/barracuda.git/blob/HEAD:/docs/REMOTE.txt.
You can actually skip the mysql steps outlined there.

You want slave servers not remote import

geoff's picture

The "Remote Import" allows you to use one server to log into a another server and "copy" a site (files and database) back to that first server. You end up with a copy of the site on each server.

I have recently tested this and it works.

This is NOT what you want.

What you want is a single "master" instance of BOA and then several "slave" servers. Technically, after you register a slave server on the master, you can create a platform on the slave (from the master) and then create sites on that slave (again, from the master).

That way, you have a single - centralised - list of sites and can clone from one slave server to another.

This is what you want - this is what I want.

I have been testing this now for a while and have not been able to get it to work.

If anyone has been able to get this working, I would be interested in hearing what they did.

So far, using both Ubuntu 12.04 and then again servers using Debian, I have created two servers - "master" and "slave"

I install BOA on each normally.

I setup the slave so that I can SSH and access MySQL - Everything registers corrrectly.

  1. If I install db and files on the master - it all works. Expected since this is not using any special from a single server install.

  2. If I install the db on the slave and the files on the master - it works.

  3. If I install the db on the master and the files on the slave - it fails. Expected as the server is named "localhost" and should be on the master's URL to be accessible from the slave.

  4. if I install db and files to the slave - it fails. Insecure Database Error. Then rolls back.

I think the error is not reporting the actually problem as otherwise (2) would have failed.

Here I am stuck???

I thought I read a while back

snlnz's picture

I thought I read a while back that this working feature won't be supported in the 1.x branch of Aegir.
It is limited to the 2.x development branch so I'm led to believe.

BOA

Group organizers

Group notifications

This group offers an RSS feed. Or subscribe to these personalized, sitewide feeds:

Hot content this week