Add flag to enable containers on all providers.
Merge pull request #551 from frankban/containers-feature-flag

Add flag to enable containers on all providers.

Introduce the `containers` feature flag.
Ensure proper committed status on containers.

This fixes bug https://bugs.launchpad.net/juju-gui/+bug/1369601

Containers had been (incorrectly) inheriting their commited status from
their parent machine. That meant that a newly-created container on an
existing machine would show up as committed upon re-render. We now check
for 'new' in the name of each container and set its committed status
based on that. The only exception is root containers, which still
inherit from the parent machine because they *are* the parent machine.
Merge pull request #552 from kadams54/fix-uncommitted-indicator-1369601

Ensure proper committed status on containers.

This fixes bug https://bugs.launchpad.net/juju-gui/+bug/1369601

Containers had been (incorrectly) inheriting their commited status from
their parent machine. That meant that a newly-created container on an
existing machine would show up as committed upon re-render. We now check
for 'new' in the name of each container and set its committed status
based on that. The only exception is root containers, which still
inherit from the parent machine because they *are* the parent machine.
Do not show subordinate services in the mv unplaced unit token list
Added test to make sure we don't render subordinate units as unplaced
Merge pull request #554 from hatched/sub-unplaced-1369576

Do not show subordinate services in the mv unplaced unit token list

This is a temporary fix to not instantiate or render subordinate services as unplaced units in the machine view. A real fix will involve having the service charm data fetch updating the unit information and having juju send the unit subordinate status in the delta.