Juju API

[Mark Canonical Ramm-Christensen]

Hi Mike,

Thanks for bringing this all up!

> 1> Is Juju api built to be available for external use (public if you will) ? If so, where can I find the documentation for it?

Our first goal for the API was to support an "external" but highly
trusted component, the GUI.  For that and for the client, we are
exposing an API which we definitelydo expect external users.   We are
also creating a new API designed fo the "internal" agents, and that
one is being designed primarily for our own use.

However for any given API call, if there is a strong use case for it
being public, we can certianly add that to the priority list -- and as
an open source project it probably goes without saying that "patches
are always welcome".   But, since a lot of Go Juju's life so far has
been spent in relative isolation, it is probably not obvious that we
are very much open to contributed code that solves particular people's
needs.

> 2> Can I talk to the state server just with the API only or do I need juju installed on my machine?

Right now, you can talk to the state server over the same API as the
GUI, without any need for a local juju client (or anything other than
the ability to connect to a web socket and parse JSON -- in fact the
GUI does all of this from javascript.)

> 3> When should be expect to have redundancy for the state server available?

There is a tiny bit of undocumented hackery-jiggery-foo that would let
you setup a slave mongo right now.   Then if the state server were to
go down (and not come back) you'd have to do another small bit of
hackery to get the clients working again. Meanwhile fully automated
"state server" redundancy is on the roadmap for later this summer.

--Mark Ramm