cmd/juju: status using the API

cmd/juju: status using the API

Add status cmd to api with state access fallback

Current progress on having `juju status` use the api. Moves the
existing code to a resurrected state/statecmd file. This is
exposed both through the api, and as a fallback to accessing
state directly.

The status tests now pass, but moving some testing down a layer
or two would probably be a good plan.

Is there anything else required for a status first pass?

dimitern: I pulled Martin's branch lp:~gz/juju-core/status_api,
merged trunk and resolved conflicts, also fixed a couple of
tests, but no other changes are made. All tests pass, and
I also did a successful live test on EC2. Original CL is
at: https://codereview.appspot.com/40350043/, and has already
2 LGTMs.

https://code.launchpad.net/~dimitern/juju-core/gz-status_api/+merge/199814

(do not edit description out of merge proposal)

[dimitern, 2013-12-20 14:04:00]

Please take a look.

[rog, 2013-12-20 14:08:19]

LGTM with one additional added comment.

https://codereview.appspot.com/38420046/diff/1/cmd/juju/status_test.go
File cmd/juju/status_test.go (right):

https://codereview.appspot.com/38420046/diff/1/cmd/juju/status_test.go#newcode69
cmd/juju/status_test.go:69: st :=
s.Conn.Environ.(testing.GetStater).GetStateInAPIServer()
// We make changes in the API server's state so that
// our changes to presence are immediately noticed
// in the status.

[dimitern, 2013-12-20 14:30:16]

Please take a look.

https://codereview.appspot.com/38420046/diff/1/cmd/juju/status_test.go
File cmd/juju/status_test.go (right):

https://codereview.appspot.com/38420046/diff/1/cmd/juju/status_test.go#newcode69
cmd/juju/status_test.go:69: st :=
s.Conn.Environ.(testing.GetStater).GetStateInAPIServer()
On 2013/12/20 14:08:20, rog wrote:
> // We make changes in the API server's state so that
> // our changes to presence are immediately noticed
> // in the status.

Done.