Home > ServerTemplates > Archive > 11H1 > References > Database Manager with MySQL 5.0 - 11H1

MindTouch
Copyright (c) 2006-2014 MindTouch Inc.
http://mindtouch.com

This file and accompanying files are licensed under the MindTouch Master Subscription Agreement (MSA).

At any time, you shall not, directly or indirectly: (i) sublicense, resell, rent, lease, distribute, market, commercialize or otherwise transfer rights or usage to: (a) the Software, (b) any modified version or derivative work of the Software created by you or for you, or (c) MindTouch Open Source (which includes all non-supported versions of MindTouch-developed software), for any purpose including timesharing or service bureau purposes; (ii) remove or alter any copyright, trademark or proprietary notice in the Software; (iii) transfer, use or export the Software in violation of any applicable laws or regulations of any government or governmental agency; (iv) use or run on any of your hardware, or have deployed for use, any production version of MindTouch Open Source; (v) use any of the Support Services, Error corrections, Updates or Upgrades, for the MindTouch Open Source software or for any Server for which Support Services are not then purchased as provided hereunder; or (vi) reverse engineer, decompile or modify any encrypted or encoded portion of the Software.

A complete copy of the MSA is available at http://www.mindtouch.com/msa

Database Manager with MySQL 5.0 - 11H1

Table of Contents

  1. Info
  2. Images
  3. Scripts
  4. Inputs
  5. Revision History
  6. See also

Info

Current Revision: 16
MultiCloud Marketplace: https://www.rightscale.com/library/server_templates/Database-Manager-with-MySQL-5-/18227

  • Description - The RightScale Database Manager for MySQL is one of our most popular premium ServerTemplates. It provides a high-availability master/slave database configuration that can be used as the backbone for a variety of applications and workloads. It is cloneable, just like any other RightScale ServerTemplate, so you can make adjustments specific to your organization's technology or work flow needs.
  • Supported Clouds - AWS US-East, AWS US-West, AWS EU, AWS AP-Singapore, AWS AP-Tokyo

Images

The following MultiCloud Images (MCIs) are used by the ServerTemplate. The MCIs determine which operating systems and clouds are supported.

MultiCloud Images

  • RightImage_CentOS_5.4_x64_v5.6 - 11H1
    • AWS US-East, AWS US-West, AWS EU, AWS AP-Singapore, AWS AP-Tokyo
  • RightImage_CentOS_5.4_i386_v5.6 - 11H1
    • AWS US-East, AWS US-West, AWS EU, AWS AP-Singapore, AWS AP-Tokyo

Scripts

Inputs

DBADMIN_PASSWORD

The password of the database user (DBADMIN_USER) that has "admin" privileges.

DBADMIN_USER

The username of the database user that has "admin" privileges.

DBREPLICATION_PASSWORD

The password that's used for replication between master and slave MySQL databases.

DBREPLICATION_USER

The username that's used for replication between master and slave MySQL databases.

DB_BACKUP_KEEP_DAILY

The number of daily snapshots (backups) to keep (i.e. rotation size). A daily backup is defined as the latest completed snapshot of a day that is closest to the end of the day (23:59:59). (Default: 14) See "Archiving of EBS Snapshots" on RightScale's Support site for further details on the archiving logic.

DB_BACKUP_KEEP_LAST

The total number of snapshots to keep. When this limit has been reached, the oldest snapshot will be deleted. (Default: 60) See "Archiving of EBS Snapshots" on RightScale's Support site for further details on the archiving logic.

DB_BACKUP_KEEP_MONTHLY

The number of monthly snapshots to keep (i.e. rotation size). (Default: 12) See "Archiving of EBS Snapshots" on RightScale's Support site for further details on the archiving logic.

DB_BACKUP_KEEP_WEEKLY

The number of weekly snapshots to keep (i.e. rotation size). (Default: 6) See "Archiving of EBS Snapshots" on RightScale's Support site for further details on the archiving logic.

