ec2baseAmazon EC2 by Robot and Me |
|
http://www.infoq.com/interviews/grigorik-tokyo-cabinet
Summary
Ilya Grigorik discusses his company’s PostRank algorithm for tracking reader engagement with content. Also: his experience scaling MySQL, Tokyo Cabinet, Ruby HTTP libs, Solr, Amazon EC2 and more.
http://code.google.com/p/mcollective/
The Marionette Collective aka. mcollective is a framework to build server orchestration or parallel job execution systems.
Primarily we’ll use it as a means to programmatically execute actions on clusters of servers. In this regard we operate in the same space as tools like Func, Fabric or Capistrano.
We’ve attempted to think out of the box a bit designing this system by not relying on central inventories and tools like SSH, we’re not simply a fancy SSH “for loop”. MCollective uses modern tools like Publish Subscribe Middleware and modern philosophies like real time discovery of network resources using meta data and not hostnames. Delivering a very scalable and very fast parallel execution environment.
http://github.com/iconara/piglet
Piglet is a DSL for writing Pig Latin scripts in Ruby:
a = load ‘input’
b = a.group :c
store b, ‘output’
The code above will be translated to the following Pig Latin:
relation_2 = LOAD ‘input’;
relation_1 = GROUP relation_2 BY c;
STORE relation_1 INTO ‘output’;
The aim is to support most of Pig Latin, but currently there are some limitations.
http://stackoverflow.com/questions/1653101/rails-based-ec2-ami
Having said that: Some time last year I used EC2 on Rails. It’s decent, but not very flexible. It also uses mongrel_cluster instead of Passenger. Apparently there’s a way to set up a cluster, but frankly at that point there are probably better alternatives.
http://railsdog.com/blog/2009/12/generating-pdfs-on-ec2-with-ruby/
The caveat of this decision is that in addition to the numerical outputs, three graphs and a summary (both in HTML and PDF) would need to be generated for each permutation. Since there were 3600 permutations, this would amount to 18000 files in total. Initial local runs of our generation process took about 30 seconds for each permutation, mostly due to embedding the graph images into the PDF. On a single machine, that would take 30 hours of uninterrupted processing! Clearly, this was a job for “the cloud”.
http://www.scribd.com/doc/24368319/Cooking-up-a-Cloud-with-Chef-EC2
Chef is a young and ambitious Ruby DSL built for easy configuration management. Nick Zadrozny will take a look at the philosophy of configuration management, the basics of Chef, and some recipes to build out a basic Rails server. Watch a video at http://www.bestechvideos.com/2009/12…
http://code.fotopedia.com/blog/2009/12/how-we-use-chef.html
Chef is a (young) very powerful system integration framework. When we started developing the Fotopedia server apps and infrastructure, we were already sold on automation. Initially, we had a hairy collection of script shells to install our server components. The goal was – and it did not change – to have a standardized way to configure a remote server and to set up a local virtualized linux instance for development purposes. A bit later, we switched to Puppet, when we set up fully separated testing and production environments.
http://rubyhitsquad.com/Ruby_Hit_Squad.html
Basically, attack on Capistrano.
Grab the popcorn.
• Do the simplest thing that could possibly work.
• Nothing to 1.0 in four(ish) days.
• Targets the 80% use case.
• Uses Rake, as god intended.
• Use the right tool for the job (ssh, rsync, etc).
• Fold in the Rails Machine recipes.
• Clever is bad. Period.
http://probablyinteractive.com/2009/3/29/Amazon%20EC2%20+%20Chef%20=%20Mmmmm.html
One of the perceived downsides of EC2 is that the instances aren’t persistent. That’s where Chef comes in! Chef is like a little system admin robot… you tell it how you want your system configured and it will do all the dirty work on the server.
http://ec2onrails.rubyforge.org/
EC2 on Rails is an Ubuntu Linux server image for Amazon’s EC2 hosting service that’s ready to run a standard Ruby on Rails application with little or no customization. It’s a Ruby on Rails virtual appliance.
