DHX: A Customized Hook Debugging Environment Plugin

Following on from my previous post, I created a Juju plugin that allows you to fully and automatically customize the machines created by Juju, for the purposes of making developing and debugging hooks as painless as possible.

Continue reading…

A laymans guide to the "Big Data" ecosystem

Have you been confused by the big data landscape before? there are literally tons of applications that can comprise a big-data ecosystem. Each with their own contributions to the over-arching goals of the data-scientist leveraging these components.

I’ll take you through a guided tour of the big data landscape, and offer some down to earth guidance to get started rapidly in this evolving ecosystem leveraging Juju as your delivery mechanism.

A laymans Guide to Big data

Using the Default tmux Key Bindings with debug-hooks

The Juju debug-hooks command is a great tool when developing charms. However, one point of friction I've had with it is the lack of customizability of the environment it creates, particularly with the screen-style key bindings that tmux is configured to use.

This week, however, I discovered it was fairly trivial to revert the key bindings for tmux in a debug-hooks session. All that is needed is to create (or replace) /home/ubuntu/.tmux.conf with an empty file. This can be done quite easily with a juju ssh command, and so I set up the following alias on my local machine:

function juju-debug-hooks() {
    juju ssh $unit 'echo -n > .tmux.conf' && \
    juju debug-hooks "$@"

Now, instead of juju debug-hooks, I use juju-debug-hooks and I get normal tmux bindings, including using Ctrl-B as the prefix instead of Ctrl-A so that I can once again use Ctrl-A to jump to the start of the current command line in bash.

A Tale of Two Deployments

By: @bcsaller w/ @whitmo

At the Juju Solutions sprint in Dillon Chuck Butler demoed a nice example of using the Rails charm to deploy a sample app/workload right out of github https://github.com/leereilly/github-high-scores.git. The rails charm serves as a great example of framework charm, automating many of the common tasks around running and managing a Rack served application.

I’ve spent the last few months working on using Juju to deploy and manage a system that also helps deploy and manage applications: CloudFoundry. Strikingly, this charm provides a user a similar develop and deploy experience as using a PAAS like Cloudfoundry, Heroku or OpenShift

My curiousity piqued, I did an experiment to compare the the relative experience of deploying a rails app via a framework charm vs. the experience of deploying the same app into a PAAS.

Continue reading…

Charm Testing

To help ensure the quality of items in the Charm Store, we’ve been working on automated testing for charms and bundles. What follows is a summary of the current state of charm testing, plans for the future, and some testing-related tips and recommendations for charm authors.

Continue reading…

Charm Templates

Within Charm Tools, the charm create command makes it easy to create a charm that follows the recommended structure and includes all the right pieces. While the -t option is discussed in the documentation, I wanted to take a moment to call it out specifically, as well as briefly talk about the new default template.

Continue reading…

Deploying ElasticSearch clusters with Juju and Ansible

ElasticSearch is one of those tools that’s just handy to have. When combined with Logstash and Kibana, you can use the “ELK” stack for all sorts of things.

One thing we’d like to see is to bring these capabilities to our users. So I’ve been working on bundling together some of our ElasticSearch resources in Ubuntu so we can bring them to the cloud.

Continue reading…