Announcing the immediate release of Mercury 0.81-Beta for Amazon in 32 bit and 64 bit versions.
This is a bug-fix release - there are no new features in 0.81-Beta:
1) /etc/init.d/ec2-ssh-host-key-gen was running on reboots. This would present new SSH keys every time the system reboots (Note that we want /etc/init.d/ec2-ssh-host-key-gen to run on first boot and it was doing this correctly). To fix this without migrating to 0.81-Beta, run chmod -x /etc/init.d/ec2-ssh-host-key-gen as root.
2) 0.8-Beta wasn't using all the available caching resources dues to a truncation of the /var/www/pressflow/sites/default/settings.php file and incorrect settings in pressflow. To fix this without migrating to 0.81-Beta:
Make sure the following is present in /var/www/pressflow/sites/default/settings.php:
# Cacherouter: use APC for all local caching
$conf['cache_inc'] = './sites/all/modules/cacherouter/cacherouter.inc';
$conf['cacherouter'] = array(
'default' => array(
'engine' => 'apc',
'shared' => FALSE,
'prefix' => '',
'static' => FALSE,
'fast_cache' => TRUE,
),
);
# Varnish reverse proxy on localhost
$conf['reverse_proxy'] = TRUE;
$conf['reverse_proxy_addresses'] = array('127.0.0.1');And go to Site configuration > Performance and set:
Caching mode: External
Minimum cache lifetime: None
Page cache maximum age: 10 minutes
Page compression: Disabled
Block cache: Enabled
Optimize CSS files: Enabled
Optimize JavaScript files: EnabledThe Mercury install docs (http://groups.drupal.org/pantheon/mercurywiki) and launchpad files (https://code.launchpad.net/projectmercury) have been updated with this information.
As always, please post suggestions here and bugs to https://launchpad.net/projectmercury.
The AMI IDs are:
US 32-bit: ami-b431d3dd
US 64-bit: ami-bc31d3d5
EU 32-bit: ami-671d3613
EU 64-bit: ami-371d3643
Comments
Now released to US-West
We've migrated our 0.81 AMIs to the new US-West region. All future Pantheon and Mercury AMIs will be released to all 3 regions.
The AMI IDs are:
US-West 32-bit: ami-fb3f6ebe
US-West 64-bit: ami-f93f6ebc
--
Greg Coit
Systems Administrator
http://www.chapterthree.com
All of Pantheon now released to US-West
We've migrated the rest of Pantheon to the new US-West region.
Here are a list of all Pantheon AMIs currently available:
--
Greg Coit
Systems Administrator
http://www.chapterthree.com
Question
Could you tell me how to decide to choose between 32 and 64-bit versions? Thanks.
if you load a 32bit version
if you load a 32bit version you will only be able to run a small or medium EC2 instance. If you choose 64 you won't be able to select small or medium, only large or greater.
From there it's a matter of performance and cost.
Doug
@nullvariable | www.nullvariable.com
FFMPEG on production site
Hello,
I'm very interested in testing this AMI and drupal build with pressflow.
I'm currently in the process of setting up a site with (hopefully ;)) lots of video content in the future.
My shared hosting contract is finishing soon, and i'm in the process of deciding whether to go EC2 or VPS.
First i was merely thinking of moving all files to S3, and doing transcoding locally on a VPS, but it would not be very scalable if there would be many video uploads.
+ it would have double the bandwidth costs (uploading to vps, moving to s3).
Therefor my question is: would this build already be suitable for launching a new instance for transcoding and moving files to S3?
I will start setting up in 10 hours, and let me know the findings :)
Thanks!
Transcoding workflow on AWS
Take a look at Lifeguard for Auto-scaling Amazon EC2 with Amazon SQS and use Creeper in your pressflow install. Mercury is ideal as a frontend web server in the whole architecture.
that is awesome
Thanks alot, can't wait to start!
When i have everything up and running i will probably be running some benchmarks, hammering node pages/video's and transcoding at the same time.
Can't forsee how long it would take me, but it would be interesting data i'm sure.
Thanks for project Mercury, and making the web a faster place :)