lp://staging/~frankban/charms/precise/juju-gui/deployer-unit-errors

Branch merges

Propose for merging

No branches dependent on this one.

Merged into lp://staging/~juju-gui/charms/precise/juju-gui/trunk at revision 166

Marco Ceppi (community): Abstain on 2014-02-20

Juju GUI Hackers: Pending requested 2014-02-20

Diff: 77 lines (+9/-8)

3 files modified

server-requirements.pip (+1/-1)
server/guiserver/bundles/base.py (+4/-4)
server/guiserver/tests/bundles/test_base.py (+4/-3)

api

Related source package recipes

No recipes using this branch. (?)

Create packaging recipe

Related snap packages

Related bugs

Bug #1252301: guiserver reports second bundle as failing after the first fails

High

Fix Released

Link a bug report

Related blueprints

166. By Francesco Banconi on 2014-02-21

Merged trunk.

165. By Francesco Banconi on 2014-02-20

New deployer v0.3.2.

164. By Brad Crittenden on 2014-02-12

Support for juju core constraints

All juju core constraints should be supported by Juju GUI.
See https://juju.ubuntu.com/docs/reference-constraints.html
The 'tags' constraint was not implemented as it is only supported for MaaS
deployments.

R=frankban
CC=
https://codereview.appspot.com/61510051

163. By Francesco Banconi on 2014-02-05

Merged back the new charm release.

162. By Francesco Banconi on 2014-02-05

Bump the charm revision up.

161. By Francesco Banconi on 2014-02-05

Fix sandbox mode.

The proxy handler is now started only if the GUI
is connected to a real environment.

Tests: `make unittest`.

QA:
`make deploy`
`juju set juju-gui sandbox=true`
Wait for the unit to be started.
Ensure everything works well.

R=
CC=
https://codereview.appspot.com/57690051

160. By Gary Poster on 2014-02-04

Add support for cached fonts

Per https://launchpad.net/bugs/1274955 , and building off recently landed work in the GUI itself (https://github.com/juju/juju-gui/pull/104), this adds configuration to support cached fonts.

To QA, deploy the charm with GUI trunk as you wish, and then verify in your browser's inspector's network tab that the font CSS is being downloaded from Google. Then set cached-fonts to true (command line or GUI), wait about ten seconds, do a hard reload on the GUI, and you should see in the network tab that there is no CSS from Google anymore, and there is now a fontface.css delivered locally.

To deploy the charm with GUI trunk, I like to `git pull juju develop` in my GUI trunk, `make clean && make distfile`, copy the release into the charm's releases directory, `juju switch local`, `juju bootstrap`, and `make deploy` in the charm. YMMV: the other option instead of the `make distfile` approach is to use `juju set juju-gui juju-gui-source=develop`.

R=bac
CC=
https://codereview.appspot.com/60130043

159. By Gary Poster on 2014-02-04

Restore development build support

This branch restores the ability to follow the quick trunk deploy workflow.

- In GUI: `BRANCH_IS_GOOD make distfile`
- Copy new release into local GUI charm releases folder
- bootstrap juju and run `make deploy` in charm

This is the fastest way I know to demo or qa a GUI branch with the charm trunk.

R=frankban
CC=
https://codereview.appspot.com/52230045

158. By Francesco Banconi on 2014-02-03

Add jenv file path to the GUI login help text.

Change the GUI login message to give exact
jenv file to look in for the admin secret, if
the environment name is available in the hook's
context.

Tests: `make unittest`.

QA:
1) bootstrap a stable juju-core;
2) deploy this branch with `make deploy`;
3) open the GUI: the login message should point
   you generically to the path where to find
   the jenv files;
4) destroy the environment;

5) bootstrap juju-core trunk (at least revno 2289);
6) deploy this branch with `make deploy`;
7) open the GUI: the login message should point you
   to the exact path to the jenv file;

8) now execute "juju set juju-gui login-help=HELP!",
   and wait a couple of seconds;
9) open the GUI again and you should see the new message;
10) destroy the environment.

Done, thank you!

R=gary.poster
CC=
https://codereview.appspot.com/59560044

157. By Francesco Banconi on 2014-01-31

Update deployer to 0.3.1

Update the juju-deployer package to the newer version.
As a consequence, improve the bundle deployment feedback.

Tests: `make unittest`.

QA:
1) deploy the charm by bootstrapping juju and
then running `make deploy`.

2) wait for the service to be ready/started.

3) Open the GUI.

4) Try to deploy this bundle file:
http://pastebin.ubuntu.com/6844154/

5) You should see an error in the GUI:
The deployment errored: Invalid config charm
cs:~openstack-ubuntu-testing/precise/mysql-4
no-such-option=42

6) Try to deploy this bundle file:
http://pastebin.ubuntu.com/6844187/

7) You should see an error in the GUI:
The deployment errored: Invalid relation in config,
service no-such not found,
rel mediawiki:db <-> no-such:db

Done, thank you!

R=gary.poster, jeff.pihach
CC=
https://codereview.appspot.com/55230044