Note: beta still means beta. We're aiming for release candidates for Eucalyptus 3.1 within the next month or so. Still, these packages are pretty stable for us so far, pass the majority of our ridiculous battery of QA tests, and are altogether suitable for a quick install to see what the fuss is all about.
Automation and configuration management is a big part of any successful cloud deployment. Whether on AWS, Eucalyptus or another cloud provider, having services that can be easily spun up and down with a consistent configuration is a must at cloud scale. The recipes project is looking to assist new cloud users with a first step.
The recipes project is attempting to be as vendor agnostic as possible by using both…
It's taken a while, but the move is complete. The source code for Eucalyptus 3.1 Beta is open and publicly available in Github. It's actually been there for a while now, but we've done enough housekeeping and we're ready to open the doors.
Build instructions can be found in the INSTALL file, but they are still in flux; comments and patches are welcome.
It is sort of becoming a tradition for each member of the Fedora Board to declare a personal goal of some sort and then lead by doing. So now that I am the newest Board member, some people are curious about my plans.
In 2010 I helped get Fedora's Cloud SIG off the ground. At that point in time our main goal was to get a modern version of Fedora running inside Amazon's popular cloud, EC2.
Today I did some work on a branch in git only to discover that I based it on some unstable code rather than the stable code that I usually want to use as a baseline.
You can fix this by using a bit of git's rebase magic:
This moves the entire current branch onto another.