Skip to content

Use backup providers #649

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Feb 19, 2015
Merged

Use backup providers #649

merged 1 commit into from
Feb 19, 2015

Conversation

dveeden
Copy link
Contributor

@dveeden dveeden commented Jan 27, 2015

Add backup providers for

  • mysqldump
  • MySQL Enterprise Backup
  • Percona XtraBackup

@dveeden
Copy link
Contributor Author

dveeden commented Jan 27, 2015

This is an alternative for #647

@igalic
Copy link
Contributor

igalic commented Jan 28, 2015

i'm kinda surprised this is still passing spec tests, for one, for the other, as you can imagine, i prefer this solution, and would as such prefer it to be (better?) documented

owner => $backupdirowner,
group => $backupdirgroup,
}
create_resources("mysql::backup::${provider}", {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Could you convert the backup defines to classes (since they will only ever be used once) and have this create_resources of type "class")?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@hunner done. Looks better.

@hunner
Copy link
Contributor

hunner commented Feb 5, 2015

Descriptions in the readme about the different providers would be great, and document the limitations/requirements (eg: the meb package needs to exist in a repo).

@@ -0,0 +1,85 @@
# See README.me for usage.
define mysql::backup::mysqlbackup (
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should this be called mysqlenterprisebackup instead?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No, I don't think so. The full name is MySQL Enterprise Backup and the
package name is meb and the tool/binary which you actually need to call
is mysqlbackup.

On 02/05/2015 07:36 PM, Hunter Haugen wrote:

In manifests/backup/mysqlbackup.pp
#649 (comment):

@@ -0,0 +1,85 @@
+# See README.me for usage.
+define mysql::backup::mysqlbackup (

Should this be called mysqlenterprisebackup instead?


Reply to this email directly or view it on GitHub
https://github.com/puppetlabs/puppetlabs-mysql/pull/649/files#r24186509.

@dveeden dveeden force-pushed the newbackupprovider branch 2 times, most recently from e230385 to 098b71e Compare February 11, 2015 21:10
@dveeden
Copy link
Contributor Author

dveeden commented Feb 11, 2015

I've added a short description to the README.md and I've added a config file for mysqlbackup (separate from the main my.cnf so it can be protected with 0600).

Add MySQL Enterprise Backup and Percona XtraBackup
igalic added a commit that referenced this pull request Feb 19, 2015
@igalic igalic merged commit cb142f4 into puppetlabs:master Feb 19, 2015
@igalic
Copy link
Contributor

igalic commented Feb 19, 2015

thaaaaanks @dveeden!
and thank you @hunner for the review!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants