Installation

From $1

The source code to Scalr 2.0 will soon be released, and this page updated.

Scalr v1 Installation and Configuration

System Requirements

Package names and installation methods vary. Consult the OS-specific installation guide if provided. A list of available OS-specific guides can be found at OS Specific Installation Guides.

Scalr requires a web server capable of rewrite rules and can run on any POSIX-compatible (Linux, BSD etc.) operating system, as long as the following requirements are met:

We create cheap resumes written by educated writers online!

Read this guideline and investigate how to do research online!

Delivered online book report/s is original - we communicate with the best writers only!

  • PHP 5.2.5 or higher,
  • MySQL 5.0 or higher (MySQL 5.1 or higher preferred)

You may need to install dependencies as well, such as

  • libssh2
  • OpenSSL
  • net-snmp-utils
  • bind9

Required PHP configuration options

  • safe_mode must be set to Off
  • register_globals must be Off

Required PHP extensions

Installation

Download the most recent code release from http://scalr.googlecode.com. Unzip this archive.

Copy the contents of the app/ folder to your webserver. Only the app/www folder must be readable by the webserver; all other folders must be underneath the web root. Scalr will not work from a subfolder of the document root (i.e. domain.com/something). Please create a subdomain and point its document root to the Scalr app/www folder. In the notes that follow,/scalr_home_dir/ refers to the app/ folder location on the webserver.

Set AllowOverride (Apache) or other directives as appropriate for the Scalr domain to implement the rewrite rules found in /scalr_home_dir/etc/.htaccess. If you are using webserver software other than Apache (say lighttpd) you will need to convert the .htaccess rules into a form suitable for your server.

Configure your webserver to deliver index.php by default.

Set permissions

The following folders (and subfolders) and files must be writable by the webserver. Change ownership to the webserver user and set permissions to 700, or else (less secure) set permissions to 777 (world-writable):

  • cache
  • cron/cron.pid
  • etc/.passwd

Create and configure database

  1. Create new MySQL database and database user for Scalr.
  2. Import database dump from sql/database.sql file.
  3. Edit database connection details in /scalr_home_dir/etc/config.ini file on the webserver.

Set cron jobs

For system to work properly, it needs to run a few tasks periodicaly. Scalr has a single cron/cron.php file that must be executed with various command-line switches. The following tasks must be scheduled:

 

* * * * * /path/to/php -q /scalr_home_dir/cron/cron.php --Poller
* * * * * /path/to/php -q /scalr_home_dir/cron/cron.php --Scaling
11 * * * * /path/to/php -q /scalr_home_dir/cron/cron.php --RotateLogs
*/15 * * * * /path/to/php -q /scalr_home_dir/cron/cron.php --MySQLMaintenance
*/6 * * * * /path/to/php -q /scalr_home_dir/cron/cron.php --DNSMaintenance
*/10 * * * * /path/to/php -q /scalr_home_dir/cron/cron.php --EBSArraysMaintenance
*/5 * * * * /path/to/php -q /scalr_home_dir/cron/cron.php --EBSMaintenance
*/3 * * * * /path/to/php -q /scalr_home_dir/cron/cron.php --DNSZoneListUpdate
*/2 * * * * /path/to/php -q /scalr_home_dir/cron/cron.php --DBQueueEvent
*/3 * * * * /path/to/php -q /scalr_home_dir/cron/cron.php --MessagingQueue
*/11 * * * * /path/to/php -q /scalr_home_dir/cron/cron.php --Cleaner
*/3 * * * *  /path/to/php -q /scalr_home_dir/cron/cron.php --UsageStatsPoller

A few additional cron tasks need to be scheduled in order to configure statistics. See Configuring Load Statistics for details.

Configure primary AWS account

Sclar needs to have AWS access.

  1. Retrieve your EC2 credentials from your account at the Amazon Web Services site.
  2. Copy your EC2 access certificate file to /scalr_home_dir/etc/
  3. Copy your EC2 private key file to /scalr_home_dir/etc/

These files will be named cert-XXXXXXXXXXXX.pem and pk-XXXXXXXXXXXX.pem, where XXXXXXXXXXXX is Your Access Key name, which you specify on the "Settings->Core settings" page.

Configuration

To check whether your server meets (most) Scalr system requirements, run the testenvironment.php script in the app/www folder. Assuming you have completed the steps above, this can be accessed as http://your.scalr.domain/testenvironment.php from your web browser. This will find most major issues, although some (missing rewrite rules, missing cron tasks) go undetected.

Congratulations! You may now proceed to configuration. Log in as admin / admin, go to Settings->Core settings and edit settings.

Known issues

  • Fedora 7: At least one user has reported that the snmptrap tool on Fedora 7 uses port 161 instead of standard 162 - see

http://groups.google.com/group/scalr-discuss/t/68457bc1edd9d8b4

diff scalr-1.0RC3/app/src/LibWebta/library/NET/SNMP/class.SNMP.php /var/www/scalr/app/src/LibWebta/library/NET/SNMP/class.SNMP.php
144c144
<                       return $this->Shell->QueryRaw(self::$SNMPTrapPath.' -v 2c -c '.$this->Community.' '.$this->Connection.' "" '.$trap);
---
>                       return $this->Shell->QueryRaw(self::$SNMPTrapPath.' -v 2c -c '.$this->Community.' '.$this->Connection.':162 "" '.$trap);
 
 
 

Further Installation and Configuration Guides

Some additional informations about installation and configuration can be found within this blog posts:

Tags:
 
Comments (0)
You must login to post a comment.