Juju Charms Collection
juju-gui package

lp://staging/~frankban/charms/precise/juju-gui/bug-1086788-jitsu-deploy-to

  1. Precise Pangolin (12.04)
  2. bug-1086788-jitsu-deploy-to
Created by Francesco Banconi and last modified
Get this branch:
bzr branch lp://staging/~frankban/charms/precise/juju-gui/bug-1086788-jitsu-deploy-to
Only Francesco Banconi can upload to this branch. If you are Francesco Banconi please log in for upload directions.

Branch merges

Related bugs

Related blueprints

Branch information

Owner:
Francesco Banconi
Status:
Development

Recent revisions

14. By Francesco Banconi

Fixed install hook and tests.

13. By Francesco Banconi

Checkpoint.

12. By Francesco Banconi

Fixed juju-gui upstart configuration file: now it can be correctly stopped.

11. By Francesco Banconi

Add a test for jitsu deploy-to.

10. By Francesco Banconi

Store values from config.get.

9. By Brad Crittenden

[r=gary, benji] Add command-level logging and real-time output for 'make' command.

8. By Madison Scott-Clary

Serve static files using nginx

The charm now serves static files using nginx. There is another branch to fix the websocket URL in config.js, but until then, the URL will default to localhost.

R=hazmat, teknico, bac
CC=
https://codereview.appspot.com/6898043

7. By Francesco Banconi

Juju GUI charm connects to its environment

This branch implements the ability to deploy the
Juju GUI charm so that it is actually connected to
the real Juju environment.
This is done by starting the juju API agent pointing
it to the Zookeeper address of the environment.
That part is a translation into Python of what Kapil
already did in the bash charm.

Other changes:

Changed README: now python-charmhelpers needs to be
installed to run functional tests. python-shelltoolbox
is installed as a dependency of python-charmhelpers.

Added a juju-api-port config option. The staging and
real API agents use by default different ports. I
decided to add an option so that the user can select
the port where the websocket server will be listening.
In a future branch we should let users customize the
Juju GUI port too.

Added a staging boolean flag to the config options:
by default is False (real env); users can set it to
True to start the staging server.

Also added a staging-environment config option:
if Juju staging is started, here the users can
select what kind of environment to show up in the GUI.

Fixed start up configuration scripts: now upstart
correctly keeps track of the process ids, and the
services can be correctly stopped.

Added an upstart configuration template for the real
API agent.

Added more functional tests, and implemented a
workaround for bug 872264. I run the test suite in ec2
~10 times without failures, setting the jitsu timeout
to 40 minutes.

Note that rsync raises an error during the test process:
rsync: link_stat "/var/lib/juju/units/*/charm.log" failed:
No such file or directory. This is not an error of the tests,
but a test runner failure while trying to retrieve the logs
from a destroyed unit.

R=gary.poster, bac
CC=
https://codereview.appspot.com/6846132

6. By Madison Scott-Clary

Disable console

Adds a configuration variable for whether or not the javascript console object should be enabled or disabled. Defaults to disabled.

R=benji, frankban, gary.poster
CC=
https://codereview.appspot.com/6856112

5. By Francesco Banconi

First deploy charm, with tests.

First pass of the Juju GUI deploy charm, translated to Python from a
shell script prototype written by Kapil. Currently it only uses the
"improv" version of Juju, not the standard one.

It includes both unit and functional tests, the latter using the "test"
Jitsu command recently developed by Jim Baker. The README.txt file
shows instructions for running both kinds of tests.

R=benji, gary.poster
CC=
https://codereview.appspot.com/6842074

Branch metadata

Branch format:
Branch format 7
Repository format:
Bazaar repository format 2a (needs bzr 1.16 or later)
This branch contains Public information 
Everyone can see this information.