Table of Contents
Current Revision: 10
MultiCloud Marketplace: https://www.rightscale.com/library/server_templates/PHP5-Front-End-11H1/18198
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 email@example.com 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.
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.
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
The URI of the health check page, which is used by HAProxy for checking whether the site is up or not. You must create your own health check page, which returns HTTP 200 OK. The contents of the page are not relevant but its name should be unique (preferably a random number). The same page will be used by the load balancers to determine which application servers are "up" and capable of handling requests. For example, if you use '/hlthchk378923.html' (Note: be sure to include the slash before the filename), the health check page would be 'http://www.mydomain.com:80/hlthchk378923.html' and its content could be as simple as "OK."
Sets the name of the HAProxy load balance pool on frontends in /home/haproxy/rightscale_lb.cfg. Application severs will join this load balance pool by using this name. Ex: www
Sets the name of the backend application server in the (/home/haproxy/rightscale_lb.cfg) location. This value needs to be unique. Therefore, it is best to use the EC2_INSTANCE_ID ENV variable. Ex: Select "EC2_INSTANCE_ID" from the ENV input dropdown. Do not enter this value manually.
The IP address that HAProxy will be listening on. Normally, it should be set to localhost. Ex: 127.0.0.1
The port number that HAProxy will be listening on. Normally, it's set to 85. If you have multiple load balance pools, each pool must be assigned to a different port. Ex: 85
The fully qualified hostname of all the servers that have HAProxy installed on them for load balancing purposes. For example, if www.domain.com has two dedicated load balancers with HAProxy installed on them, you would enter www.domain.com as the LB_HOSTNAME. It is necessary that these hosts be registered with DNS with matching A Records so that the application servers will be able to connect to and disconnect from all the HAProxy servers and update their configuration files. Ex: www.domain.com
The name of the base HAProxy configuration file that will be used. This file will be modified according to the defined inputs. The current values are: haproxy_fullssl, haproxy_http, and haproxy_tcp. Ex: haproxy_http
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
Defines the maximum number of connections that HAProxy will allow on any given server in the load balance pool. For example, if set to 255, each server will have a maximum of 255 connections. While the default is 255, your application may not handle this many connections. Testing is encouraged to determine the proper number of connections per server. Ex: 255
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*
The time interval (in seconds) that collectd uses to poll HAProxy for statistics. Default: 60
The URI for the HAProxy statistic report page, which lists the current session, queued session, response error, health check error, server status, etc., for each HAProxy group. Ex: /haproxy-status
Optional path for a maintenance page, relative to document root (i.e., "".../current/public""). The file must exist in the subtree of the vhost, which will be served by the web server if it's present. If ignored, it will default to '/system/maintenance.html'.
Enables PHP support for Apache by enabling PHP module. Required to execute PHP scripts.
Optional PHP module packages to install. By default php5-mysql and php-pear are installed.
If set to 'True', any existing static content (e.g. *.html, *.jpg, *.css) will be served directly by Apache. If set to 'False', static content will come from the application server. Regardless, Apache will forward requests for PHP and Tomcat dynamic content (e.g. *.php, *.action, *.jsp, and *.do) to the application servers.
Determines HAProxy session stickiness. Set to 'True' to use session stickiness where HAProxy will reconnect a session to the last server it was connected to (which it does via a cookie). Set to 'False' if you do not want to use sticky sessions; HAProxy will establish connections with the next available server.
The svn mode you would like to get your files in. Export is more secure, while checkout allows you to make changes and update them. Ex: [checkout,export]
The SVN password that is used to checkout the application code from SVN repository.
The SVN username that is used to checkout the application code from SVN repository.
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.
A value of 'env:RS_INSTANCE_UUID' is required for proper RightScale monitoring and logging.
The URL of your SVN repository where your application code will be checked out from. Ex: http://mysvn.net/app/
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|
|11||Mar 22, 2011||Initial Release -- 11H1 compatibility release|
© 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.