Before jumping into the runbook situations we want to briefly introduce the 2 existing templates used
by Manager for MySQL. Understanding their main differences will clarify the sequence of steps described
for each of the situations below.
NOTE: Before version 2 of the Manager for MySQL, the templates below were named "Master MySQL
v1" and "Slave MySQL v1," instead of "Bootstrap MySQL" and "Additional MySQL." Therefore substitute
the names if you're working on a version earlier than 2.
This ServerTemplate is ONLY launched when there is no other MySQL instance running. This
template is only used to bootstrap a new Manager for MySQL. Therefore, unless a catastrophic
failure killing all MySQL instances occurs, this template will only be launched once in the lifetime of that
application. Any life-cycle operations on the system are done by launching an "Additional MySQL"
template (see below) and performing operational tasks such as promoting instances to master,
initializing as slaves etc.
The sequence of boot scripts executed by this template roughly consists of:
This is the the server template that is used when there is at least one other MySQL instance running in
the system (i.e., all situations except the bootstrap process). Launching this template can be seen as
launching a wildcard MySQL template, that can be molded and 'configured' after it completes the
initialization. For example, to launch a new slave MySQL server, we can boot this template, and once
it's operational, we can click on the "initialize as slave" button.
The sequence of boot scripts executed by this template is basically the same as the bootstrap one,
except that it doesn't register the master DNS and it doesn't restore any previous backup:
© 2006-2014 RightScale, Inc. All rights reserved.
RightScale is a registered trademark of RightScale, Inc. All other products and services may be trademarks or servicemarks of their respective owners.