Eucalyptus Recipe of the Month Challenge

Its time!

Eucalyptus Hoodie, Shirt, Coffee Mug, Frisbee, and Stickers

Eucalyptus Swag

We are issuing a challenge to the Open Source community.  The challenge is called the “Recipe of the Month Challenge”.

The Rules:

  • Documentation on what application(s) the recipe deploys and how to use it. This also includes what is the purpose of the application(s). (Documentation should be easy to follow and straight-forward.  This will help with the judging and testing of the recipe)
  • Any scripting language/configuration management software can be used. Some examples are as follows:
  • Mention the Image (EMI) used by recipe.  (for example: UEC image, Turnkey image or EMI from emis.eucalyptus.com)

The following categories will be used for judging [scale from 1 (lowest) to 10 (highest):

  • Complexity (the more simple and elegant, the better)
  • Deployment speed/efficiency
  • Failure resiliency (how quickly can the solution return to a healthy operational state after an outage)
  • Creativity

Available swag awards:

  • Eucalyptus Hoodie (color available – dark grey)
  • Eucalyptus Electric Cloud Shirt (colors available – black or white)
  • Eucalyptus Contributor’s Coffee Mug
  • Various Eucalyptus stickers

The winning recipe will be made available on the Eucalyptus Recipes Github repository.  Submissions will be accepted at the beginning of each month.  All submissions must be made to the Recipes mailing list.  The last day allowed for submissions will be the 25th of the month (this allows us time to test out each recipe and grade accordingly).  Feel free to use the Eucalyptus Community Cloud as a testbed for your cloud recipe.   Results announcing the winner will be posted to the Recipes, Images, and Eucalyptus Open Community mailing lists (for more information concerning the mailing lists, please visit the Eucalyptus Mailing Lists page).

Look forward to seeing the recipes.  Remember, its all about creativity, deployment speed, and failure resiliency.  Please send all questions, suggestions, additional ideas to the Recipes Mailing list.

Good luck!  Let the Challenge begin!

PSA from Ubuntu

hspencer77:

Good insight as to the hard work Ubuntu puts into their UEC images. A highly recommended read…..

Originally posted on Sometimes Lucky, But Smart Everyday:

The amount of uptake seen with Ubuntu Server over the past year has been extremely rewarding and simply amazing.  Infrastructure as a Service (IaaS), a.k.a. Public Cloud, providers are popping up left and right, all wanting to provide Ubuntu Server…all helping to further cement Ubuntu Server’s position as the OS for the cloud.

With that said, I’ve started to become concerned about the way in which some of these IaaS providers distribute Ubuntu.  Ubuntu developers create, publish, and regularly update images on Amazon Web Services and Microsoft Azure.  Canonical hosts and maintains internal archive mirrors in these clouds to provide a low-latency, low-cost update mechanism to users.  Finally, Canonical engineers purposely designed in a pluggable cloud provider API approach to Ubuntu’s service orchestration application, Juju, to lower the operational barriers that often place limitations on cross-cloud workload and service migrations.  We do all this to help ensure cross-platform…

View original 375 more words

hspencer77:

Good layout of configuration management recipes that can be used with Eucalyptus/AWS. Looking forward to contributing to this project. Good work Andrew!

Originally posted on Semi-Empirical Shenanigans:

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 Puppet and Chef with the possible expansion to more options (Fabric, Ansible, etc) in the future. The project will be showing users basic techniques to get started with configuration management once their cloud is up and running. The project will also attempt to tie in the plentiful resources already available from these vibrant communities to extend the flexibility of deployments.

To help users with this a repository on GitHub has been created. The simple structure will…

View original 328 more words