Use utils/featureflags.
Update juju/utils to get feature flags.
Update cmd and utils dependencies.
Check that the local id is valid, not the doc id.
Be more explicit.
Remove unneeded imports.
Merge branch 'master' into feature-flags
Fix the imports... always the imports.
move InferRemoteUnit inside runner factory, integration tests passing, unit tests broken
fix operation tests
fix uniter/runner tests/code
state: removed unnecessary docID calls

Many calls to State.docID() are now unnecessary since the introduction
of envStateCollection.

This change also adds the openedPorts and subnets collections to the
list of those which contain data for multiple environments.
Move state/storage.go to state/storage/

This moves storage (blobstore) code out of state,
and into the state/storage package. The storage code
is inconsequential to state itself, it just happens
to be co-resident in the Mongo database.

The moved code does not depend on state, but instead
takes an environment UUID and an mgo.Session derived
from a state.State.

In the future we should also move the ToolStorage
code, removing the dependency of state on blobstore
altogether.
juju-run: help message was not properly displaying
merge master
Remove unused import.
worker/certupdater: add "juju-apiserver" as DNS name

The in-tree API clients are using "juju-apiserver" as the
hostname to verify when connecting to the API server,
rather than the actual hostname. The certupdater worker
was not setting this as a DNS name in the certificates it
generates. The Azure provider doesn't record any public IP
addresses, so the verification always takes place and always
fails.

We fix this by adding "juju-apiserver" as a DNS name in the
certificates. Ideally the clients should be using the actual
hostname used to connect with, but this will break backwards-
compatibility with older versions of Juju.

Fixes https://bugs.launchpad.net/juju-core/+bug/1400348
Move add and remove machine to subcommands.
Tweak imports.
Merge pull request #1287 from axw/lp1400348-certupdater-jujuapiserver

worker/certupdater: add "juju-apiserver" as DNS name

The in-tree API clients are using "juju-apiserver" as the
hostname to verify when connecting to the API server,
rather than the actual hostname. The certupdater worker
was not setting this as a DNS name in the certificates it
generates. The Azure provider doesn't record any public IP
addresses, so the verification always takes place and always
fails.

We fix this by adding "juju-apiserver" as a DNS name in the
certificates. Ideally the clients should be using the actual
hostname used to connect with, but this will break backwards-
compatibility with older versions of Juju.

Fixes https://bugs.launchpad.net/juju-core/+bug/1400348