tripleo-image-elements/elements/mysql-migration
Ralf Haferkamp 2b846c7406 Add quotes around $DISTRO
The lsb_release -si output might contain spaces. E.g. on openSUSE it is
"openSUSE project".

Change-Id: I0e37bab54d0156f484433246bba7cdc686326c86
2013-12-18 16:51:50 +01:00
..
os-config-applier Migrate data into MySQL from bootstrap. 2013-04-04 11:12:09 -07:00
os-refresh-config/migration.d Add quotes around $DISTRO 2013-12-18 16:51:50 +01:00
README.md Use os-apply-config everywhere 2013-11-20 09:12:15 +00:00
element-deps Rename os-config-applier to os-apply-config. 2013-06-14 20:39:18 +12:00

README.md

Migrate data from another MySQL server into the local one using os-apply-config and os-refresh-config.

Please note the migration process is destructive to any data currently in the MySQL database running on the target host. Safeguards are in place to ensure the process only happens once on any machine.

Configuration

Pass in Heat Metadata with the following structure in the OpenStack::Config sub-key.

mysql:
  users:
    root:
      username: rootuser
      password: XXXXXXX
    dump:
      username: dumpuser
      password: XXXXXXX
mysql-migration:
  bootstrap_host: x.y.z
  slave_user: slave-bot1
  slave_password: XXXXXXXX

The migration process assumes dump and root exist on the bootstrap_host and have access from this host.

The dump user will be used to dump data from bootstrap_host. The root user will be used for localhost access after the database is migrated. If slave_user and slave_password are set to non-empty strings, replication will be setup against the bootstrap_host using this user/password combination.

Special /root/.my.cnf

As a convenience, we copy the given dump and root user names and passwords to /root/.my.cnf after migration. If this file is overwritten, they will also be available as /root/metadata.my.cnf