lp:~benji/charms/precise/juju-gui/bug-1284088

Branch merges

Propose for merging

No branches dependent on this one.

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

charmers: Pending requested 2014-03-19

Diff: 117 lines (+48/-9)

2 files modified

scripts/charmsupport/nrpe.py (+27/-2)
scripts/update-nrpe.py (+21/-7)

api

Related source package recipes

No recipes using this branch. (?)

Create packaging recipe

Related snap packages

Related bugs

Related blueprints

175. By Benji York on 2014-03-19

fix bugs found in review

174. By Benji York on 2014-03-19

handle lost nrpe relations

173. By Richard Harding on 2014-03-13

Merged back the new charm release.

172. By Richard Harding on 2014-03-13

Updated to the newest juju-gui release.

171. By Brad Crittenden on 2014-03-05

Constraint parsing from charmworldlib.

The constraint parsing code has been moved to charmworldlib so it has been
deleted here.

Add dependency on charmworldlib and include it in deps.

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

170. By Francesco Banconi on 2014-02-28

Merged back the new charm release.

169. By Francesco Banconi on 2014-02-28

Fix GUI charm broken by npm update.

R=rharding
CC=
https://codereview.appspot.com/67990044

168. By Richard Harding on 2014-02-21

Merged back the new charm release

167. By Richard Harding on 2014-02-21

Update to the 1.0 juju-gui release

166. By Francesco Banconi on 2014-02-21

New deployer version.

The new deployer fixes several bugs, including
- unit errors during deployments;
- only watching the units belonging to services included
  in the bundle being deployed;
- fixed a failure in deploying a bundle when a unit is
  already in error in the environment;
- gui bundle imports can use revision-less charm urls.

Also updated the guiserver/deployer interaction to reflect
changes in the deployer.

Tests: `make unittest`.
QA:
- bootstrap a Juju env;
- deploy the charm (`make deploy`);
- wait for the charm to be ready;
- start watching the guiserver logs:
  `juju ssh juju-gui/0 sudo tailf /var/log/upstart/guiserver.log`;
- from the GUI, deploy the bundle in http://pastebin.ubuntu.com/6965041/ :
  it includes a bad-wolf failtester service that will
  fail with an install error;
- even if bad-wolf units fail, the deployment proceeds:
  the relation between wordpress and mysql is eventually established
  and errors are printed to the guiserver logs;
- wait for the first deployment to be completed;
- from the GUI, deploy the bundle in http://pastebin.ubuntu.com/6965647/ :
  it just includes one haproxy service;
- ensure the bundle deployment proceeds correctly even if
  the environments contains units in an error state;
- done, thank you, destroy the juju environment.

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