DB_BACKUP_KEEP_YEARLY

The number of yearly snapshots to keep (i.e. rotation size). (Default: 2) See "Archiving of EBS Snapshots" on RightScale's Support site for further details on the archiving logic.

DB_BINLOG_PREFIX

The prefix defines the filename and location of your MySQL stored binlog files. The prefix sets the log-bin variable in MySQL config file. If you do not specify an absolute path, it will be relative to the data directory. Ex: /mnt/mysql-binlogs/mysql-bin

DB_LINEAGE_NAME

The prefix that will be used to name/locate the backup EBS snapshots of a particular MySQL database. For example, if prefix is 'mydb', the filename will be 'mydb-master-timestamp' for a snapshot of your master database and 'mydb-slave-timestamp' for a snapshot of the slave. When you launch a Slave-DB or perform a database restoration, the prefix will be used to find the most recent MySQL EBS snapshot (default) or one that you've explicitly specified using the optional override inputs. (OPT_DB_RESTORE_LINEAGE_OVERRIDE and OPT_DB_RESTORE_TIMESTAMP_OVERRIDE) Each database's prefix should be unique. Ex: mydbprefix

DB_SERVER_USAGE

Set this input to "dedicated" if it's a standalone MySQL server. Set to "shared" if you're launching an all-in-one server where there are other applications such as Apache, PHP, Rails, etc. also running on the server.

DB_TERMINATE_SAFETY

Prevents the accidental running of the "DB TERMINATE SERVER" script. This script will only run if the input variable is set to "off".

DNS_PASSWORD

The password that's used to access and modify your DNS A Records. For DNSMadeEasy and DynDNS, enter your password. (Ex: myPassw0rd) For AwsDNS, enter your AWS Secret Access Key. (Ex: XVdxPgOM4auGcMlPz61XVdxPgOM4auGcMlPz6)

DNS_PROVIDER

The name of your DNS provider. Select the DNS provider that you're using to manage the DNS A Records of your Master/Slave DB servers. Ex: DNSMadeEasy, DynDNS, Route53

DNS_USER

The username that's used to access and modify your DNS A Records. For DNSMadeEasy and DynDNS, enter your username. (Ex: myUsername) For AwsDNS, enter your AWS Access Key ID. (Ex: 1JHQQ4KVEVM1JHQQ4KVE)

EXTERNAL_DNS_ID

The unique identifier that's associated with the DNS A Record of the Master-DB. The unique identifier is assigned by the DNS provider when you create a dynamic DNS A Record. Unlike the MASTER_DNS_ID input, this ID is used to register the external (public) IP address and not the private IP. This ID is used to update the associated A Record with the public IP Address of the Master-DB when defining which server is the "master" database. If you are using DNSMadeEasy as your DNS provider, a 7-digit number is used. (Ex: 4403234)

INIT_SLAVE_AT_BOOT

Set to 'True' for the instance to initialize the MySQL database server as a slave at boot time. Set to 'False' if there is no Master-DB server running.

MASTER_DB_DNSID

The unique identifier that's associated with the DNS A Record of the Master-DB. The unique identifier is assigned by the DNS provider when you create a dynamic DNS A Record. This ID is used to update the associated A Record with the private IP Address of the Master-DB when defining which server is the "master" database. If you are using DNSMadeEasy as your DNS provider, a 7-digit number is used. (Ex: 4403234)

MASTER_DB_DNSNAME

The fully qualified hostname for the MySQL Master-DB server. There must be a corresponding DNS A Record for the Master-DB server with your DNS provider (e.g. DNSMadeEasy). Application servers and Slave-DB servers will connect to the Master-DB by looking up the IP address that's mapped to the Master-DB's hostname. RightScale's scripts are designed to update the A Record with the Master-DB's private IP address. Ex: master.mydomain.com

MON_PROCESSES

