lp://staging/~gary/charms/precise/juju-gui/download-cache

Branch merges

Propose for merging

No branches dependent on this one.

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

charmers: Pending requested 2013-11-19

Diff: 136 lines (+52/-6)

7 files modified

.bzrignore (+1/-0)
HACKING.md (+21/-0)
Makefile (+1/-0)
test-requirements.pip (+19/-0)
tests/00-setup (+8/-1)
tests/deploy.py (+1/-1)
tests/test_deploy.py (+1/-4)

api

Related source package recipes

No recipes using this branch. (?)

Create packaging recipe

Related snap packages

Related bugs

Related blueprints

135. By Gary Poster on 2013-11-19

update test per change

134. By Gary Poster on 2013-11-19

respond to review

133. By Gary Poster on 2013-11-19

add download cache for test dependencies

132. By Brad Crittenden on 2013-11-15

After deploying a bundle increment counter.

The guiserver will make a GET request to the deployment counter incrementer
URL for the bundle. This required accepting the bundle ID in the
Deployer/Import path.

Note neither the GUI nor quickstart have been updated to pass this value yet.

The charmworldurl is also now passed to the server via the command line.

QA: just deploy your favorite bundle and see that it works as it should. You
can observe the bundle page in charmworld and see the counts remain at 0.

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

131. By Gary Poster on 2013-11-14

Sandbox should always use go

On jujucharms, bundle deployment wasn't working because we were using the python sandbox (because jujucharms still uses pyjuju). Thank you to Francesco for noticing, diagnosing, and offering a fix. This is his fix with a quick test.

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

130. By Francesco Banconi on 2013-11-14

Improve charm test venv creation.

Also added missing SYSDEP.

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

129. By Gary Poster on 2013-11-13

changes from released charm

128. By Gary Poster on 2013-11-13

Updated to the newest juju-gui release.

127. By Francesco Banconi on 2013-11-13

Fix base Python dependencies.

The install hook imported charmhelpers
before installing python-yaml, and
charmhelpers imports from yaml.

This very old bug has been hidden by the
fact that python-yaml is automatically
installed in ec2/lxc instances, but showed
itself when using the manual provider.

Copy/pasting and integrating the QA from
my last branch, a double check can help
before the release.
QA:
- Bootstrap a Juju environment with --debug.
- Deploy and expose the GUI (make deploy).
- Check juju debug-log (or
  less ~/.juju/local/log/unit-juju-gui-0.log if you
  used lxc): you should see the following message
  at the beginning of the install hook log:
  "Installing base Python dependencies: python-apt,
  python-launchpadlib, python-tempita, python-yaml."
- Wait for the GUI to be ready/started.
- Deploy this bundle: http://pastebin.ubuntu.com/6411548/
- Check everything is ok, xy annotations work (
  the services are vertically aligned), wordpress has
  customized constraints, mysql customized options and
  two units.
- No try to deploy the same bundle again, you
  will see a "services already there" kind of error.

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

126. By Francesco Banconi on 2013-11-13

Update requirements and improve their handling.

Updated the juju-deployer and jujucleint
dependencies to the latest versions, which
include our recent fixes. This way we avoid
using our own forks of the projects.

Updated the code that installs the builtin
server dependencies: now a pip requirement
file is used, and the test requirement file
includes the former. The overall dependency
infrastructure should now be less confusing.

Also added documentation about how to update
the builtin server requirements.

Removed the no longer required --upload-tools
from the functional tests runner.

The deployer functional tests now also use
bundles including numunits > 1 and constraints.

QA:
- Bootstrap a Juju environment.
- Deploy and expose the GUI (make deploy).
- Wait for the GUI to be ready/started.
- Deploy this bundle: http://pastebin.ubuntu.com/6411548/
- Check everything is ok, xy annotations work (
  the services are vertically aligned), wordpress has
  customized constraints, mysql customized options and
  two units.
- No try to deploy the same bundle again, you
  will see a "services already there" kind of error.

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