Yesterday the earth (or should I say the cloud) trembled with the rename of
ensemble to “juju”. I find the new name to be sexy and cool, and every charm (previously formula) writer automatically becomes a charmer (I like that part ) Apart from that, let’s check out recent goodies that landed in juju since the last report
- William Reade implemented more robust machine killing. In case of any errors, machines are still being killed which is important in pay-as-you-go cloud environments
- William also adds authentication and unicode support to saving files over webdav protocol, which is needed for the Orchestra integration to support deploying physical systems
- Thanks to Jim Baker, the juju command to completely destroy an environment is now more appropriately called “destroy-environment” rather than shutdown. It sounds scarier, which is needed in this case!
- Benjamin Saller fixed a bug such that now a charm’s default configuration values are correctly made available to hooks
- Benjamin also improves juju’s LXC interaction by writing an LXC wrapper and integrating lxc-clone which helps juju deploy LXC containers (for locally deploying charms to your laptop) much faster by cloning a template LXC container
- Kapil Thangavelu has been working hard to improve juju’s openstack compatibility. This allows juju to target openstack (and ubuntu cloud naturally) not only ec2
- Kapil also improved juju’s security backend, and progressed the local developer story writing down foundation code that enables a juju user to deploy or test juju charms on the local machine (or laptop if you will!)
- Kapil also switched juju’s default AMI image to Oneiric Yay!
- Clint Byrum has been working hard to improve juju’s test suite, fixed a bunch of test failures and improved multiple tests as well. Good test coverage is always a sign of a healthy project, and juju is no different
- Last but most definitely not least, juju’s God father Gustavo Niemeyer is working hard to bring the world juju’s Charm Store! A way for juju users to quickly search, find, download and use charms that others from the juju community have contributed. Once ready, this will be huge news, trust me
The short version, juju is rapidly progressing, becoming more mature, more secure. The charm store is starting to materialize, a lot of work is going into juju to support deploying to your local machine, or to Ubuntu cloud (openstack based). Exciting times indeed!
- The NFS charm is now in a working state, this can be backend for any charms that need to have a shared file system
- A whole bunch of charms landed to help deploy an OpenStack cloud from juju! This is quite an achievement, expect a tutorial post soon 😉
- The cassandra charm has been updated
- Membase charm
- Couchbase charm
- PostGres charm is now marked Mature yay!
- A generic Node app container charm is also marked mature
- HAproxy joins the mature charms crowd as well
- Jenkins and Jenkins slave charms are also updated and ready
Wow! that’s a lot of great news! Juju is progressing rapidly, now is a great time to start playing with juju. If you care about a specific piece of software that does not yet have a charm, this is your chance to be the first one to step up and write one! Hop on to #juju on IRC/Freenode and we’ll all help you
So what do you folks think? leave me a comment, let me know your thoughts