Charm needed: Juju GUI

Bug #1103035 reported by Gary Poster
12
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Juju Charms Collection
Fix Released
Undecided
Unassigned

Bug Description

Please review lp:~juju-gui/charms/precise/juju-gui/trunk for inclusion in the official charm store. This charm provides the Juju GUI for PyJuju (Go Juju support coming later).

Thanks

Revision history for this message
Robert Ayres (robert-ayres) wrote :

Thanks for your submission. A very nice charm :)

I've tested on EC2 and LXC.

Please see bugs/comments below.

Bugs:
*'curl' needs to be added as an apt-get install dependency if you use the charm under LXC.

*If you use the 'user', 'password' config options then these can be obtained simply by accessing the URL - https://xxx/juju-ui/assets/config.js .

Comments:
*metadata.yaml, for consistency I'd move the maintainer line to below 'summary'.

*I'd mention in the README that you may need to add a https certificate exception for self-signed certificates for port 8080 ('juju-api-port'). I found I couldn't get the UI to appear unless I first accessed on port 8080 and accepted the self-signed certificate.

*I'd anonymise the EC2 address in the README. You never know, this charm might generate accidental traffic for a real site :)

Please fix the bugs and consider the comments, then reopen for a second review.

Changed in charms:
status: New → Incomplete
Nicola Larosa (teknico)
no longer affects: juju-gui
Revision history for this message
Nicola Larosa (teknico) wrote :

Thanks for these comments, Robert. We need more info on one point:

> I'd mention in the README that you may need to add a https certificate
> exception for self-signed certificates for port 8080 ('juju-api-port').
> I found I couldn't get the UI to appear unless I first accessed on port
> 8080 and accepted the self-signed certificate.

This should not be needed. In order to replicate, it would be useful to know on which platform it happens (EC2, LXC, both) and using which browser (Chrome, Firefox, other).

Revision history for this message
Robert Ayres (robert-ayres) wrote :

This is using EC2 and Firefox 18.

Steps to reproduce:

1. Deploy to EC2, using defaults
2. Expose the service
3. Open 'https://ec2-xxx.compute-1.amazonaws.com', accept the self-signed certificate
4. Allow local data storage

- No login screen, just a background

5. Open 'https://ec2-xxx.compute-1.amazonaws.com:8080', accept the self-signed certificate
6. Reopen 'https://ec2-xxx.compute-1.amazonaws.com'

- Login screen appears

Revision history for this message
Nicola Larosa (teknico) wrote :

Robert, we have reproduced the problem, and confirmed that it's Firefox-specific.

A charm branch has landed which addresses all the issues you raised. Can you please have another look? Thanks.

Revision history for this message
Gary Poster (gary) wrote :

Thank you for the extremely helpful review, Robert.

Changed in charms:
status: Incomplete → New
Revision history for this message
Robert Ayres (robert-ayres) wrote :

Great, thanks for fixing the issues.

I've updated the README to reflect charm store links.

Charm has been promulgated!

Changed in charms:
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.