← Back to team overview

sandbox-developers team mailing list archive

Network based Sandbox setups

 

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi List,

I'm working on a master failover set of scripts for our production environment
of mysql replication architectures.

I would very much like to use mysql-sandbox to test and develop my scripts.
In order to minimalize the changes between my development environment and my
production environment I would like to change the behaviour of the make_sandbox
scripts to start mysql servers on the same port but on a different local network
address:

 master -> 127.0.0.10:3306
 slave1 -> 127.0.0.11:3306
 slave2 -> 127.0.0.12:3306
 ..
 ..
 slaveX -> 127.0.0.X:3306

I've read the distributed replication setup blog [1] and took the script,
modified it to work on a local host that has the ip-addresses preconfigured.
That works now, if someone is interested I'll post it.

I would like to add this functionality to the core mysql-sandbox scripts if
people agree that this is useful functionality ?

It's possible to supply config options through the make_sandbox script which
generate sandboxes on different ipaddresses with the same portnumber, however
sbtool for example isn't aware of them.

If so, what would the preferred cmdline semantics be ?

Given the fact that adding ip-aliases is usually a root privilege-only activity,
 I would propose to add a check for requested ip-addresses:portvalues and output
some instructions for the user to add the ipaddresses to the necessary interfaces.

In addition I found several places in the scripts that are generated where a
she-bang: #!/usr/bin/perl is used. The bash she-bang is replaced everywhere by
#!_BINBASH_

However the perl invocation is fixed to #!/usr/bin/perl, which happens to be NOT
the correct location of the perl binary on my system.

I couldn't find a button to log a bug on launchpad, so I'm posting it here.
Please accept my apologies if this is the wrong place.

Possible solutions would be to introduce a similar construct as the _BINBASH_
for perl or use /bin/env to do the dirty work. Any preference ?


Regards,

Ramon

[1] :
http://datacharmer.blogspot.com/2009/06/remote-replication-setup-with-gearman.html

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.8 (Darwin)

iEYEARECAAYFAkqfx+sACgkQwiVM6CtDHQ2MvACfW8aeAU3XTLSZdMIwajQATJtU
y2oAnjUjud1xK0iRnsf0J1KL43z5PHVW
=4Si7
-----END PGP SIGNATURE-----