Puppet users - May 2013 - Running multile MySQL Instances on the same server

Was wondering if someone has implemented the management of multiple MySQL 
instances using puppet on the same server?  Essentially we want to use the 
same MySQL binaries but implement multiple distinct MySQL instances 
connecting via a specific port number.  Puppet Forge has a great MySQL 
implementation including databases, users and permissions but it
doesn''t
seem to allow for managing multiple instances.
 
Any information would be greatly appreciated.

-- 
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscribe@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Should be easy to do, just no one has yet to share their module code.

This would require customizing both the configuration and the puppet-service
implementation.

I have done this (not with puppet) on Red Hat/CentOS type systems by making
duplicate startup scripts in /etc/init.d :

/etc/init.d/mysql-instance1
/etc/init.d/mysql-instance2
... etc.

And even had multiple versions by using customized source builds installed into
parallel locations :

/usr/local/mysql-5.0.xx/...
/usr/local/mysql-5.5.xx/...
... etc.

HTH

“Sometimes I think the surest sign that intelligent life exists elsewhere in the
universe is that none of it has tried to contact us.”
Bill Waterson (Calvin & Hobbes) 

----- Original Message ----- 
From: "Peter Krawetzky" <pkrawetzky@gmail.com> 
To: puppet-users@googlegroups.com 
Sent: Friday, May 17, 2013 10:12:49 AM 
Subject: [Puppet Users] Running multile MySQL Instances on the same server 


Was wondering if someone has implemented the management of multiple MySQL
instances using puppet on the same server? Essentially we want to use the same
MySQL binaries but implement multiple distinct MySQL instances connecting via a
specific port number. Puppet Forge has a great MySQL implementation including
databases, users and permissions but it doesn''t seem to allow for
managing multiple instances.

Any information would be greatly appreciated. 

-- 
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscribe@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com. 
Visit this group at http://groups.google.com/group/puppet-users?hl=en . 
For more options, visit https://groups.google.com/groups/opt_out . 


-- 
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscribe@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

On 17.05.2013 16:12, Peter Krawetzky wrote:
> Was wondering if someone has implemented the management of multiple
> MySQL instances using puppet on the same server?  Essentially we want to
> use the same MySQL binaries but implement multiple distinct MySQL
> instances connecting via a specific port number.  Puppet Forge has a
> great MySQL implementation including databases, users and permissions
> but it doesn''t seem to allow for managing multiple instances.
> Any information would be greatly appreciated.
This is a fundamental limitation of all mysql modules I''ve seen. 
Implementing this is quite a big step up from the usual install 
package/manage databases setup as it requires configuring the new db 
cluster, and passing the port through all other defines.


I think the common solution is either kernel or h/w level virtualisation 
(e.g. openvz, xen, or kvm) instead of trying to cram multiple db 
clusters onto the same base installation.


Regards, David

-- 
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscribe@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Agreed.  This is a much cleaner approach to the problem.

“Sometimes I think the surest sign that intelligent life exists elsewhere in the
universe is that none of it has tried to contact us.”
Bill Waterson (Calvin & Hobbes)

----- Original Message -----
From: "David Schmitt" <david@dasz.at>
To: puppet-users@googlegroups.com
Sent: Friday, May 17, 2013 10:29:50 AM
Subject: Re: [Puppet Users] Running multile MySQL Instances on the same server

On 17.05.2013 16:12, Peter Krawetzky wrote:
> Was wondering if someone has implemented the management of multiple
> MySQL instances using puppet on the same server?  Essentially we want to
> use the same MySQL binaries but implement multiple distinct MySQL
> instances connecting via a specific port number.  Puppet Forge has a
> great MySQL implementation including databases, users and permissions
> but it doesn''t seem to allow for managing multiple instances.
> Any information would be greatly appreciated.
This is a fundamental limitation of all mysql modules I''ve seen. 
Implementing this is quite a big step up from the usual install 
package/manage databases setup as it requires configuring the new db 
cluster, and passing the port through all other defines.


I think the common solution is either kernel or h/w level virtualisation 
(e.g. openvz, xen, or kvm) instead of trying to cram multiple db 
clusters onto the same base installation.


Regards, David

-- 
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscribe@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.


-- 
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscribe@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Hi,

We do this, unfortunately none of our code is clean enough to release.
It''s
used to run replication slaves of several different masters on a single box.

In short we have a base mysql class that installs required packages,
disables the default service instance and makes other global-level changes
(noop io scheduler, helper scripts, etc). Then we define a new type:
define roles::db_mysql_instance($role, $application, $id =
''1'', $port ''3306'', ...) { ... }

In the type we include our base class and roll out everything that needs to
be per-instance with per-instance names:

   - mysql-$name service
   - /etc/mysql-$name + templated configs
   - /var/log/mysql-$name, /run/mysql-$name, /etc/init/mysql-$name
   - Log rotation, SSL key, backup scripts, etc etc

Our base class and role definition are pretty short, ~500 lines, comprising
~50 individual resources (mostly file).

It all works fine. Been in use for a little over a year. Right now
we''re
moving from physical hardware to the cloud so this will probably be
deprecated as part of the migration. I think it only makes sense for
non-virtualised physical hardware.

Alex


On Sat, May 18, 2013 at 12:12 AM, Peter Krawetzky
<pkrawetzky@gmail.com>wrote:
> Was wondering if someone has implemented the management of multiple MySQL
> instances using puppet on the same server?  Essentially we want to use the
> same MySQL binaries but implement multiple distinct MySQL instances
> connecting via a specific port number.  Puppet Forge has a great MySQL
> implementation including databases, users and permissions but it
doesn''t
> seem to allow for managing multiple instances.
>
> Any information would be greatly appreciated.
>
> --
> You received this message because you are subscribed to the Google Groups
> "Puppet Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to puppet-users+unsubscribe@googlegroups.com.
> To post to this group, send email to puppet-users@googlegroups.com.
> Visit this group at http://groups.google.com/group/puppet-users?hl=en.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>
>
-- 
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscribe@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

On 05/17/2013 04:41 PM, Dan White wrote:
> Agreed.  This is a much cleaner approach to the problem.
Yeah, but what about HA clusters? None of the modules are suited for 
managing HA services, because it''s really hard to implement it right
and
to suit it for all the corner cases in already a corner case usage 
scenario...



-- 
Jakov Sosic
www.srce.unizg.hr

-- 
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscribe@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.