Juju is written entirely in python (though a rewrite in Go is underway). In theory it will work fine on OS X, but there are a couple of challenges to making that happen:
* Juju is python, but links to the python zookeeper bindings which are C, so one needs something like homebrew to install Zookeeper.
* Juju does sometimes make assumptions about Ubuntu specific stuff. We need some brave OS X users to try it out start reporting bugs so we can find out where these are and build tests around it (A good start would be if somebody wanted to donate an OS X machine to run the test suite on).
Thats not far from what we're aiming at with Juju. The idea is to encapsulate things so they're easy to mix and match and share between environments. Those scripts you saw were all islands unto themselves, and they had to be mapped onto your server. Juju puts them into "charms", which are just metadata+executables that encapsulate how to deploy a service, and how to talk to it.
The idea is to give people a way to express to one another best practices in a way where it can be used directly (so no need for a human to translate that wiki page into automation.. its done). Then it can be measured, refined, and shared.
* Juju is python, but links to the python zookeeper bindings which are C, so one needs something like homebrew to install Zookeeper. * Juju does sometimes make assumptions about Ubuntu specific stuff. We need some brave OS X users to try it out start reporting bugs so we can find out where these are and build tests around it (A good start would be if somebody wanted to donate an OS X machine to run the test suite on).