lp:~frankban/juju-quickstart/unicode-all-the-things

Branch merges

Propose for merging

No branches dependent on this one.

Merged into lp:juju-quickstart at revision 30

Juju GUI Hackers: Pending requested 2013-12-06

Diff: 1249 lines (+370/-148)

19 files modified

juju-quickstart (+3/-1)
quickstart/__init__.py (+4/-1)
quickstart/app.py (+13/-5)
quickstart/juju.py (+4/-4)
quickstart/manage.py (+27/-7)
quickstart/models/charms.py (+27/-16)
quickstart/models/envs.py (+15/-12)
quickstart/serializers.py (+47/-0)
quickstart/settings.py (+2/-0)
quickstart/tests/helpers.py (+3/-1)
quickstart/tests/models/__init__.py (+15/-0)
quickstart/tests/models/test_charms.py (+14/-12)
quickstart/tests/models/test_envs.py (+3/-1)
quickstart/tests/test_app.py (+4/-2)
quickstart/tests/test_juju.py (+7/-5)
quickstart/tests/test_manage.py (+32/-5)
quickstart/tests/test_serializers.py (+58/-0)
quickstart/tests/test_utils.py (+46/-38)
quickstart/utils.py (+46/-38)

api

Related source package recipes

No recipes using this branch. (?)

Create packaging recipe

Related snap packages

Related bugs

Related blueprints

33. By Francesco Banconi on 2013-12-06

Done

32. By Francesco Banconi on 2013-12-06

Add missing tests.

31. By Francesco Banconi on 2013-12-06

Merged trunk.

30. By Francesco Banconi on 2013-12-06

Checkpoint.

29. By Francesco Banconi on 2013-12-06

Fisrt pass.

28. By Francesco Banconi on 2013-12-05

Bumped version up for new release.

27. By Brad Crittenden on 2013-12-04

Handle cases where default-series is problematic.

If the bootstrap node is not the default (currently precise) then it is bad
for deploying the Juju GUI since the charm is only currently available for
precise.

If an environment is already booted to non-precise or the default-series is
set to something other than precise then special care needs to be taken. All
of the scenarios are summarized in this note:

http://bit.ly/1cXiPIW

The three QA steps will all re-use the following command to invoke Quickstart:

% .venv/bin/python juju-quickstart \
   --gui-charm-url cs:~juju-gui/precise/juju-gui-136 \
   bundle:~bac/muletrain/6/wiki

All of the following use ec2, so:

% juju switch ec2

1) No default-series.

Destroy any existing environment.
Edit ~/.juju/environments.yaml and comment out default-series for ec2.
Run Quickstart as above.

Expect: Three machines (BSN and GUI on 0) all precise.

2) Non-precise default-series

Destroy any existing environment.
Edit ~/.juju/environments.yaml and set 'default-series: raring' for ec2.
Run Quickstart as above.

Expect: Four machines
 0 - bootstrap node, raring
 1 - GUI, precise
 2 & 3, bundle services, precise because that's what their charms are.

Look at the output generated. You should see

setting the default-series to raring

Also do a
% juju get-env
The default-series should be raring.

3) Existing environment with non-precise.

Destroy any existing environment.
Edit ~/.juju/environments.yaml and set 'default-series: raring' for ec2.
% juju bootstrap
Run Quickstart as above.

Expect: As #2 without the message about setting the default-series.

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

26. By Gary Poster on 2013-12-04

Fix GUI connection problems

This fixes two problems. One was introduced by the authtoken work: if you deployed a bundle, then quickstart could no longer launch a browser. The other was pre-existing, I believe, but related: if it took too long to connect to the GUI server, then quickstart would fall over.

To QA, I suggest simply trying to run `.venv/bin/python juju-quickstart bundle:~jorge/jenkins/5/jenkins-scalable` or similar, and verify that the browser opens as expected. To also test authtoken, you could instead run `.venv/bin/python juju-quickstart --gui-charm-url cs:~juju-gui/precise/juju-gui-136 bundle:~jorge/jenkins/5/jenkins-scalable`. The second spelling should log you in automatically.

Thank you!

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

25. By Francesco Banconi on 2013-12-04

Envs management: code reorganization.

This branch includes code reorg as
a preparation for the upcoming envs
management work.

It's just about mechanically moving code
to the new models package, except for a
minor fix to test_init_environment in
test_manage.py.

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

24. By Madison Scott-Clary on 2013-12-02

Run juju init if environments.yaml is missing

Create environments.yaml and use local provider if environments.yaml is not found.

To test: make check

To QA:
1. mv ~/.juju/environments.yaml ~/.juju/environments.yaml.bak
2. .venv/bin/python juju-quickstart <bundle> # should run juju init and juju switch local
3. ensure deployment goes as planned, ensure ~/.juju/environments.yaml is default from init
4. mv ~/.juju/environments.yaml.bak ~/.juju/environments.yaml

R=bac, frankban
CC=
https://codereview.appspot.com/34260044