For those working on AWS and Eucalyptus, 1.1 brings some nice module improvements as well as a new cloudformation and s3 module. It’s great to see the AWS-related modules becoming so popular so quickly. Here are some more details about the changes but you can find info in the changelog here: https://github.com/ansible/ansible/blob/devel/CHANGELOG.md
Security group ID support
It’s now possible to specify the security group by its ID. This is quite typically behaviour in EC2 and Eucalyptus will support this with the pending 3.3 release. The parameter is optional.
VPC subnet ID
VPC users can now specify a subnet ID associated with their instance.
Instance state wait timeout
In 1.0 there was no way to specify how long to wait…
The first cut of the Ansible deployment playbook for deploying Eucalyptus private clouds is ready. I’ve merged the first “release” into the master branch here: https://github.com/lwade/eucalyptus-playbook. Feedback and contributions are very welcome, please file issues against the project.
This playbook allows a user to deploy a single front-end cloud (i.e. all component on a single system) and as many NC’s as they want. Although admittedly I’ve only tested with one so far. I’ve followed, to a certain degree, the best practices described here: http://ansible.cc/docs/bestpractices.html
Overall I’m pretty happy with it, there are some areas which I’d like to re-write and improve but the groundwork is there. It was all very fluid to start with and doing something multi-tier has been enjoyable. I’ve also learnt what its like to automate a deployment of Eucalyptus and there are probably a number of things we should improve to make it easier in this…
My previous post talked a little bit about new functionality from (new and updated) ec2-related modules in the Ansible 1.0 release. In this post I’ll go through the practical example of launching multiple instances with the ec2 module and then configuring them with a workload. In this case the workload will be the Eucalyptus User Console :)
For those who are unfamiliar with ansible, check out the online documentation here. The documentation itself is in a pretty good order for newcomers, so make sure to take it step by step to get the most out of it. Once you’ve finished you’ll then come to realise how flexible it is but hopefully also how *easy* it is.
To launch my instances and then configure them, I’m going to use a playbook. For want of a better explanation a playbook is a yaml formatted file containing a series of tasks which…
You may be forgiven for thinking that a version 1.0 software release indicates some sort of significant milestone for the lifecycle of a project. Perhaps in many cases it does but with Ansible, not so much. Michael DeHaan articulates it much better than I could in this post to the project mailing list. My personal experience from using Ansible since v0.8 is that each release delivers consistency, quality and increased flexibility. It’s great to see fast releases delivering something which is incrementally more useful and enjoyable to use. There’s always new handy stuff in each release.
For those using AWS and Eucalyptus, Ansible 1.0 is a perfect example of incremental AWSomeness (geddit?!). Along with a host of other improvements it delivers the following for AWS/Eucalyptus users:
An updated ec2 module; ported to boto by our very own tgerla and now with the capability to launch multiple instances. It works…
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…