Merge lp://staging/~frankban/charms/precise/juju-gui/new-requirements into lp://staging/~juju-gui/charms/precise/juju-gui/trunk
Status: | Merged |
---|---|
Merged at revision: | 126 |
Proposed branch: | lp://staging/~frankban/charms/precise/juju-gui/new-requirements |
Merge into: | lp://staging/~juju-gui/charms/precise/juju-gui/trunk |
Diff against target: |
264 lines (+88/-34) 9 files modified
HACKING.md (+10/-0) Makefile (+4/-1) hooks/utils.py (+9/-17) revision (+1/-1) server-requirements.pip (+26/-0) test-requirements.pip (+3/-7) tests/00-setup (+4/-3) tests/example.py (+2/-1) tests/test_utils.py (+29/-4) |
To merge this branch: | bzr merge lp://staging/~frankban/charms/precise/juju-gui/new-requirements |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
charmers | Pending | ||
Review via email: mp+195100@code.staging.launchpad.net |
Description of the change
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://
- 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.
Reviewers: mp+195100_ code.launchpad. net,
Message:
Please take a look.
Description:
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: pastebin. ubuntu. com/6411548/
- Bootstrap a Juju environment.
- Deploy and expose the GUI (make deploy).
- Wait for the GUI to be ready/started.
- Deploy this bundle: http://
- 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.
https:/ /code.launchpad .net/~frankban/ charms/ precise/ juju-gui/ new-requirement s/+merge/ 195100
(do not edit description out of merge proposal)
Please review this at https:/ /codereview. appspot. com/26130043/
Affected files (+85, -30 lines): deployer- 0.2.8.tar. gz deployer- 0.2.9.tar. gz -0.13.tar. gz -0.15.tar. gz requirements. pip ts.pip
M HACKING.md
M Makefile
A [revision details]
D deps/juju-
A deps/juju-
D deps/jujuclient
A deps/jujuclient
M hooks/utils.py
M revision
A server-
M test-requiremen
M tests/00-setup
M tests/example.py
M tests/test_utils.py