Juju 2.3.3 has been released
Juju 2.3.3 has arrived. This is primarily a bug fix release.
## Critical bugs fixed.
Among the bugs fixed three were considered critical.
1746265 juju-upgrade from 2.2.9 to 2.3.2 fails with state changing too
quickly
1747048 vsphere bootstrap: go panic comparing uncomparable type
map[string]interface {}
1745321 removed model can cause allmodelwatcher to die permanently
If you were affected by any of the bugs fixed in this release, your
feedback is appreciated. Please contact the juju team using the
communication channels specified in the feedback section.
## Get juju.
The easiest way to get juju is using the snap package.
snap install juju --classic
## 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 juju@lists.ubuntu.com.
## More information
To learn more about juju please visit https://jujucharms.com.
--
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/juju
Re: Beware 2.2.7 release
Hi all, 2.2.8 has been released (agent only) and is now available. Regards, Chris On Tue, Dec 19, 2017 at 10:31 AM, Tim Penhey wrote: > Hi folks, > > Last night we were alerted to a fundamental issue with the 2.2.7 agent > only release. > > There was a weird race condition that was only observable on larger > models which would cause a model to be non-responsive to controller > generated events, like config updates, actions, juju run etc. > > We have a fix available, and it has been tested on one of the broken > controllers and shown to fix the problem. > > Expect a 2.2.8 agent only release shortly to address this issue. > > Thanks > Tim > > -- > Juju-dev mailing list > juju-...@lists.ubuntu.com > Modify settings or unsubscribe at: https://lists.ubuntu.com/ > mailman/listinfo/juju-dev > -- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
Juju 2.3 beta3 is here!
A new development release of Juju is here, 2.3-beta3. This is primarily a bug fix release which addresses issues carried over from beta2. ## New and Improved * A new command "remove-saas", aliased to "remove-consumed-application", is added to remove a SAAS entry from a consuming model. * Support for the new Google Cloud asia-south1 (Mumbai) region. * Lots of papercut fixes for command help and other user facing text. ## Fixes For a list of all bugs fixed in this release, see https://launchpad.net/juju/+milestone/2.3-beta3 Some notable fixes include: * The issue of not a machine's public address not always being available when deploying a cross model scenario from a script has been addressed. Feedback welcome to ensure this has been fix in all scenarios. ## 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/ for more info on snaps). snap install juju --classic Other packages are available for a variety of platforms. Please see the online documentation at 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 a message on Twitter using #jujucharms, join us at #juju on freenode, and subscribe to the mailing list at juju@lists.ubuntu.com. ## More information To learn more about juju please visit https://jujucharms.com. -- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
Juju 2.3 beta2 is here!
A new development release of Juju is here, 2.3-beta2. ## New and Improved * Deploying bundles now supports --dry-run With --dry-run, no changes are made to the model, but what would be done is output. The new machine numbers and unit numbers take into account the current model. The --dry-run flag can also be used to apply changes made to a bundle since it had been deployed. * Deploying bundles can now target existing machines When deploying bundles, machines specified in the bundle are added to the model as new machines. In order to use the existing machines in the model rather than create new machines, the --use-existing-machines flag can be used. To specify a particular machine, the --bundle-machine flag can be used to specify a specific machine for a particular machine in the bundle. These flags can be combined with the --bundle-machine flag taking precidence. For example, if there was a bundle that specified machines 1, 2, and 3, and the model had machines 1, 2, 3 and 4, the following deployment of the bundle would use machines 1 and 2 in the model for machines 1 and 2 in the bundle and use machine 4 in the model for the bundle machine 3. juju deploy some-bundle --use-existing-machines --bundle-machine 3=4 * OpenStack Cinder storage provider now supports “volume-type” https://bugs.launchpad.net/juju/+bug/1719323 The “cinder” storage provider now supports a “volume-type” pool configuration. You can create a pool using “juju create-storage-pool”, specifying the name of an OpenStack Cinder volume type. * Cross model relations now supports nagios in its own [controller:]model The nagios and nrpe charms are updated to be cross model relations aware. This means they work in either a single model or cross model scenario. For now, the charms are available at cs:~wallyworld but will be published to the store soon. juju bootstrap aws juju switch controller juju deploy cs:~wallyworld/nagios juju expose nagios juju offer nagios:monitors juju switch default juju deploy ubuntu juju deploy cs:~wallyworld/nrpe juju add-relation ubuntu nrpe juju add-relation nrpe:monitors controller.nagios - get the public IP of nagios and load it in the browser - username is nagiosadmin - password can be found by this command on the nagios model: juju ssh nagios/0 sudo cat /var/lib/juju/nagios.passwd * open_port and close_port hook tools now support ICMP The open_port and close_port hook tools now support opening firewall access for ICMP. The syntax is: open_port icmp This was needed for the (new) nrpe charm when used in a cross model scenario, so that the remote nagios application could access the nrpe subordinate in another model. The necessary charm helpers change has not yet landed upstream - it is for now just contained in the cs:~wallyworld/nrpe charm. But the Juju support is there so charms can shell out to call open_port directly if needed, until charm helpers is updated. * Cross model relations now supports prometheus in its own [controller:]model The prometheus and telegraf charms are updated to be cross model aware. This means they work in either a single model or cross model scenario. For now, the charms are available at cs:~rharding but will be published to the store soon. juju bootstrap google bigbrother juju bootstrap aws monitorme juju switch bigbrother juju deploy cs:~rharding/prometheus-0 juju expose prometheus juju offer prometheus:target offerprom juju switch monitorme juju deploy ubuntu juju deploy cs:~rharding/telegraf-0 juju relate ubuntu:juju-info telegraf juju consume bigbrother:/admin/default.offerprom promed juju relate telegraf:prometheus-client promed:target juju switch bigbrother juju show-machine 0 - get the public IP of prometheus and load it in the browser :9090 - open the status->targets list and make sure you see the CMR with the public IP address of the telegraf unit in AWS * Cross model relations over private networks The algorithm used to select the ingress address to advertise across a cross model relation is tweaked to better support the case where both applications are on a private subnet. If the offered endpoint is bound to a space, select an ingress address in that space. If the offered endpoint is not bound to a space, attempt to select a public address on the machine, and fallback to a cloud local address if necessary. The deployer of the application being offered thus gets to decide how they want the offer to be accessed when they deploy the application. Not all scenarios are covered since they are not yet modelled, eg bind to a private subnet but access over a (public) shadow address. But what is supported should cover many of the use cases people encounter. * Autoconfiguration of FAN networking for EC2 and GCE providers When creating a model in a VPC environment on EC2 or on GCE FAN settings (model-config fan-config and container-networking-method) will be autoconfigured, and container networking will work out-of-the-box. * Para
We are pleased to announce the release of Juju 1.25.13
Hi all, Today we released Juju 1.25.13 which addressed some memory leak bugs. For a list of all bugs fixed in these release see: https://launchpad.net/juju-core/+milestone/1.25.13 Regards, Chris -- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
Juju 2.2-rc2 has been released
# Juju 2.2-rc2 Release Notes We are delighted to announce the release of Juju and conjure-up 2.2-rc2! In this release, Juju greatly improves memory and storage consumption, works on KVM containers, and improves network modelling. conjure-up now supports Juju as a Service (JAAS), provides a MacOS client, and adds support for repeatable spell deployments. The best way to get your hands on this release of Juju and conjure-up is to install them via snap packages (see https://snapcraft.io/ for more info on snaps). snap install juju --classic --candidate snap install conjure-up --classic --candidate Other packages are available for a variety of platforms. Please see the online documentation at https://jujucharms.com/docs/devel/reference-releases#development Please note that if you are upgrading an existing controller, please make sure there is at least 6G of free disk space. The upgrade step for the logs can take a while, in the vicinity of 10 or more minutes if the current logs collection is at its maximum size. Since 2.2-rc1 ## New and Improved -- Better support credential management in the Azure provider * support autoload-credentials and juju add-credential in the azure provider when Azure CLI is installed. (this removes the requirement that the user discover their subscription ID before creating credentials) Rate limit login and connection requests to the controller(s) on busy systems. ## Fixes -- Fix issue where status history logs were not pruned: https://bugs.launchpad.net/juju/+bug/1696491 -- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
A new release of Juju, 2.2-beta2, and conjure-up, are here!
A new release of Juju, 2.2-beta2, and conjure-up, are here! ## What's new in 2.2-beta2 - [conjure-up] A new spell which deploys Landscape On-Premises 17.03 - [conjure-up] Support for channels ### conjure-up channel support conjure-up can now deploy from release channels, for example, if canonical-kubernetes is pushed into the charmstore channel ‘beta’, conjure-up can make use of that bundle with the following: $ conjure-up canonical-kubernetes --channel beta ## Resolved Issues Check the milestones for a detailed breakdown of Juju and conjure-up bugs corrected. https://github.com/conjure-up/conjure-up/milestone/19?closed=1 https://launchpad.net/juju/+milestone/2.2-beta2 ## How do I get it? If you are running Ubuntu, you can get Juju from the juju stable 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 --classic --beta Install conjure-up from the snap store: snap install conjure-up --classic --beta 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 --beta macOS users can install conjure-up with brew: brew install conjure-up --devel Windows, CentOS, and MacOS users can get a corresponding Juju installer at: https://launchpad.net/juju/+milestone/2.2-beta2 ## 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 juju@lists.ubuntu.com. ## More information To learn more about these great technologies please visit https://jujucharms.com and http://conjure-up.io. -- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
A new supported stable release of Juju, 1.25.11, is here!
A new supported stable release of Juju, 1.25.11, is here! ## Resolved Issues * SetAPIHostPorts runs afoul of "state changing too quickly" https://bugs.launchpad.net/bugs/1613855 ## How do I get it? If you are running Ubuntu, you can get it from the juju 1.25 ppa: sudo add-apt-repository ppa:juju/1.25 sudo apt-get update; sudo apt-get install juju-core Windows, Centos, and MacOS users can get a corresponding installer at: https://launchpad.net/juju-core/+milestone/1.25.11 ## Feedback Appreciated! We encourage everyone to subscribe the mailing list at juju@lists.ubuntu.com and join us on #juju on freenode. We would love to hear your feedback and usage of juju. -- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
