Table of Contents
Current Revision: 12
MultiCloud Marketplace: https://www.rightscale.com/library/server_templates/LAMP-All-In-One-with-MySQL-5-0/18989
The following MultiCloud Images (MCIs) are used by the ServerTemplate. The MCIs determine which operating systems and clouds are supported.
The email address that Apache uses to send administrative mail (set in /etc/httpd/conf/httpd.conf). By setting it to firstname.lastname@example.org emails are saved on the server. You can use your own email address, but your spam filters might block them because reverse DNS lookup will show a mismatch between EC2 and your domain.
Can be set to "worker" or "prefork" and defines the setting in httpd.conf. Use "worker" for Rails/Tomcat/Standalone frontends and "prefork" for PHP.
Sets the directory for your application's web files (/home/webapps/APPLICATION/current/). If you have multiple applications, you can run the code checkout script multiple times, each with a different value for APPLICATION, so each application will be stored in a unique directory. This must be a valid directory name. Do not use symbols in the name.
The name of the S3 bucket where the application tarball (.tgz) can be retrieved.
The name of application tarball that can be retrieved from the S3 bucket specified by APPLICATION_CODE_BUCKET. Valid extensions are .tar/, .tar.gz/, .tgz/, .gz/, .zip/, .war/, and .jar. Be sure to include the file extension. (Ex: myapp.tgz)
The Access Key ID is an Amazon Access Credential that's used to authenticate your requests to AWS services. It's unique to your AWS Account Number. The Access Key ID and Secret Access Key are used to retrieve objects from an S3 bucket that are 'private'. Log into your AWS account at aws.amazon.com to retrieve your access identifiers. It's strongly recommended that you use a RightScale Credential (Design > Credentials) to hide the actual key value from non-admin users while still allowing them to pass the appropriate value as an input. Ex: 1JHQQ4KVEVM02KVEVM02
The Secret Access Key is an Amazon Access Credential that's used to authenticate your requests to AWS services. It's unique to your AWS Account Number. The Access Key ID and Secret Access Key are used to retrieve objects from an S3 bucket that are 'private'. Log into your AWS account at aws.amazon.com to retrieve your access identifiers. It's strongly recommended that you use a RightScale Credential (Design > Credentials) to hide the actual key value from non-admin users while still allowing them to pass the appropriate value as an input. Ex: XVdxPgOM4auGcMlPz61IZGotpr9LzzI07tT8s2Ws
If the MySQL administrator set up a restricted MySQL account for application servers to access the database, then specify the password of that account for this input. If there is not a restricted MySQL account then use the same value that's used for DBADMIN_PASSWORD. The application server will then have unrestricted access to the database.
If the MySQL administrator set up a restricted MySQL account for application servers to access the database, then specify the username of that account for this input. If there is not a restricted MySQL account then use the same value that's used for DBADMIN_USER. The application server will then have unrestricted access to the database.
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
The S3 bucket where the MySQL database dump files will be stored to or restored from. The S3 bucket is specific to MySQL-S3 setups that are not using binary backups. Typically used for free developer ServerTemplates where binary backups are not supported.
Defines the prefix of the MySQL dump filename that will be used to name the backup database dumpfile along with a timestamp. Backups are stored in your S3 bucket (DB_MYSQLDUMP_BUCKET). For example, if prefix is 'mydb', the filename will be 'mydb-timestamp.gz'. During a database restoration, the prefix will be used to find the most recent MySQL dumpfile. Each database's prefix should be unique. Ex: mydbprefix
Enter the name of the MySQL database schema to which applications will connect. The database schema was created when the initial database was first set up. This input will be used to set the application server's database config file so that applications can connect to the correct schema within the database. This input is also used for MySQL dump backups in order to determine which schema is getting backed up. Ex: mydbschema
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.
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
A space-separated list of additional processes to monitor in the RightScale Dashboard. Ex: sshd crond
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*
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.
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.
Optional PHP module packages to install. By default php5-mysql and php-pear are installed.
A value of 'env:RS_INSTANCE_UUID' is required for proper RightScale monitoring and logging.
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.
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||Date Published||Description of Changes||Known Issues|
|12||Apr 20, 2011||Fixed DB_MYSQLDUMP_PREFIX input (w3798)|
|11||Mar 22, 2011||Initial Release -- 11H1||(w3798) The DB_MYSQLDUMP_PREFIX input has a default value set to 'mysql' however it should be left blank because it's a user-specific value.|
© 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.