~bac/charms/precise/juju-gui/ga-key : changes

~bac/charms/precise/juju-gui/ga-key » Changes from revision 108

From Revision 108 to 89

Rev	Summary	Authors	Date
108	Better description of ga-key Better description of ga-key	Brad Crittenden	10 years ago
107	Remove use-analytics Remove use-analytics	Brad Crittenden	10 years ago
106	Make GA key configurable Make GA key configurable	Brad Crittenden	10 years ago
105	GUI server deployer: update the Import request. GUI server deployer: update the Import request. Updated the Import deployer request so that the Name field is optional if the YAML one contains just one bundle. R=matthew.scott CC= https://codereview.appspot.com/13313044	Francesco Banconi	10 years ago
104	The GUI no longer run from the charm directory. The GUI no longer run from the charm directory. Updated the GUI and (under pyJuju) the API agent so that now the files are served from /var/lib/juju-gui. That directory is also removed when the service is destroyed. To do that, this branch introduces the Backend.destroy method, called in the stop hook. QA: deploy the charm using this branch, check everything is ok, check that the GUI files are stored in /var/lib/juju-gui. Then destroy the juju-gui service and ensure that directory is cleaned up. R=benjamin.saller CC= https://codereview.appspot.com/13309044	Francesco Banconi	10 years ago
103	Merged charmers trunk. Merged charmers trunk.	Francesco Banconi	10 years ago
102	Merged charmers trunk. Merged charmers trunk.	Francesco Banconi	10 years ago
101	Fix WebSocket URL in pyJuju. Fix WebSocket URL in pyJuju. The WS URL must include the /ws path when the GUI is connected to rapi. R= CC= https://codereview.appspot.com/13432043	Francesco Banconi	10 years ago
100	Fix for the upgrade-charm story. Fix for the upgrade-charm story. The builtin-server option is not included in the previous configuration. R= CC= https://codereview.appspot.com/13300045	Francesco Banconi	10 years ago
99	Enable sandbox mode in juju-core environments. Enable sandbox mode in juju-core environments. Also added a sandbox functional test and improved the backend framework unit tests. R=rharding CC= https://codereview.appspot.com/13424043	Francesco Banconi	10 years ago
98	Fix Chrome dev WebSocket sub-protocol error. Fix Chrome dev WebSocket sub-protocol error. Also updated the way we suggest to install system dependencies. Tests: `make unittest` from the branch root. QA: - Install the system dependencies by running the following command from the root of this branch: make sysdeps - Bootstrap a juju-core environment: juju bootstrap --upload-tools - From the root of this branch, deploy and expose the GUI running the following: make deploy The command above will exit when the GUI is ready. - Switch to the GUI server, then wait a minute for the server to be ready: juju set juju-gui builtin-server=true - With a development version of the Chrome browser (>=30), visit the GUI and check everything works well. R=rharding CC= https://codereview.appspot.com/13386043	Francesco Banconi	10 years ago
97	GUI server: logging option and sandbox mode. GUI server: logging option and sandbox mode. This branch includes three changes: - the GUI server logging level can now be set using a charm option; - added support for sandbox mode: when the GUI is run in sandbox mode, the GUI server avoids listening for WebSocket connections; - fixed a bug preventing the builtin server to work when the secure charm option was set to false. Tests: `make unittest` from the branch root. QA: In the steps below I assume your default juju is juju-core and your juju-core env is named "go". - Bootstrap a juju-core environment: juju bootstrap -e go --upload-tools - From the root of this branch, deploy and expose the GUI running the following: make deploy JUJU_ENV=go The command above will exit when the GUI is ready. - Switch to the GUI server, then wait a minute for the server to be ready: juju set -e go juju-gui builtin-server=true - In a separate terminal tab, start watching the GUI server log (the first line should be "starting Juju GUI server v0.1.0"): juju ssh -e go 1 sudo tailf /var/log/upstart/guiserver.log - Use the browser to navigate the GUI, log in and check everything works fine. - Set the logging level to debug, then wait a minute for the cahnge to be applied: juju set -e go juju-gui builtin-server-logging=debug - Now the contents of the WebSocket messages should be included in the GUI server logs. - Switch to HTTP mode, then wait a minute for the cahnge to be applied: juju set -e go juju-gui secure=false - Visit the GUI using http:// and check everything works fine. Note that at this time it is impossible to QA sandbox mode in a juju-core env. This will be fixed in a future branch. R=rharding, gary.poster CC= https://codereview.appspot.com/13340043	Francesco Banconi	10 years ago
96	GUI server: bundles support integration. GUI server: bundles support integration. This branch enables the GUI server bundles support. Changed the hooks so that the new GUI server dependencies are installed. Also added more info to the info handler. Tests: `make unittest` from the branch root. QA: In the steps below I assume your default juju is juju-core and your juju-core env is named "go". - Bootstrap a juju-core environment: juju bootstrap -e go --upload-tools - From the root of this branch, deploy and expose the GUI running the following: make deploy JUJU_ENV=go The command above will exit when the GUI is ready. - Switch to the GUI server, then wait a minute for the server to be ready: juju set -e go juju-gui builtin-server=true - In a separate terminal tab, start watching the GUI server log (the first line should be "starting Juju GUI server v0.1.0"): juju ssh -e go 1 sudo tailf /var/log/upstart/guiserver.log - Use the browser to navigate the GUI, log in and check everything works fine. - Also visit the /gui-server-info URL path: you should see something like: { "uptime": 77, "deployer": [], "apiversion": "go", "version": "0.1.0", "debug": false, "apiurl": "wss://ec2-54-211-156-178.compute-1.amazonaws.com:17070" } - Let's live test the deployer support: to do that, we will use the script in http://pastebin.ubuntu.com/6028073/ - Download the script, edit the PASSWORD value (line 17) and execute it passing the Juju GUI node address as first argument, e.g.: python start-deployer.py ec2-54-227-188-14.compute-1.amazonaws.com - The script runs several API calls, simulates errors in the API parameters (which should also be notified in the GUI server logs), starts two deployments and start watching the second one. It takes some minutes to complete. In the meanwhile, you should be able to see the relevant changes in the topology view. At the end of the process, the GUI should show three started services (wordpress and mysql, connected to each other, and mediawiki), and the output of the script should be similar to this one: http://pastebin.ubuntu.com/6028121/ Note that I added a card to create a charm functional test that automates this live check. - Switch back to the legacy server (haproxy + apaxche2): juju set -e go juju-gui builtin-server=false - Refresh the browser and check everything is ok. Done, thank you! R=bac, rharding CC= https://codereview.appspot.com/12741051	Francesco Banconi	10 years ago
95	GUI server: Deployer and DeployMiddleware. GUI server: Deployer and DeployMiddleware. This branch includes the bundles support base classes. They are already described in the bundles package docstring. The diff is a bit long, sorry about that. Most of the new code are tests. The next branch will integrate and enable the bundle support in the GUI server. Tests: `make unittest` from the branch root. R=benji, bac CC= https://codereview.appspot.com/12802045	Francesco Banconi	10 years ago
94	GUI server: base deployer helpers. GUI server: base deployer helpers. This branch includes some helper functions and objects that are required to implement the Deployer and DeployMiddleware classes. To avoid this branch to include too many changes, the base classes above will be implemented in a separate branch. Tests: `make unittest` from the branch root. R=benji, bac CC= https://codereview.appspot.com/13153043	Francesco Banconi	10 years ago
93	Bundle deployment views. Bundle deployment views. This branch includes the implementation of the bundle views. Their goal is to handle the bundle deployment request/response process. Views interact with the Deployer instance (not yet implemented) in order to schedule, run and observe bundle deployments. R=bac, benji CC= https://codereview.appspot.com/12927049	Francesco Banconi	10 years ago
92	GUI server: deployer blocking functions. GUI server: deployer blocking functions. This branch includes the functions and objects required to interact with the juju-deployer library. These functions are synchronous/blocking, they are stored in the blocking module (inside the bundles package) and they will be executed in a separate process or thread. Also implemented an InfoHandler that will be useful when integrating the GUI server with the charm. Tests: `make unittest` from the root of the branch. R= CC= https://codereview.appspot.com/13106043	Francesco Banconi	10 years ago
91	Asynchronous watcher for bundle deployments. Asynchronous watcher for bundle deployments. This is the first of several branches implementing the bundle deployments support in the GUI server. This branch includes an AsyncWatcher implementation: it will be used to observe the progress of bundle deployments. To give you a wider overview of what will be added, I created the bundle module and added a comprehensive documentation of the pieces that will be used to implement the functionality, and a description of the request/response process. Tests: `make unittest` from the root of the branch. R=benji, bac CC= https://codereview.appspot.com/12903044	Francesco Banconi	10 years ago
90	Add support for nagios-external-master subordinate charm. Add support for nagios-external-master subordinate charm.	Curtis Hovey	10 years ago
89	Integrate the built-in server into the charm. Integrate the built-in server into the charm. Add a "builtin-server" option to config.yaml, defaulting to false, to enable a new Tornado-based built-in web server, in place of haproxy and Apache (still the default). Add a "guiserver.conf" Upstart config file, generated via a template. Add a BuiltinServerMixin to hooks/backend.py . Add tests for the new functions in hooks/utils.py . Clean up all paths and constants in hooks/utils.py . Miscellaneuos cleanup. QA1 (quick): $ make unittest QA2 (long, 40 minutes): $ make ftest QA3 (long but shorter than the former): $ juju bootstrap $ make deploy (check web access) $ juju set juju-gui builtin-server=true (check web access) $ juju set juju-gui builtin-server=false (check web access) $ juju destroy-environment R=frankban, matthew.scott CC= https://codereview.appspot.com/12650044	Nicola Larosa	10 years ago

Older »