tych0/juju forked from juju/juju

Signed-off-by: Tycho Andersen <tycho.andersen@canonical.com>

Signed-off-by: Tycho Andersen <tycho.andersen@canonical.com>

"All problems in computer science can be solved by another level of
indirection, except of course for the problem of too many indirections."
-- David Wheeler

Signed-off-by: Tycho Andersen <tycho.andersen@canonical.com>

Signed-off-by: Tycho Andersen <tycho.andersen@canonical.com>

lxd-images is going away, and this way we get all the goodness of the
simplestreams auto-updating that was recently added to LXD. plus we don't
have to exec either.

Signed-off-by: Tycho Andersen <tycho.andersen@canonical.com>

Instead of making people import their own image, let's just do it for them
if it doesn't exist, like we do in the container type.

Signed-off-by: Tycho Andersen <tycho.andersen@canonical.com>

The client code understands the new b4 server.

Signed-off-by: Tycho Andersen <tycho.andersen@canonical.com>

Made storageprovisioner machine

Move the storageprovisioner worker from the machine agent runner to the dependency engine.

(Review request: http://reviews.vapour.ws/r/3919/)

MADE Identity File Writer

Move the Identity File Writer worker from the machine agent runner to the dependancy engine.

(Review request: http://reviews.vapour.ws/r/3951/)

Message listing prior agreements to terms for the deployment.



(Review request: http://reviews.vapour.ws/r/3833/)

rpc: remove Conn.Go method

Conn.Go was never called directly, but was exported in the package's
API. As `go` is a reserved word, this probably explains the method's
public name. Because the method was public, a lot of preconditions, some
panicing had to be set to ensure the method was not called incorrectly.

Remove all of this and collapse `Go` into its single caller, reducing
the API surface, and ensuring it is always called correctly.

(Review request: http://reviews.vapour.ws/r/3992/)

Conn.Go was never called directly, but was exported in the package's
API. As `go` is a reserved word, this probably explains the method's
public name. Because the method was public, a lot of preconditions, some
panicing had to be set to ensure the method was not called incorrectly.

Remove all of this and collapse `Go` into its single caller, reducing
the API surface, and ensuring it is always called correctly.

Lxd container type

This branch is good to merge into master. It is currentish with master. The failures seen on
    http://reports.vapour.ws/releases/3676
are all from master. This branch fixes some of the errors in master, so it is desirable to merge now.
The one bug shown on
     https://bugs.launchpad.net/juju-core/lxd-container-type
is still valid and will affect master when merged. Both the gccgo and golang ppc64el unittests are already broken and need a fix.

(Review request: http://reviews.vapour.ws/r/3991/)

Fix typo in windows test

Wrong env var was patched, should have been USERPROFILE

(Review request: http://reviews.vapour.ws/r/3990/)

merge master into lxd-container-type



(Review request: http://reviews.vapour.ws/r/3989/)

…e-master

fix int overflows in lxdclient test

Signed-off-by: Tycho Andersen <tycho.andersen@canonical.com>

(Review request: http://reviews.vapour.ws/r/3988/)

Signed-off-by: Tycho Andersen <tycho.andersen@canonical.com>

destroy model doesn't use legacy config store

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

juju destroy-model was broken because it still tried to use the legacy config store which we no longer use when creating models


(Review request: http://reviews.vapour.ws/r/3987/)

Update lxd-container-type to support lxd-2.0.0~beta4

This should be all the steps we need to make Juju compatible with LXD 2.0.0~beta4.

This was done in collaboration with Tycho. I've tested it doing a local "juju bootstrap lxd lxd" on Trusty using the 2.0.0~beta4 packages from ppa:ubuntu-lxc/lxd-stable as well as bootstrapping an AWS controller and installing the ppa there as well before doing "juju deploy --to lxd". 

There may still need to be some tests fixed. containers/lxd still expects you to have installed an image into your local lxd server. But I think this is really close to being good enough to land in master.


(Review request: http://reviews.vapour.ws/r/3973/)

…ontainer-type-no-disk

Add a few tests so that we actually know it is doing the right thing.

…hods

api/charms: remove unused methods

Remove all but one method, the rest were unused. This package is
obviously misnamed.

(Review request: http://reviews.vapour.ws/r/3909/)

merge juju master into lxd-container-type



(Review request: http://reviews.vapour.ws/r/3980/)

Remove all but one method, the rest were unused. This package is
obviously misnamed.

Add gce credential detection, improve autoload command

The GCE provider now detects credentials by looking for the json file in known google locations.
The detect credentials method signature is reworked to allow detection to include region.
The autoload credentials command supports the --replace option.
Bootstrap complains if auto credential detection finds > 1 credentials.

Still todo: present detected credentials to user and allow them to choose which to import

(Review request: http://reviews.vapour.ws/r/3971/)

It connects to a real LXD server and creates real containers.
This should become a CI test.