The recent release of Eucalyptus 3.3.0 delivers meaningful features which make possible a new level of IaaS usage. This is the start of a series of blog posts which illustrate what is now possible to do with in Eucalyptus.
The 3.3.0 release has a number of noteworthy new features. First, we have new services:
Then, we have expanded the known set of SDKs which are meant to work against AWS, but can also be pointed (by configuring the endpoint and service path appropriately) at Eucalyptus:
@mdshaonimran in his great post summarizing the changes in this release.
The fruits of our laborsExpanding the AWS services implemented and improving the coverage of SDKs enable a new (and unpeered) level of compatibility. New because tools which depend on missing services are non-starters: three new services arrived in this release. Unpeered because, to date, related efforts have yet to be fruitful. Today, Eucalyptus makes it possible to do exciting new things.
With the 3.3.0 release, use cases previously restricted to AWS are now possible using Eucalyptus. I'll be writing a series of posts on how to get going , the main category is:
- Netflix OSS: Progressively we add the ability to run parts (and soon enough all of) the Netflix cloud platform.
Others have made similar posts and surely more will follow:
- ElasticWolf had a pup with @vicnastea, creating a Gov.Cloud friendly client.
- AppScale (congrats on the launch today!) running on Eucalyptus from @mdshoanimran.
This is the story of EucalyptusYou can read along with me in your data center. You'll know its time to turn the page when your hear the chimes ring like *this*.
All of these posts will assume that you have a working 3.3.0 cloud setup. To do that you have a couple of options:
- Follow the excellent post from
@paul_weiss Follow another excellent post from @lesterwade about using Ansible
- See the get started page
- See the install guide