|
Installation
Scalr v1 Installation and Configuration
Scalr v1 Instalation and ConfigurationSystem RequirementsTo quickly check either your server meets Scalr system requirements, use testenvironment.php script from app/www folder. Simply upload php file on your host and open it in browser. It should find most of major issues. Scalr requires a web server and can run on any POSIX-compatible (Linux, BSD etc.) operating system, as long as the following requirements are met:
Required PHP configuration options
Required PHP extensions
InstallationCopy contents of app folder on your webserver. Only app/www folder must be readable by webserver, all other folders must be underneath web root. This also means that Scalr will not work from the subfolder (i.e. domain.com/something). Please create a subdomain and install in it's web root. Set folders permissionsSet permissions on the following folders (and subfolders) and files to 777 (world-writable):
Create and configure database
Set Cron jobsFor 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 sheduled: * * * * * /path/to/php -q /scalr_home_dir/cron/cron.php --Poller * * * * * /path/to/php -q /scalr_home_dir/cron/cron.php --Scaling 1 1 * * * /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 */2 * * * * /path/to/php -q /scalr_home_dir/cron/cron.php --EBSQueue */3 * * * * /path/to/php -q /scalr_home_dir/cron/cron.php --UsageStatsPoller Configure primary AWS accountSclar needs to have AWS access.
ConfigurationInstallation complete! You may now proceed to configuration. Log in as admin / admin, go to Settings->Core settings and edit settings. Known issues
|
Sign in to add a comment
Can you add some verbiage about "Where XXXXXXXXXXXX is a Key Name" Where do I config the $AWS_KEYNAME?
Key Name is "Your Access Key ID" that can be taken on "AWS Access Identifiers" page inside AWS portal. Going to adjust the text, thanks.
Alex,
Do you think you could get scalr working for Linode.com? Better cost structure and mor flexible sizing of nodes.
I just want to know if i should install these in my own server( not EC2 ). I am quite new to Amazon Web Services and Scalr.
thanashyam, it's entirely up to you.
It's a little unclear from the docs as to what should be entered in the AWS Settings section of the Core Settings page.
Just to be clear, is this correct: Account ID = AWS Account Number eg. 123412341234 Key Name = The string between cert-XXXX.pem and pk-XXXX.pem in the x.509 certificates that get copied to /etc Access Key: AWS Secret Key Access Key ID: Public Access Key ID as shown in the AWS account page
Is this correct?
Thanks
I had to install Scalr today on Amazon EC2. Some of the documentation found on Internet is very old (dating from scalr 0.5) and the one you provide here is ... how should I say ... spartan. So I've wrote down everything I've done in the process of installing scalr on a new instance running Ubuntu Intrepid Ibex. I hope it will help other users to install scalr.
Here is the link: http://blog.getasysadmin.com/2008/11/how-to-install-scalr-on-ubuntu-810-ec2.html
If you find errors please let me know. Good luck!
I receive often this error WSSESoapClient::__doRequest? Failure Signing Data (Please, check your keys) in the Shared roles » View section.
The AWS settings is not clear. Account ID = AWS Account Number Key Name is the string between cert-xxxxxx.pem, these files must be copied in the /etc/ Access Key = what is ? Access Key ID = is the public Access Key ID
Maybe The Access Key is the AWS Secret Key ? If yes, the error is not resolved.
Please specify all the value in the Settings » General Section Thanks Fabio
I find the way, finally. The path where must be copied the two files .pem is /etc , but the /etc under the scalr/app/etc. I think more than me has mistaken this.
What's the diff between the scalr-ami/ images and scalr-images/ in ec2-describe-images? Also, do any of the AMIs in ec2 provide an already built, working Scalr install?
after installing (following Octavian´s nice guide), I assume I have to create a new client first before I can create a new app/farm? After creating a new client and trying to login with this new client, I keep on getting the error:
"Incorrect login or password"
anyone can help?
In order to use a freshly created client it needs to be activated..