Support for new status formatter: tabular.
Migrated formatter to its own file. Refactoring.
implemented the default sender
updates for latest version of trunk
syslog: fixes and updates to rsyslogd and logrotate.
Adjust lograte size to prevent a mismatch.
Change rsyslogd size to be actual size instead of a naive value.
some changes after reviewing
start the workers when we start
Introduced new summary formatter. First draft; WiP.
Merge branch 'master' into status-formatter-summary

Conflicts:
	cmd/juju/status.go
	cmd/juju/status_test.go
utils/syslog: updating comments for logrotate config
start the metrics workers; the metricsmanager should rely on a machine agent connection

sensible periods for the metric workers
Merge branch 'master' into status-formatter-tabular

- Migrated FormatTabular to status_formatters.go.
- Migrated return error to github.com/juju/errors
- Removed debugging/panic in an impossible situation.
- Migrated towards use of stack-local byte-buffer rather than a heap-based pointer dereference.

Conflicts:
	cmd/juju/status.go
	cmd/juju/status_test.go
upgrades: migrate uploaded image metadata to environment storage

We no longer search for image metadata in provider storage.
This is the final piece: migrate existing metadata from provider
storage to environment storage, preserving paths and data exactly.
fixes from review
Made indentation level a constant for clarity.
added tests for the default sender
Implemented feedback from review.

- Migrated formatter to status_formatter.go
cmd/juju: ensure that API calls used by "juju ssh" are allowed during upgrades

We recently had a regression where an API call required by "juju ssh"
wasn't being allowed by the API server while upgrades are in progress.
"juju ssh" is one of the few commands that is supposed to work during
upgrades.

The Client used by "juju ssh" is now forced into an interface and this
is checked using reflection against what the API server will allow
during upgrades. Effectively, the compiler helps to check that the
required API methods will be allowed.
apiserver: refactored upgradingRoot method check

Given that the API methods allowed during upgrade are all on the
Client facade, avoid having to write "Client." at the front of each
method name.
Merge pull request #803 from mjs/check-ssh-api-methods-are-allowed-during-upgrade

cmd/juju: ensure that API calls used by "juju ssh" are allowed during upgrades

We recently had a regression where an API call required by "juju ssh" wasn't being allowed by the API server while upgrades are in progress. "juju ssh" is one of the few commands that is supposed to work during upgrades.

The Client used by "juju ssh" is now forced into an interface and this is checked using reflection against what the API server will allow during upgrades. Effectively, the compiler helps to check that the required API methods will be allowed.

http://reviews.vapour.ws/r/64/diff/