A new release of Juju, 2.1-rc1, and Conjure-up, are here!
## What's new? [juju] Manual provisioning now supports CentOS machines. See https://github.com/juju/docs/issues/1647 for instructions on how to prepare a CentOS LXD container for manual provisioning. [juju] Beta 5 changed the way LXD certificate credentials are handled internally, which caused issues for some users connecting to a "localhost" controller from remote machines. If you need to add models to a LXD controller from a remote machine, you can now use juju autoload-credentials followed by juju add-credential localhost on the LXD host to generate a certificate credential, and then load that credential into the Juju client on the remote host. See https://github.com/juju/docs/issues/1636 for more details if this applies to you. [juju] Container networking refinements to explicitly specify which spaces to deploy applications to. The most visible changes apply to machines that have more than one network interface. Juju's network spaces now gives operators greater control over the spaces into which applications are deployed. When deploying an application to a target with multiple spaces, the operator must specify which to use. Ambiguous bindings will result in a provisioning failure. Juju creates bridges for containers when it knows the spaces the applications require, and the container's bridge only connects to the required network interfaces. Previously, Juju bridged all networks and placed the network card in promiscuous mode when the machine was provisioned. Bindings are supported per-endpoint, allowing operators to configure mysql so the 'admin' endpoint is accessed on a separate subnet from 'db'. Charms utilizing the existing "unit-get private-address" must be updated to use "network-get --primary-address <BINDING>". Operators may specify bindings when deploying a charm: juju deploy --bind "admin=admin-space db=internal-space" <charm> To specify everything in the same space: juju deploy --bind space <charm> Bundles may specify bindings with a bindings stanza: mysql: charm: "./xenial/percona-cluster" num_units: 1 bindings: access: internal-api shared-db: internal-api Bundles may place all bindings in the same space: mysql: charm: "./xenial/percona-cluster" num_units: 1 bindings: "": internal-api [conjure-up] Added several Big Data spells: conjure-up bigdata ## Bugs Addressed Check the milestones for a detailed breakdown of Juju and Conjure-Up bugs corrected. https://launchpad.net/juju/+milestone/2.1-rc1 https://github.com/conjure-up/conjure-up/milestone/14?closed=1 ## How do I get it? If you are running Ubuntu, you can get Juju from the juju devel ppa: sudo add-apt-repository ppa:juju/devel; sudo apt-get update sudo apt-get install juju Or install Juju from the snap store: snap install juju --beta --devmode Install conjure-up from the snap store: snap install conjure-up --classic --candidate If you are on Trusty, you'll need to run a few extra commands: sudo apt-get install snapd sudo groupadd lxd && sudo usermod -a -G lxd $USER sudo reboot Now you can install snaps, including conjure-up, as normal: snap install conjure-up --classic --candidate Windows, CentOS, and MacOS users can get a corresponding Juju installer at: https://launchpad.net/juju/+milestone/2.1-rc1 ## Feedback Appreciated! We encourage everyone to let us know how you're using Juju. Send us a message on Twitter using #jujucharms, join us at #juju on freenode, and subscribe to the mailing list at j...@lists.ubuntu.com. -- Curtis Hovey Canonical Cloud Development and Operations http://launchpad.net/~sinzui -- Juju-dev mailing list Juju-dev@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju-dev
