Ask Your Question

Need clarification on Puppetlabs/mysql documentation

asked 2017-10-05 05:22:57 -0600

Ashley@HCE gravatar image

This line is in the puppetlabs/mysql readme: "When working with a remote server, do not use the mysql::server class in your Puppet manifests". I am not sure what it means by "remote server" in this case. I have set up a test environment using a puppet master with multiple servers running MariaDB using this in my manifest and everything seems to be working fine, is there anything here that will cause problems in time when I am running in production?

edit retag flag offensive close merge delete

2 Answers

Sort by » oldest newest most voted

answered 2017-10-05 20:25:09 -0600

DarylW gravatar image

If you wanted to manage an RDS instance, you wouldn’t be able to use mysql::server, because it expects to install and manage the server. You can point the other part of the module at a remote server, or a server not managed by the puppet module, and still maintain some level of automation

edit flag offensive delete link more



I think this is the answer then, I was reading remote to mean not on the puppet master. Thanks.

Ashley@HCE gravatar imageAshley@HCE ( 2017-10-06 03:05:20 -0600 )edit

answered 2017-10-05 09:14:08 -0600

nb gravatar image

mysql::server: Installs and configures MySQL on a server. When using puppet to manage an existing install you should use mysql::db.

edit flag offensive delete link more


So can I continue to use mysql::server to manage the MySQL instances installed by puppet (e.g. if I need to increase max-connections in the future)? Does "existing install" only apply to MySQL instances that weren't installed by puppet?

Ashley@HCE gravatar imageAshley@HCE ( 2017-10-05 09:46:07 -0600 )edit

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Question Tools


Asked: 2017-10-05 05:22:57 -0600

Seen: 56 times

Last updated: Oct 05 '17