Hi all. The Juju GUI team is preparing a new feature [1] that requires some significant changes to our charm [2]. We'd like your help for testing.
If you are deploying a new instance of the GUI, please include "builtin-server=true" in your config. For instance, $ juju set juju-gui builtin-server=true Once the charm has churned a bit, you'll have the change: the service will be running a new server. You can verify this by going to /gui-server-info on the GUI: this exists in the new server and does not in the old one. Let us know--reply here or file a bug [3]--if you encounter any new issues that seem to be related to the new server. If you have a long-running GUI server, even better! Please first upgrade your charm... $ juju upgrade-charm ...and then set the configuration given above. Thanks! Gary [1] The new feature is "bundles". Bundles are pre-configured collections of services that can be deployed together. [2] We had to write our own server in order to provide a way for the GUI to interact with the Juju deployer (https://code.launchpad.net/~juju-deployers/juju-deployer/darwin), which provides the engine for bundles. [3] https://bugs.launchpad.net/juju-gui/+filebug -- Juju mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
