2015/03/18 - Apache Whirr has been retired.

Whirr

• About
• Download
• Road Map
• Wiki
• FAQ

Project Information

• Summary
• Mailing Lists
• IRC
• Team
• Issue Tracking
• License
• Sponsorship
• Thanks
• Security

Documentation

• Home
• Whirr in 5 Minutes
• Quick Start Guide
• Configuration Guide
• API Guide
• Javadoc
• Release Notes
• Known Limitations
• Supported Services and Clouds

Apache Whirr is a set of libraries for running cloud services.

Whirr provides:

• A cloud-neutral way to run services. You don't have to worry about the idiosyncrasies of each provider.
• A common service API. The details of provisioning are particular to the service.
• Smart defaults for services. You can get a properly configured system running quickly, while still being able to override settings as needed.

You can also use Whirr as a command line tool for deploying clusters.

Download a release of Whirr from a nearby mirror.

Start with Whirr in 5 Minutes or the Quick Start Guide.

There is also an FAQ which covers how to achieve common tasks with Whirr, and a configuration guide for reference.

Find out more about Whirr at our wiki.

Have you got a suggestion for improving Whirr? It's easy to get involved.

The code that would become Whirr started out in 2007 as some bash scripts in Apache Hadoop for running Hadoop clusters on EC2. Later the scripts were ported to Python for extra features (such as EBS support) and a wider range of cloud providers. These Python scripts are no longer supported, but can be found in the 0.5.0 release and the contrib-python SVN branch.

In May 2010 the Apache Whirr Incubator project was started to give a home to the existing work that had been done, but also to create a Java version using jclouds as the cloud provisioning library. jclouds supports many providers and has a very rich API for running code on instances, so it provides a very solid foundation for building Whirr on.

In August 2011 Whirr became an Apache Top-Level Project.