Comments on: Managing MySQL with MySQL Sandbox? http://blog.wl0.org/2010/01/managing-mysql-with-mysql-sandbox/ Random thoughts on different topics Thu, 22 Jul 2010 06:31:53 +0000 http://wordpress.org/?v=2.9.1 hourly 1 By: shinguz http://blog.wl0.org/2010/01/managing-mysql-with-mysql-sandbox/comment-page-1/#comment-1521 shinguz Wed, 06 Jan 2010 11:35:23 +0000 http://blog.wl0.org/2010/01/managing-mysql-with-mysql-sandbox/#comment-1521 Hi Simon, In myEnv v0.2 this should be easy to implement. If you want to try I can send you a preview. But I have to implement it first. Oli Hi Simon,

In myEnv v0.2 this should be easy to implement. If you want to try I can send you a preview. But I have to implement it first.

Oli

]]> By: Giuseppe Maxia http://blog.wl0.org/2010/01/managing-mysql-with-mysql-sandbox/comment-page-1/#comment-1490 Giuseppe Maxia Sun, 03 Jan 2010 22:42:40 +0000 http://blog.wl0.org/2010/01/managing-mysql-with-mysql-sandbox/#comment-1490 Hi Simon, I have some ideas to extend MySQL::Sandbox into a general purpose install-and-deploy application. I will propose some design plans in my blog quite soon. Hi Simon,
I have some ideas to extend MySQL::Sandbox into a general purpose install-and-deploy application. I will propose some design plans in my blog quite soon.

]]> By: Simon Mudd http://blog.wl0.org/2010/01/managing-mysql-with-mysql-sandbox/comment-page-1/#comment-1486 Simon Mudd Sun, 03 Jan 2010 17:55:50 +0000 http://blog.wl0.org/2010/01/managing-mysql-with-mysql-sandbox/#comment-1486 Hi Giuseppe, I'll take a longer look at the manual to see if I can do what I want. Regarding the init scripts both Oracle and Sybase have root owned scripts which su to the non-root script which does the real task of start/stopping the instances. This should not be to hard to replicate for MySQL. The thing that is important to me is some way to be able to select which instances will be started on boot. On some development servers I have over 10 mysql instances running and some of those may not be fully operational or I may want to keep them down. Having a way to able to say: start all "selected" instances would be nice. I'm not sure how that fits in with your current scheme. In any case the MySQL Sandbox does seem to have the most generic and flexible way to manage MySQL servers and is easy to use. Hi Giuseppe,

I’ll take a longer look at the manual to see if I can do what I want.

Regarding the init scripts both Oracle and Sybase have root owned scripts which su to the non-root script which does the real task of start/stopping the instances. This should not be to hard to replicate for MySQL.

The thing that is important to me is some way to be able to select which instances will be started on boot. On some development servers I have over 10 mysql instances running and some of those may not be fully operational or I may want to keep them down. Having a way to able to say: start all “selected” instances would be nice. I’m not sure how that fits in with your current scheme.

In any case the MySQL Sandbox does seem to have the most generic and flexible way to manage MySQL servers and is easy to use.

]]> By: Giuseppe Maxia http://blog.wl0.org/2010/01/managing-mysql-with-mysql-sandbox/comment-page-1/#comment-1485 Giuseppe Maxia Sun, 03 Jan 2010 17:01:54 +0000 http://blog.wl0.org/2010/01/managing-mysql-with-mysql-sandbox/#comment-1485 About the things that you say seem to be missing, please look at the reference manual, especially the sbtool and the scripts created by the sandbox installer. Some of what you need is already available. http://search.cpan.org/~gmax/MySQL-Sandbox-3.0.05/lib/MySQL/Sandbox.pm The ability of starting/stopping a sandbox at startup/shutdown has never been in the design. MySQL::Sandbox does already provide a common directory ($HOME/sandboxes) The single sandbox installer has more than 20 options that you can fiddle with to achieve optimal installations. The group sandbox installers can do the same fine tuning by means of environment variables that invoke the above mentioned options. Regarding the name, it is appropriate for the usage for which it was created. Cheers Giuseppe About the things that you say seem to be missing, please look at the reference manual, especially the sbtool and the scripts created by the sandbox installer. Some of what you need is already available.
http://search.cpan.org/~gmax/MySQL-Sandbox-3.0.05/lib/MySQL/Sandbox.pm
The ability of starting/stopping a sandbox at startup/shutdown has never been in the design.

MySQL::Sandbox does already provide a common directory ($HOME/sandboxes)

The single sandbox installer has more than 20 options that you can fiddle with to achieve optimal installations. The group sandbox installers can do the same fine tuning by means of environment variables that invoke the above mentioned options.

Regarding the name, it is appropriate for the usage for which it was created.

Cheers

Giuseppe

]]>