A space-separated list of additional processes to monitor in the RightScale Dashboard. Ex: sshd crond

MON_PROCESSMATCH

A space-separated list of pairs used to match the name(s) of additional processes to monitor in the RightScale Dashboard. Pair arguments are passed in using the syntax 'name/regex'. Ex: ssh/ssh* cron/cron*

OPT_DB_MYSQL_TIMEOUT

Optional period of time to wait for a MySQL server to startup. When starting MySQL with large databases or on databases that need to rebuild tables, you may need to increase this value to prevent a MySQL server from timing out during startup.

OPT_DB_RESTORE_LINEAGE_OVERRIDE

If defined, it will override the input defined for DB_LINEAGE_NAME so that you can restore the database from another backup that has as different DB_LINEAGE_NAME. The most recent completed snapshots will be used unless a specific timestamp value is specified for OPT_DB_RESTORE_TIMESTAMP_OVERRIDE. This input allows you to restore from a different set of snapshots however, the subsequent backups will use DB_LINEAGE_NAME to name the snapshots. Be sure to remove this input once the new master is operational. Ex: lineageoverride

OPT_DB_RESTORE_TIMESTAMP_OVERRIDE

Another optional variable to specify restore from a specific timestamp. Specify a string matching the timestamp tags on the EBS snapshot set.

OPT_DB_RESTORE_VERSION_CHECKING

Determines if a database version check is performed before a database restoration from snapshot. Set to 'no' to disable version checking. Set to 'true' (default) to enable version checking.

OPT_MON_FILES

A list of the files to be monitored. The filenames should be separated with spaces, and must be readable by the "nobody" user.

OPT_MYSQL_MAX_CONNECTIONS

The maximum MySQL connection that can be established across the entire deployment. (Default: 500) You should adjust this carefully! Too many connections can consume large amounts of memory and crash your database.

OPT_SYS_LVM_SWAP_SIZE

Defines the size (in GB) of the swap partition to create on the running instance. If set to 'ignore' no swap partition will be created. Ex: 3

PRIVATE_SSH_KEY

The private SSH Key of another instance that gets installed on this instance. It allows this instance to SSH into another instance to update the configuration files. Select input type "key" from the dropdown and then select an SSH key that is installed on the other instance. You must select an SSH Key where its private material is available.

SERVER_EIP

EC2 elastic IP address

SERVER_UUID

A value of 'env:RS_INSTANCE_UUID' is required for proper RightScale monitoring and logging.

SKETCHY

A value of 'env:RS_SKETCHY' is required to use RightScale monitoring servers.

SLAVE_DB_DNSID

The unique identifier that's associated with the DNS A Record of the Slave-DB. The unique identifier is assigned by the DNS provider when you create a dynamic DNS A Record. This ID is used to update the associated A Record with the private IP Address of the Slave-DB. If you are using DNSMadeEasy as your DNS provider, a 7-digit number is used. (Ex: 4403234)

SYSLOG_SERVER

The hostname of the syslog server where log files will be sent. This input should be set to 'env:RS_SYSLOG' so that you can view your log files in the Dashboard.

SYS_TZINFO

Sets the system time to the timezone of the specified input, which must be a valid zoneinfo/tz database entry. If the input is 'unset' the timezone will use the 'localtime' that's defined in your RightScale account under Settings -> User -> Preferences tab. You can find a list of valid examples from the timezone pulldown bar in the Preferences tab. Ex: US/Pacific, US/Eastern

Revision History

Revision Date Published Description of Changes Known Issues
16 Mar 22, 2011 Initial Release -- 11H1  

See also

You must to post a comment.
Last Modified
23:31, 16 May 2013

Tags

Classifications

This page has no classifications.

Announcements

None

Glossary | 用語용어 Site Map | Site Help Community Corporate Site Get Support Dashboard Login
Doc Feedback Product Feedback Resources MultiCloud Marketplace Forums

Dashboard Status


© 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.