*A new development release of Juju is here, 2.4-beta3.## New and Improved - ‘Relations’ section in status output has been cleaned up:- When filtering by application name, only direct relations are shown;- In tabular format, ‘relations’ section is no longer visible by default (bug # 1633972 <https://bugs.launchpad.net/juju/+bug/1633972>). Use ‘--relations’ option to see the section.- Clarified empty status output - whether it is due to a model being empty or because a provided filter did not match anything on the model (bugs 1255786 <https://bugs.launchpad.net/juju-core/+bug/1255786>, 1696245 <https://bugs.launchpad.net/juju/+bug/1696245> and 1594883 <https://bugs.launchpad.net/juju/+bug/1594883>).- New model proxy config values for new proxy behaviour. Using the existing model config for juju proxy remain unchanged, and any existing model or controller should not notice any changes at all. There are now four new model config properties are:- juju-http-proxy, juju-https-proxy, juju-ftp-proxy, juju-no-proxyThese proxy values are used by the model for downloading charms, but are not set as the normal proxy environment variables for charm hook contexts, nor written as default systemd config values.The juju-no-proxy can and should contain CIDRs for subnets. The controller machines are not added automatically to the juju-no-proxy value, so the internal network that is used should be in the juju-no-proxy value if there are other proxies set.The new proxy values are passed in to the charm hook contexts, but as the following environment variables: JUJU_CHARM_HTTP_PROXY, JUJU_CHARM_HTTPS_PROXY, JUJU_CHARM_FTP_PROXY, and JUJU_CHARM_NO_PROXY. The charm helpers library will be gaining the ability to use proxies for certain activities. This is new behaviour and still being developed.The rationale behind this change is to better support proxies in situations where there are larger subnets, or multiple subnets that should not be proxied. The traditional no_proxy values cannot have CIDR values as they are not understood by many tools.## FixesFor a list of all bugs fixed in this release, see https://launchpad.net/juju/+milestone/2.4-beta3 <https://launchpad.net/juju/+milestone/2.4-beta3>Some important fixes include:* fixes for when /var, /etc, /tmp are on different partitionshttps://bugs.launchpad.net/bugs/1634390 <https://bugs.launchpad.net/bugs/1634390>https://bugs.launchpad.net/bugs/1751291 <https://bugs.launchpad.net/bugs/1751291>* various network related fixes, eghttps://bugs.launchpad.net/bugs/1733266 <https://bugs.launchpad.net/bugs/1733266>https://bugs.launchpad.net/bugs/1764735 <https://bugs.launchpad.net/bugs/1764735>https://bugs.launchpad.net/bugs/1771120 <https://bugs.launchpad.net/bugs/1771120>## How can I get it?The best way to get your hands on this release of Juju is to install it as a snap package (see https://snapcraft.io/ <https://snapcraft.io/> for more info on snaps). sudo snap install juju --classic --betaOther packages are available for a variety of platforms. Please see the online documentation at https://jujucharms.com/docs/stable/reference-install <https://jujucharms.com/docs/stable/reference-install>. Those subscribed to a snap channel should be automatically upgraded. If you’re using the ppa/homebrew, you should see an upgrade available.## Feedback Appreciated!We encourage everyone to let us know how you're using Juju. Send us amessage on Twitter using #jujucharms, join us at #juju on freenode, and subscribe to the mailing list at j...@lists.ubuntu.com <j...@lists.ubuntu.com>.## More informationTo learn more about juju please visit https://jujucharms.com <https://jujucharms.com>.''*
-- Juju-dev mailing list Juju-dev@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju-dev
