Mike McClurg

Posts Tagged ‘ubuntu

Getting started with Go and Juju

with one comment

So this title probably doesn’t even parse correctly if you haven’t heard of Google’s Go language our Ubuntu’s Juju service orchestration software. I’ve been toying with the idea of writing a Juju service provider for the XenAPI. This would allow people to use Juju to provision services on a pool of XCP or XenServer hosts. Since the Juju team have recently completed the rewrite of Juju from Python to Go, this gives me the perfect reason to teach myself Go.

And I had the perfect opportunity to learn both Go and Juju at last week’s Ubuntu Developer Summit in Copenhagen, where I got to meet most of the Juju core team. After one of the Juju planning meetings, Roger Peppe gave me a hands on intro to setting up a Go environment and building Juju. Now I’ll share the notes I took, to help would-be Go/Juju hackers to get started. (This isn’t an introduction to the Go language, by the way. This is just instructions for setting up the tools necessary for compiling Juju. Check out the Go Tour for help learning Go.)

The first thing to do, of course, is to install Go:

# Install go
sudo aptitude install golang golang-mode

I haven’t been able to get Vim to highlight my Go files, but Emacs and golang-mode work. I’ve managed to get go-mode confused a bit, though, including one weird hang that forced me to kill Emacs.

It turns out that Go isn’t just a compiler, it’s an entire packaging system too. So before you start using Go, you’ll need to set up your GOPATH environment variable to point to some directory (any directory will do; I put mine in ~/go). This is where all your Go source code and compiled binaries will live.

# Set up go environment (add this to .bashrc)
export GOPATH=~/go
export PATH=${GOPATH}/go/bin:${PATH}

Here’s where the package management system comes in. Instead of doing a ‘bzr clone lp:juju-core’ like I imagined I would, instead you tell Go to go fetch your source code:

# Get juju-core and its dependencies
go get -v launchpad.net/juju-core/...

This will tell Go to go to Launchpad and fetch everything under the juju-core path. It will even use bzr to clone the source repo, so you can make changes and commit back to Launchpad. Note the use of the ‘…’ wildcard feature. This will match any path after juju-core/. You could also put the ‘…’ characters in the middle of a path, as in foo/…/bar, and it will match paths such as foo/baz/bar and foo/boz/buz/bar. This reminds me a bit of Xpath’s ‘//’ search feature.

Juju-core isn’t the only thing that Go downloaded for us. Go ahead and check out your $GOPATH/src directory. There should be a directory called launchpad.net which contains juju-core, but there will also be another directory called labix.org. Where did this come from? It turns out that Go will scan the source files it downloads looking for external dependencies. If those dependencies are prefixed with a network address, go will try to download those as well.

I’m not sure how I feel about this, to be honest. It’s pretty cool that it can just go out and find dependencies. But how does it deal with version pinning? I’m sure there’s a good answer to this out there somewhere. (Update: Rog Peppe tells me that the standard way to do this is to encode versions in the library path. I wonder if this would work with a git branch on Github…)

The ‘go get’ command both fetched the Juju source and built and installed it. To see how to build Go source on your own, we’ll nuke the compiled libraries and tell Go to build and install them again.

# Build and install Juju
rm -rf ${GOPATH}/pkg/linux_amd64/launchpad.net/
cd ${GOPATH}/src/launchpad.net/juju-core
go install ./...

One of the best things about Go (and the primary reason Rob Pike developed Go, actually) is the fast compile times. That command above took less than 9 seconds on my laptop. That’s all it takes for Go to compile all the juju-core source code, and all its external depedencies. Doing a quick and dirty ‘find ${GOPATH}/src -name “*.go” | xargs sed ‘/^\s*\/\//d;/^\s*$/d’ | wc -l’ gives me 72135 lines of code, so 9 seconds sounds pretty good.

Go also has a great online help feature. Not only can you get help on the core tools through man pages, but you can get library docs — even for libraries you just downloaded — using the ‘godoc’ command. Here’s documentation for the entire ec2 package:

# Check out documentation for a package
go doc launchpad.net/.../ec2

And here’s documentation for a particular exported name of that package:

# Documentation for a type or function (notice we call godoc directly)
godoc launchpad.net/goamz/ec2 Instance

If you’d rather read your package docs on the web, a great resource is http://go.pkgdoc.org/, which has docs for the standard library as well as many, many third party libraries.

Go will also format your code for you. You can run ‘go fmt <file.go>’ to format a file in place, or use ‘M-x gofmt’ in Emacs. I really should bind that to a shortcut.

# Reformat your code
go fmt <file.go>

And on top of all that, Go also has a built in test framework. Files which end with _test.go are special and are considered test cases. You can use the command ‘go test’ to build and execute these tests. There is a built in unit testing library which I won’t cover here (because I don’t know now to use it yet).

# Run tests in a given directory
go test

So that’s all you need to get started with Go development for Juju. For a good tutorial on bootstrapping Juju, you can take a look at Juju’s Getting Started document.

I’ll hopefully follow this blog up with a status report on my XenAPI service provider for Juju, and how I’ve modified Dmitry Maksimov’s XMLRPC library to work with the XenAPI.

Written by mcclurmc

November 5, 2012 at 6:07 am

Posted in Programming

Tagged with , ,