-
Committer:
Francesco Banconi
-
Date:
2013-10-09 09:25:26 UTC
-
mfrom:
(113.2.7 local-releases)
-
Revision ID:
francesco.banconi@canonical.com-20131009092526-jyqnh2ldx6d9qzxg
Introduce local GUI releases.
Implemented the new "local" juju-gui-source option.
By default the GUI release is now retrieved from
the charm itself, so that in the deployment process
the charm can avoid connecting to Launchpad.
This should result in the charm being able to be
deployed behind a firewall without the traditional
workarounds. Note that this is not yet demonstrated
and must be QAed in a real firewalled environment.
The process tries is like the following:
- if juju-gui-source is "local", the last tarball
in the releases dir is installed;
- if juju-gui-source is a stable or development version,
the charm checks if that version is present in the
local repository before downloading it from Launchpad.
- the rest of the options should still work as usual
(but some QA could help, e.g. deploying from a branch).
Also updated the charm documentation and added some
missing tests.
Tests: `make unittest` from the branch root
(I am currently running the functional tests).
QA (assuming 0.10.1 is the latest GUI release):
- `juju bootstrap --debug`;
- `make deploy`;
- check the logs: no PPAs are used, the local release
is installed;
- `juju set juju-gui juju-gui-source=0.10.0`;
- check the logs: the release is downloaded from
Launchpad;
- `juju set juju-gui juju-gui-source=0.10.1`;
- check the logs: the charm successfully find
the 0.10.1 release in the local repository and
avoids downloading it from Launchpad.
- keep trying to break the charm in all the ways
you can imagine...
Thank you.
R=matthew.scott, gary.poster
CC=
https://codereview.appspot.com/14545044