164.1.3
|
|
|
Francesco Banconi |
10 years ago
|
|
|
164.1.2
|
|
|
Francesco Banconi |
10 years ago
|
|
|
164.1.1
|
|
|
Francesco Banconi |
10 years ago
|
|
|
164
|
|
|
Brad Crittenden |
10 years ago
|
|
|
163
|
|
|
Francesco Banconi |
10 years ago
|
|
|
162
|
|
|
Francesco Banconi |
10 years ago
|
|
|
161
|
|
|
Francesco Banconi |
10 years ago
|
|
|
160
|
|
Add support for cached fonts
Per https://launchpad.net/bugs/1274955 , and building off recently landed work in the GUI itself (https://github.com/juju/juju-gui/pull/104), this adds configuration to support cached fonts.
To QA, deploy the charm with GUI trunk as you wish, and then verify in your browser's inspector's network tab that the font CSS is being downloaded from Google. Then set cached-fonts to true (command line or GUI), wait about ten seconds, do a hard reload on the GUI, and you should see in the network tab that there is no CSS from Google anymore, and there is now a fontface.css delivered locally.
To deploy the charm with GUI trunk, I like to `git pull juju develop` in my GUI trunk, `make clean && make distfile`, copy the release into the charm's releases directory, `juju switch local`, `juju bootstrap`, and `make deploy` in the charm. YMMV: the other option instead of the `make distfile` approach is to use `juju set juju-gui juju-gui-source=develop`.
R=bac CC= https://codereview.appspot.com/60130043
|
Gary Poster |
10 years ago
|
|
|
159
|
|
|
Gary Poster |
10 years ago
|
|
|
158
|
|
|
Francesco Banconi |
10 years ago
|
|
|
157
|
|
|
Francesco Banconi |
10 years ago
|
|
|
156
|
|
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
|
Francesco Banconi |
10 years ago
|
|
|
155
|
|
|
Brad Crittenden |
10 years ago
|
|
|
154
|
|
|
Rick Harding |
10 years ago
|
|
|
153
|
|
|
Brad Crittenden |
10 years ago
|
|
|
152
|
|
|
Francesco Banconi |
10 years ago
|
|
|
151
|
|
|
Francesco Banconi |
10 years ago
|
|
|
150
|
|
|
Benji York |
10 years ago
|
|
|
149
|
|
|
Rick Harding |
10 years ago
|
|
|
148
|
|
|
Rick Harding |
10 years ago
|
|
|