lp:~bac/charms/precise/juju-gui/1086790

Created by Brad Crittenden on 2012-12-07 and last modified on 2012-12-10
Get this branch:
bzr branch lp:~bac/charms/precise/juju-gui/1086790
Only Brad Crittenden can upload to this branch. If you are Brad Crittenden please log in for upload directions.

Branch merges

Related bugs

Related blueprints

Branch information

Owner:
Brad Crittenden
Status:
Development

Recent revisions

10. By Brad Crittenden on 2012-12-10

Detabify

9. By Brad Crittenden on 2012-12-07

Changes from review: formatting, adding comments, clarifications.

8. By Brad Crittenden on 2012-12-07

Add command-level logging and real-time output for 'make' command

7. By Francesco Banconi on 2012-12-03

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 on 2012-11-30

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 on 2012-11-28

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

4. By Benji York on 2012-11-21

Initial project structure, mostly testing.

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

3. By Benji York on 2012-11-14

watch the world burn

2. By Benji York on 2012-11-14

add tests and flesh out README.txt

1. By Benji York on 2012-11-14

initial commit

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.

Subscribers