lp://staging/~frankban/charms/precise/juju-gui/deployer-031

Branch merges

Propose for merging

No branches dependent on this one.

Merged into lp://staging/~juju-gui/charms/precise/juju-gui/trunk at revision 157

charmers: Pending requested 2014-01-30

Diff: 15 lines (+1/-3)

1 file modified

server-requirements.pip (+1/-3)

api

Related source package recipes

No recipes using this branch. (?)

Create packaging recipe

Related snap packages

Related bugs

Bug #1252295: guiserver bundle deployment error is empty

High

Fix Released

Link a bug report

Related blueprints

157. By Francesco Banconi on 2014-01-30

Update to new deployer release.

156. By Francesco Banconi on 2014-01-29

Add putcharm support to the GUI server.

Implement a proxy handler propagating requests/responses from
the GUI to the real juju-core HTTPS endpoint.

Tests: `make unittest`.

QA:
QA must be done using juju-core trunk.
I used revno 2265 for the following.

1) Bootstrap a juju environment, deploy the GUI charm
and get the latest GUI sources:
    juju bootstrap
    make deploy
    juju set juju-gui juju-gui-source="https://github.com/juju/juju-gui.git"

2) wait for the GUI to be ready
(using `juju debug-log` or `tailf ~/.juju/local/log/unit-juju-gui-0.log`
if you bootstrapped a local environment).
This step takes a while.

3) Open the GUI with Chrome and log in. Open the network tab of the
Chrome JavaScript console and refresh.

4) In the terminal, open and observe the GUI server logs:
    juju ssh juju-gui/0 sudo tailf /var/log/upstart/guiserver.log

5) Drag and drop a zipped archive of a local charm.
Charm files (e.g. metadata.yaml) must be on the zip root.
You can use an haproxy archive I used for tests:
it is available in http://ubuntuone.com/3FRDrcjSECyHp3xLmMIZLY

At this point you should see a 200 response in the gui server logs,
and a notification in the GUI itself.
Moreover, if you inspect the request from the JavaScript console,
you should see a response including info about the charm you
just uploaded: if you used haproxy, you should see
{"CharmURL":"local:precise/haproxy-0"}.

Done!. If you want additional fun, you can now try to
execute the following in the Chrome console:
    app.env.deploy('local:precise/haproxy-0', 'myservice', null, null, 1)
Replace "local:precise/haproxy-0" with the charm URL you used.

In a couple of seconds you should see the "myservice" box appearing
in a pending state. Congratulations, you deployed a local
charm from the GUI! :-)

6) Destroy the environment.

R=gary.poster, jeff.pihach
CC=
https://codereview.appspot.com/57820043

155. By Brad Crittenden on 2014-01-22

Bump juju-deployer to pre-release fix.

New version of juju-deployer handles constraints with size specifiers like
'4G'.

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

154. By Richard Harding on 2014-01-22

Add a log when skipping updating juju-gui-source

153. By Brad Crittenden on 2014-01-22

Bump juju-deployer to pre-release fix.

New version of juju-deployer handles constraints with size specifiers like
'4G'.

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

152. By Francesco Banconi on 2014-01-22

Merged back the new charm release.

151. By Francesco Banconi on 2014-01-22

Updated to the newest juju-gui release.

150. By Benji York on 2014-01-21

Ignore inodes when generating etags.

Since the inode for a given file will vary across servers, using inode to
generate etags when there are multiple back-end servers means that the etags
for a given URL will vary depending on which back-end fulfilled the request.

R=benji-york
CC=
https://codereview.appspot.com/55210044

149. By Richard Harding on 2014-01-16

Change juju-gui-source to be git-enabled.

- Allow pulling from various repo urls
- Support checking out a branch name
- Support checkout out a direct sha
- Remove support for the trunk releases.

The list of what you can check out is simplified a bit. You can easily use the
git access, url, or a local file in the releases directory to enable loading
the gui with any combination of code you would like to use.

Drive by removing some left over bits of the PyJuju branch previously.

148. By Richard Harding on 2014-01-15

Remove support for PyJuju and rapi from charm.

- Removes the support for running rapi/pyjuju.
- Removes the agent used to communicate with zookeeper.
- Removes anything pertaining to zookeeper.
- Attempts to clean up docs and such to make sense with pure juju-core.