A new release of Juju, 2.2-beta1 and conjure-up are here!
A new release of Juju, 2.2-beta1, and conjure-up, are here! ## What's new in 2.2-beta1 - juju login updates - [conjure-up] Integrated JAAS support - [conjure-up] Steps now support handling actions that require sudo (ie sudo snap install kubectl --classic --edge) - [conjure-up] macOS port (waiting on merge https://github.com/Homebrew/homebrew-core/pull/11488) - [conjure-up] Lots of step processing polishes ### juju login updates Juju login command now accepts the name or hostname of a public controller as a parameter. juju login jaas This would add the jaas public controller to the list of the controllers you can use, it will also get cached in the controllers.yaml. Public controllers usually use external identity providers. JAAS uses Ubuntu SSO as an external provider, so in order to use this controller, you have to register at Ubuntu SSO. In order to get access to the JAAS public controller, please register through jujucharms.com or using this URL: https://jujucharms.com/login The previous version of the command accepted the user name as a parameter. In order to login as a local user, you can specify a user name as the argument to the -u flag. juju login -u bob Note that this release includes only the initial implementation of the juju login command changes. Polishing and improved UX will come with following releases. ## 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-beta1 ## 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-beta1 ## 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. ## More information To learn more about these great technologies please visit https://jujucharms.com and http://conjure-up.io. -- 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
Juju 2.2-alpha and conjure-up, are here!
A new release of Juju, 2.2-alpha1, and conjure-up, are here! ## What's new in 2.2-alpha1 - juju login ### juju login Juju login command now accepts the name of the public controller as a parameter. juju login jaas This would add the jaas public controller to the list of the controllers you can use, it will also get cached in the controllers.yaml. Public controllers use external identity providers. JAAS uses Ubuntu SSO as an external provider, so in order to use this controller, you have to register at Ubuntu SSO. In order to get access to the JAAS public controller, please register through jujucharms.com or using this URL https://jujucharms.com/login The previous version of the command accepted the user name as a parameter. In order to login as a local user, pass the -u option. juju login -u bob Note that this release includes only the initial implementation of the juju login command changes. Polishing and improved UX will come with following releases. ## Resolved Issues Check the milestones for a detailed breakdown of Juju and conjure-up bugs corrected. https://github.com/conjure-up/conjure-up/milestone/20?closed=1 https://launchpad.net/juju/+milestone/2.2-alpha1 ## 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 --edge 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 --edge Windows, CentOS, and MacOS users can get a corresponding Juju installer at: https://launchpad.net/juju/+milestone/2.2-alpha1 ## 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. ## More information To learn more about these great technologies please visit https://jujucharms.com and http://conjure-up.io. -- 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
Juju 2.1.2 and conjure-up, are here!
A new release of Juju, 2.1.2, and conjure-up, are here! ## What's new in 2.1.2 - [conjure-up] headless installs now support cloud regions - [conjure-up] improved error handling - [juju] Handle 'Node with this Hostname already exists' errors when provisioning containers. LP:#1670873 - [juju] Fix 'interface bindings cannot have empty names' LP:#1671489 - [juju] Fix 'upgrade-charm broken after using default binding' LP:#1671428 ## Resolved Issues Check the milestones for a detailed breakdown of Juju and conjure-up bugs corrected. https://github.com/conjure-up/conjure-up/milestone/20?closed=1 https://launchpad.net/juju/+milestone/2.1.2 ## 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/stable; sudo apt-get update sudo apt-get install juju Or install Juju from the snap store: snap install juju --classic Install conjure-up from the snap store: snap install conjure-up --classic 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 Windows, CentOS, and MacOS users can get a corresponding Juju installer at: https://launchpad.net/juju/+milestone/2.1.2 ## 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. ## More information To learn more about these great technologies please visit https://jujucharms.com and http://conjure-up.io. -- 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
Juju, 2.1.1 and conjure-up, are here!
A new release of Juju, 2.1.1, and conjure-up, are here! ## What's new in 2.1.1 - Networking improvements - [conjure-up] Spells support side-loading bundles. This helps spells authors who are writing spells for particular software but want to offer variations. For example, there are OpenStack bundles that support both KVM and LXD, or Telemetry additions. Side-loading will help with spells that need to provide those various bundle configurations. - [conjure-up] More LXD improvements in addition to support for the recently released LXD 2.10. ### Networking improvements - containers now respect static routes from MAAS. The static routes defined for the subnets that the containers are in should should be set for the containers as well. - 'lxdbr0' subnet selection has changed from a simple incremental search to randomized selection across 10.0.X. It also now properly handles when an active subnet spans more than just a /24. - better handling of http_proxy and no_proxy when interacting with LXD - errors while trying to set up networking for containers are properly reported as provisioning errors, instead of falling back to 'lxdbr0'. This mostly impacts MAAS deployments where they would end up with containers that were not addressable, and the actual failure was buried in log files. ## Resolved Issues Check the milestones for a detailed breakdown of Juju and conjure-up bugs corrected. https://github.com/conjure-up/conjure-up/milestone/18?closed=1 https://launchpad.net/juju/+milestone/2.1.1 ## 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/stable; sudo apt-get update sudo apt-get install juju Or install Juju from the snap store: snap install juju --classic Install conjure-up from the snap store: snap install conjure-up --classic 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 Windows, CentOS, and MacOS users can get a corresponding Juju installer at: https://launchpad.net/juju/+milestone/2.1.1 ## 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. ## More information To learn more about these great technologies please visit https://jujucharms.com and http://conjure-up.io. -- 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
Juju 2.1.0, and Conjure-up, are here!
-candidate Windows, CentOS, and MacOS users can get a corresponding Juju installer at: https://launchpad.net/juju/+milestone/2.1.0 ## 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
A new release of Juju, 2.1-rc2, and Conjure-up, are here!
ll 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-rc2 ## 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
Juju 2.1-rc1 and Conjure-Up are here!
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 ". Operators may specify bindings when deploying a charm: juju deploy --bind "admin=admin-space db=internal-space" To specify everything in the same space: juju deploy --bind space 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
Juju stable 2.0.3 is here!
A new stable release of Juju, 2.0.3, is here! ## What's new? This releases addresses stability and performance issues. ## How do I get it? If you are running Ubuntu, you can get it from the juju stable ppa: sudo add-apt-repository ppa:juju/stable sudo apt-get update; sudo apt-get install juju Windows, Centos, and MacOS users can get a corresponding installer at: https://launchpad.net/juju/+milestone/2.0.3 ## Feedback Appreciated! We encourage everyone to subscribe the mailing list at j...@lists.ubuntu.com and join us on #juju on freenode. We would love to hear your feedback and usage of juju. ## Resolved issues * Improvements to Juju's CPU and memory performance, and overall responsiveness. Lp 1645729, Lp 1635311, Lp 1651291, Lp 1660087, Lp 1632362, Lp 1639577, Lp 1645917 * Required packages are upgraded with Juju agent upgrades. Lp 1637079 * Better cleanup of resources in OpenStack and manual providers. Lp 1642295, Lp 1625624 * Commands in interactive ssh from windows clients are properly passed. Lp 1468752 See https://launchpad.net/juju/+milestone/2.0.3 for more details. -- 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
A new development release of Juju, 2.1-beta3, is here!
A new development release of Juju, 2.1-beta3, is here! ## What's new? * Deployments to LXD containers on Xenial use the more performant directory backend https://bugs.launchpad.net/juju/+bug/1648513 * Constraints placed on KVM containers in bundles are honoured * Juju SSH improvements for the Windows platform * Memory usage improvements * Other Bug fixes https://launchpad.net/juju/+milestone/2.1-beta3 ## Known Issues: * Model Migrations does not migrate back to the original controller ## How do I get it? If you are running Ubuntu, you can get it from the juju devel ppa: sudo add-apt-repository ppa:juju/devel sudo apt-get update; sudo apt-get install juju-2.0 Or install it from the snap store snap install juju --beta --devmode Windows, Centos, and MacOS users can get a corresponding installer at: https://launchpad.net/juju/+milestone/2.1-beta3 ## Feedback Appreciated! We encourage everyone to subscribe the mailing list at j...@lists.ubuntu.com and join us on #juju on freenode. We would love to hear your feedback and usage of juju. -- 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
Re: Representative tests failing
On Wed, Dec 14, 2016 at 3:29 PM, Nate Finch <nate.fi...@canonical.com> wrote: > Seems like there's a likely out of disk space problem with the LXD and > windows machines that run representative tests. For example: > > http://juju-ci.vapour.ws/job/github-check-merge-juju/441/ > http://juju-ci.vapour.ws/job/github-check-merge-juju/442/ > > Sounds like this happens often enough to be a problem. It is a problem but has not been a priority to fix :( https://bugs.launchpad.net/juju-ci-tools/+bug/1645744 The windows machine has only been problematic on a monthly basis. -- 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
Juju 1.25.8 is now available
A new supported stable release of Juju, 1.25.8, is here! ## Notable Changes * Added support for new AWS regions: ap-south-1 and us-east-2 * Fixed issue allowing you to re-provision a machine with manual provider https://bugs.launchpad.net/juju/+bug/1418139 * Improved charm garbage collection https://bugs.launchpad.net/juju-core/+bug/1626304 * HA Agents connectivity fixes; https://bugs.launchpad.net/juju/+bug/1510651 https://bugs.launchpad.net/juju/+bug/1597830 * Corrected Backup and Restore failures; https://bugs.launchpad.net/juju/+bug/1457575 https://bugs.launchpad.net/juju/+bug/1544796 * Support for MacOS Sierra https://bugs.launchpad.net/juju/+bug/1638560 ## How do I get it? If you are running Ubuntu, you can get it from the juju proposed 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.8 ## Feedback Appreciated! We encourage everyone to subscribe the mailing list at j...@lists.ubuntu.com and join us on #juju on freenode. We would love to hear your feedback and usage of juju. -- 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
Juju 2.1-beta1 is here!
A new development release of Juju, 2.1-beta1, is here! ## What's new? * Controller instance size to have bigger default out of the box https://bugs.launchpad.net/bugs/1638165 * Interactive add cloud * Updates to "juju models" output * Vsphere fixes * Bug fixes https://launchpad.net/juju/+milestone/2.1-beta1 ## How do I get it? If you are running Ubuntu, you can get it from the juju devel ppa: sudo add-apt-repository ppa:juju/devel sudo apt-get update; sudo apt-get install juju-2.0 Or install it from the snap store snap install juju --beta --devmode Windows, Centos, and MacOS users can get a corresponding installer at: https://launchpad.net/juju/+milestone/2.1-beta1 ## Feedback Appreciated! We encourage everyone to subscribe the mailing list at j...@lists.ubuntu.com and join us on #juju on freenode. We would love to hear your feedback and usage of juju. -- 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
Re: Juju 2.0-rc3 is here!
Hi Matt, You, and several of us, are victims of '"upload-tools strikes back" cannot upgrade with streams' https://bugs.launchpad.net/juju/+bug/1631529 On Fri, Oct 7, 2016 at 1:51 PM, Matt Rae <matt@canonical.com> wrote: > Hi, I'm testing an upgrade between juju 2.0 rc2 and rc3. > > Should 'juju upgrade-juju -m default' upgrade to rc3? > > So far I'm seeing 'no upgrades available' > > $ juju model-config agent-version > 2.0-rc2 > $ juju --version > 2.0-rc3-xenial-amd64 > $ juju upgrade-juju > no upgrades available > $ juju upgrade-juju --agent-version 2.0-rc3 > ERROR no matching tools available Do you see this: $ juju model-config -m controller agent-stream released ^ No, the juju client selected devel streams without telling the controller WORK AROUND Tell the juju controller to use devel streams. Eg, to upgrade my own deployment, I I set the streams to devel, then upgrade the controller than the hosted model. $ juju model-config -m controller agent-stream=devel $ juju upgrade-juju -m controller started upgrade to 2.0-rc3 $ juju upgrade-juju -m default started upgrade to 2.0-rc3 When 2.0.0 is released, switch the streams to released. $ juju model-config -m controller agent-stream=released Then upgrade as normal. -- 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
Re: Juju 2.0-rc3 is here!
> A new development release of Juju, 2.0-rc3, is here! ... > ## How do I get it? You can now install the Juju 2.0-rc3 snap. snap install juju --beta --devmode ^ This is the 2.0-rc3. Juju requires requires confinement: devmode, which restricts our RCs and stables to the beta channel :( -- 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
Re: Juju 2.0-rc1 is here!
On Wed, Sep 21, 2016 at 2:07 AM, Andrew Wilkins <andrew.wilk...@canonical.com> wrote: > In case anyone jumps right on this, please note that > https://streams.canonical.com/juju/public-clouds.syaml isn't yet updated. It > will be updated soon, but in the mean time, if you want to try out the azure > interactive add-credential, make sure you: > - delete ~/.local/share/juju/public-clouds.yaml (if it exists) > - *don't* run "juju update-clouds" until that file is updated > Then Juju will use the cloud definitions built into the client. https://streams.canonical.com/juju/public-clouds.syaml is updated. If you are using Juju 2.0-rc1, you are all set. Testers of older Juju 2,0 betas need to upgrade to Juju 2.0-rc1 to experience the new Azure interactive setup. Run "juju update-clouds" after upgrading to enable the new feature. -- 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
Juju 2.0-rc1 is here!
A new development release of Juju, 2.0-rc1, is here! ## What's New in RC1 * The Juju client now works on any Linux flavour. When bootstrapping with local tools, it's now possible to create a controller of any supported Linux series regardless of the Linux flavour the client is running on. * Juju resolved command retries failed hooks by default: juju resolved // marks unit errors resolved and retries failed hooks juju resolved --no-retry //marks unit errors resolved w/o retrying hooks * MAAS 2.0 Juju provider has been updated to use MAAS API 2.0's owner data for instance tagging. * Networking fixes for containers in MAAS 2.0 when the parent device is unconfigured. (#1566791) * Azure provider performance has been enhanced, utilising Azure Resource Manager templates, and improved parallelisation. * Azure provider now supports an "interactive" auth-type, making it much easier to set up credentials for bootstrapping. The "userpass" auth-type has been deprecated, and replaced with "service-principal-secret". ## How do I get it? If you are running Ubuntu, you can get it from the juju devel ppa: sudo add-apt-repository ppa:juju/devel sudo apt-get update; sudo apt-get install juju-2.0 Or install it from the snap store snap install juju --beta --devmode Windows, Centos, and OS X users can get a corresponding installer at: https://launchpad.net/juju/+milestone/2.0-rc1 ## Feedback Appreciated! We encourage everyone to subscribe the mailing list at j...@lists.ubuntu.com and join us on #juju on freenode. We would love to hear your feedback and usage of juju. ## Anything else? You can read more information about what's in this release by viewing the release notes here: https://jujucharms.com/docs/devel/temp-release-notes -- 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
Juju, 2.0-beta18 is here!
A new development release of Juju, 2.0-beta18, is here! ## What's new? * juju model-defaults command(s) have been collapsed to one command * juju model-config command(s) have been collapsed to one command * juju list-controllers displays model count, machine count, and HA status * juju show-controllers contains more detailed information about controller machines (instance id, HA status) * juju list-models displays machine count and core count * "juju login" now supports external users. If you have identity-url configured, you must now explicitly specify a user name on the command line to log in as a local user * When a login expires for local users, you will now be automatically prompted, rather than getting an error back telling you to run "juju login" * Macaroons for local users are now stored in the cookie jar, as with external users. There is a known issue with logout (#1621375) which will be addressed in beta19. ## How do I get it? If you are running Ubuntu, you can get it from the Juju devel PPA: sudo add-apt-repository ppa:juju/devel sudo apt-get update; sudo apt-get install juju-2.0 Or install it from the snap store snap install juju --beta --devmode Windows, Centos, and OS X users can get a corresponding installer at: https://launchpad.net/juju/+milestone/2.0-beta18 ## Feedback Appreciated! We encourage everyone to subscribe the mailing list at j...@lists.ubuntu.com and join us on #juju on freenode. We would love to hear your feedback and usage of juju. ## Anything else? You can read more information about what's in this release by viewing the release notes here: https://jujucharms.com/docs/devel/temp-release-notes -- 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
A new development release of Juju, 2.0-beta14, is here!
A new development release of Juju, 2.0-beta14, is here! ## What's new? * New model config capability allows managing custom configuration on models much easier. See “Shared Model Config” in the release notes. * First baby step to an interactive bootstrap experience. Look for more on this in future betas. * Ensure that openstack clouds that are configured to support Multi-hypervisors. Juju can deploy workloads to the desired hypervisor. Lp 1600054 * Juju will detect LXD default profile's bridge name and use it. Lp 1575676 * Added support for the remove-user command. Lp 1570096 * Improve the scalability when destroying large models. Lp 1579010 * Print a more user friendly error message when an api request is made and a model uuid is not found Lp 1602034 * Updated fix for 'duplicate key error' Lp 1593828, Lp 1604644 ## How do I get it? If you are running Ubuntu, you can get it from the juju devel ppa: sudo apt-add-repository ppa:juju/devel sudo apt-get update; sudo apt-get install juju-2.0 Windows, Centos, and OS X users can get a corresponding installer at: https://launchpad.net/juju-core/+milestone/2.0-beta14 ## Feedback Appreciated! We encourage everyone to subscribe the mailing list at j...@lists.ubuntu.com and join us on #juju on freenode. We would love to hear your feedback and usage of juju. ## Anything else? You can read more information about what's in this release by viewing the release notes here: https://jujucharms.com/docs/devel/temp-release-notes -- 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
top-issues preventing Juju from passing
The top issues page is contaminated with results from retests http://reports.vapour.ws/releases/top-issues (https://bugs.launchpad.net/juju-reports/+bug/1608971) Since http://reports.vapour.ws/releases/4200 we are seeing a rise in failures These are the issues seen in recent days that need fixing to see a revision bless, NEW: Deployer: KeyError: 'uuid' connecting to environment https://bugs.launchpad.net/juju-core/+bug/1608952 ^ Juju or deployer needs to change Race in github.com/juju/juju/cmd/modelcmd https://bugs.launchpad.net/juju-core/+bug/1609041 ^ There are two immediate suspect commits, but the race appears to involve older commits. OUTSTANDING Charms utilizing storage fail on LXD https://bugs.launchpad.net/juju-core/+bug/1604474 ^ Has been assigned for weeks, but no sign of progress. Restore from backup continues to fail https://bugs.launchpad.net/juju-core/+bug/1606308 https://bugs.launchpad.net/juju-core/+bug/1604959 https://bugs.launchpad.net/juju-core/+bug/1605653 ^ There are many issues seen in testing restore. Mongo setup is the dominate theme of the faillures Juju 2.0-beta12 userdata execution fails on Windows https://bugs.launchpad.net/juju-core/+bug/1604474 ^ This bug has a fix committed, but the test that deploys windows charms on azure still fails. Testing with a juju from the first week of July passes. We might decide this bug is fixed, but separate one of the duplicate bugs to track a new issue about workloads not deploying. Race in github.com/juju/juju/featuretests https://launchpad.net/bugs/1604817 INTERMITTENT These issue happen often enough to be be a cause of failure. MachineSuite.TestCertificateUpdateWorkerUpdatesCertificate timeout while waiting for certificate to be updated https://bugs.launchpad.net/juju-core/+bug/1466514 MachinerStateSuite.TestSetsStatusWhenDying timeout waiting for status to change https://bugs.launchpad.net/juju-core/+bug/1607858 TestWaitSSHRefreshAddresses failed to capture address on windows https://bugs.launchpad.net/juju-core/+bug/1604961 RunnerSuite.TestOneWorkerStartWhenStopping timed out https://bugs.launchpad.net/juju-core/+bug/1583771 ^ A commit was made to fix this, but the test still fails ActionSuite.TestUnitWatchActionNotifications unexpected change https://bugs.launchpad.net/juju-core/+bug/1589641 MachineSuite.TearDownTest no reachable servers https://launchpad.net/bugs/1605767 TestAgentConnectionDelaysShutdownWithPing https://bugs.launchpad.net/juju-core/+bug/1455627 clientSuite.SetUpTest mongo could not create index https://launchpad.net/bugs/1608938 BootstrapSuite.TestRunTests is false https://launchpad.net/bugs/1596559 Race in github.com/juju/juju/apiserver/tools_test https://bugs.launchpad.net/juju-core/+bug/1608533 testsuite.TestWatchUnitAssignment got Next https://bugs.launchpad.net/juju-core/+bug/1606302 -- 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
Critical bugs need fixing
As seen at https://bugs.launchpad.net/juju-core/+bugs?field.importance=Critical We still have 14 Critical bugs, 7 have not been started. The last two still need assignee. I'll call out" munna/juju2 is too slow to deploy windows images" https://bugs.launchpad.net/juju-core/+bug/1605777 Even though the munna mass 1.9 is very slow. juju 1.25 consistently passes, Juju 2 has not passed in weeks. The test results show Juju 2 cannot deploy windows workloads. -- 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
Juju CI is updated to test the autoload-credentials changes
We saw the autoload-credential test failures this morning. The test is strongly coupled to the prompt text. We updated the test to support the new text, then re-ran the last failure to show there is no issue in master https://bugs.launchpad.net/juju-ci-tools/+bug/1606242 -- 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
Juju 2.0-beta13 is here!
A new development release of Juju, 2.0-beta13, is here! ## What's new? * Juju publish command has been removed. Please use "charm push" and "charm publish" as replacements. * Virt-type is now properly respected. Pass it as a constraint --constraints virt-type=XXX. * Fix for Mongo 'duplicate key error' applied to both client and agents. ## How do I get it? If you are running Ubuntu, you can get it from the Juju devel PPA: sudo apt-add-repository ppa/devel sudo apt-get update; sudo apt-get install juju-2.0 Windows, Centos, and OS X users can get a corresponding installer at: https://launchpad.net/juju-core/+milestone/2.0-beta13 ## Feedback Appreciated! We encourage everyone to subscribe the mailing list at j...@lists.ubuntu.com and join us on #juju on freenode. We would love to hear your feedback and usage of Juju. ## Anything else? You can read more information about what's in this release by viewing the release notes here: https://jujucharms.com/docs/devel/temp-release-notes -- 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
New functional-ha-recovery-maas-1-9 is non-voting
We added a test specific to xenial maas 1.9 to help engineers investigate HA issues in Maas 1.9: functional-ha-recovery-maas-1-9. This test is current'y using xenial. There is also a test for trusty that QA staff can run on demand to gather logs. -- 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
functional-charm-resource-charmstore now votes
The functional-charm-resource-charmstore job that tests user permission in juju via grant and revoke commands now votes. -- 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
functional-unregister test now votes
The test of the unregister command is now voting. -- 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
Juju 2.0-beta10 is here!
A new development release of Juju, 2.0-beta10 is here! ## What's new? * Improved handling of LACP bonds * Continued usability enhancements * Users can now use `juju relate` to add a relation between applications * Additional `juju status` enhancements * Bundles requesting legacy ‘lxc’ type will automatically get new ‘lxd’ containers ## How do I get it? If you are running ubuntu, you can get it from the juju devel ppa: sudo apt-add-repository ppa:juju/devel sudo apt update; sudo apt install juju Windows, Centos, and OS X users can get a corresponding installer at: https://launchpad.net/juju-core/+milestone/2.0-beta10 ## Feedback Appreciated! We encourage everyone to subscribe to the mailing list at j...@lists.ubuntu.com and join us at #juju on freenode. We would love to hear your feedback and about your usage of juju. ## Known issues * Juju GUI is not yet compatible with the API changes in 2.0-beta10 * Juju deployer, and any tool using python-jujuclient are not yet compatible with the API changes in recent betas. ## Anything else? You can read more information about what's in this release by viewing the release notes here: https://jujucharms.com/docs/devel/temp-release-notes -- 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
Juju devel 2.0-beta8 is released
# Juju 2.0-beta8
A new development release of Juju, juju 2.0-beta8, is now available.
This release replaces version 2.0-beta7.
## Getting Juju
Juju 2.0-beta8 is available for Yakkety and backported to earlier
series in the following PPA:
https://launchpad.net/~juju/+archive/devel
Windows, Centos, and OS X users will find installers at:
https://launchpad.net/juju-core/+milestone/2.0-beta8
Upgrading 1.x environments to 2.0-beta8 is not yet supported. Once 2.x is
proven we will provide an upgrade path from 1.25
## The complete release notes available on the Web
The release notes for Juju 2.0 beta7 are very long. They are too large
to post to a list. You can find them at
https://jujucharms.com/docs/devel/temp-release-notes
## What's New in Beta8
* List-controllers now lists cloud type and region
* New command to remove clouds.
Usage: juju remove-cloud
* MAAS and LXD machines and hostnames now use short names
* clouds.yaml now supports config options
* Controller model name changed from "admin" to "controller"
## Resolved issues
* Destroying the current model should clear the current-model
Lp 1505504
* "invalid entity name or password" error with valid credentials.
Lp 1514874
* Lxd containers fail to upgrade because the bridge config changes
to a different ip address
Lp 1569361
* List-controllers and list-models doesn't list cloud type
Lp 1572741
* Juju2 usability: many options have to be specified for every
bootstrap
Lp 1576750
* Cached local charms should be deleted when their service is
removed
Lp 1580418
* Cannot restore-backup of controller model
Lp 1585851
* Provider/lxd: instance names are overly long
Lp 1586880
* There is no command for removing clouds
Lp 1586891
* Juju does not extract system ssh fingerprints
Lp 892552
* {image,tools}-metadata-url not usable w/ ec2 provider
Lp 1287949
* Containers registered with maas use wrong name
Lp 1513165
* Workers restart endlessly
Lp 1522544
* Juju deploy ignores model default-series
Lp 1540900
* Failure when deploying on lxd models and model name contains space
characters
Lp 1568944
* Container networking lxd 'invalid parent device'
Lp 1571053
* Kill-controller is stuck, lots of "lease manager stopped" errors
Lp 1573136
* "juju kill-controller" removes controllers.yaml entry even if
destroying fails
Lp 1576120
* Resource-get hangs when trying to deploy a charm with resource
from the store
Lp 1577415
* Rename 'admin' model to 'controller'
Lp 1581885
* List-models first column should be renamed to model
Lp 1581886
* Juju-upgrade-mondo typo
Lp 1582620
* Help text for juju remove-machine needs improving
Lp 1568122
* Help text for juju add-model needs improving
Lp 1568854
* Current controller not cleared on destroy
Lp 1576528
* Juju switch to non-existent controller gives wrong error
Lp 1577609
* Juju 2 help commands for constraints or placement return error
unknown command
Lp 1580946
Finally
We encourage everyone to subscribe the mailing list at
j...@lists.ubuntu.com, or join us on #juju on freenode.
--
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
Re: Unable to add machine that uses public/private key based authentication
On Wed, May 25, 2016 at 5:11 PM, Cheryl Jennings <cheryl.jenni...@canonical.com> wrote: > Hi Phani, > > Is the key used for the machine known to juju? You can view the ssh keys > with `juju authorized-keys list` for juju 1.x, and `juju list-ssh-keys` for > juju 2.0. > > If it's not there, you can use the following commands to add the key and > juju will try to use it when connecting to the machine: > juju 1.x: `juju authorized-keys add` > juju 2.0: `juju add-ssh-key` > > Let me know if this works for you. > Thanks! > -Cheryl > > On Sat, May 21, 2016 at 5:18 AM, phani shankar <phanishanka...@gmail.com> > wrote: >> >> Hi, >> >> I am trying to use add-machine command to add a machine to juju >> environment. The machine being added uses public/private key authentication. >> I am facing following error. >> >> juju add-machine ssh:ubuntu@10.115.0.2 >> ERROR subprocess encountered error code 255 (Permission denied >> (publickey).) >> >> >> This works fine when I use the command to add a machine which does >> password based authentication. I understand that it is due to not passing >> the correct key credentials. But I am not sure how I can pass necessary >> credentials. Please advise. Does "ssh ubuntu@10.115.0.2" work This command is using your localhost to do the initial connection. The error can be from your localhost, not from the state-server/controller. Once your *client* juju has entered the machine it checks that jujud is not installed, the machine can connection to the state-server/controller over the private address, and there is an ubuntu user. Your juju client will provision the machine. Once complete, the machine will talk to the state-server/controller normally. -- 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
Re: go test github.com/juju/juju/state takes > 10 minutes to run
On Tue, May 17, 2016 at 2:14 AM, David Cheney <david.che...@canonical.com> wrote: > My environment has not changed since 14.04, so I'm probably not > running mongo 3.2. > > On Tue, May 17, 2016 at 4:13 PM, Cheryl Jennings > <cheryl.jenni...@canonical.com> wrote: >> Are you using mongo 3.2? (see bug >> https://bugs.launchpad.net/juju-core/+bug/1573294) >> >> On Mon, May 16, 2016 at 9:52 PM, David Cheney <david.che...@canonical.com> >> wrote: >>> >>> Testing this package takes 16 minutes on my machine*; it sure didn't >>> use to take this long. >>> >>> What happened ? >>> >>> * yes, you have to raise the _10 minute_ timeout to make this test run. I reported https://bugs.launchpad.net/juju-core/+bug/1582731 . This issue is new in the last week. -- 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
Juju devel 2.0-beta7 is released
ength too large" Lp 1543283 * Add maas 2.0 support in juju 2.0 Lp 1564577 * Payload commands don't work Lp 1567518 * Multiple interfaces lead to stalled charm download over wrong api endpoint Lp 1574607 * Azure multi model dns failure Lp 1576376 * Unblock panic: invalid memory address or nil pointer dereference Lp 1578373 * Cannot deploy windows nano Lp 1579127 * Help text for juju list-users needs improving Lp 1557143 * Lxd, maas and manual do not make sense in list-clouds Lp 1564054 * Juju help status missing controller syntax Lp 1572746 * Add-cloud method not documented by "juju help" Lp 1575332 * Juju switch returns confusing error message Lp 1575760 Finally We encourage everyone to subscribe the mailing list at j...@lists.ubuntu.com, or join us on #juju on freenode. -- 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
juju devel 2.0-beta4 is released
ds needs improving Lp 1560667 * Update-clouds message improvement when fully up to date Lp 1563843 * Region names should be case-insensitive but displayed as lowercase Lp 1563845 * Help text for juju set-model-config needs improving Lp 1563923 * Help text for juju get-model-config needs improving Lp 1563924 * Help text for juju get-model-constraints needs improving Lp 1563927 * Help text for juju set-model-constraints needs improving Lp 1563928 * Help text for juju unset-model-config needs improving Lp 1563938 * Help text for juju update-clouds needs improving Lp 1563958 * All: mutex's copied by value Lp 1563628 Finally We encourage everyone to subscribe the mailing list at j...@lists.ubuntu.com, or join us on #juju on freenode. -- 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
The next branch is now merged into master
The next branch is now obsolete. It is merged into master. The master branch will get a version bump shortly and CI will resume testing. -- 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
Juju stable 1.25.5 is released
# juju-core 1.25.5 A stable release of Juju, juju-core 1.25.5, is now available. This release replaces version 1.25.3 ## Getting Juju juju-core 1.25.5 is available for Xenial and backported to earlier series in the following PPA: https://launchpad.net/~juju/+archive/stable Windows, Centos, and OS X users will find installers at: https://launchpad.net/juju-core/+milestone/1.25.5 ## Notable Changes This releases addresses stability and performance issues. ## Resolved issues * Jujud offers poodle vulnerable sslv3 on 17070 Lp 1536269 * Leadership dependency failures in ci deploy tests Lp 1539656 * Upgrade 1.24.7 -> 1.25.3 fails Lp 1546100 * Destroyed leader, new leader not elected. Lp 1511659 * New ec2 korea region Lp 1530957 * Maas bridge script handles vlan nics incorrectly Lp 1532167 * 1.25.0: bootstrap failure - warning discarding api open error: eof Lp 1538303 * Bootstrap node does not use the proxy to fetch tools from streams.c.c Lp 1515289 * Payload/persistence intermittent failure Lp 1519061 * 1.25.3 can't bootstrap xenial environments Lp 1550306 * Enable daily image stream in juju local provider Lp 1554073 * Juju's maas bridge script is echoed to the console by cloud-init during bootstrap Lp 1536587 * Cookies file locked for too long Lp 1534643 * 1.25.4: units attempt to go through the proxy to download charm from state server Lp 1556207 * Xenial juju 1.25.3 unable to deploy to lxc containers Lp 1557345 * Provider/maas bridge script is not idempotent Lp 1553915 * Unable to bootstrap lxd provider on s390x Lp 1554675 * Gce invalid volume id destroying environment Lp 1556293 * Juju_availability_zone not set in maas Lp 1559099 * Handle multi-series charms in 1.25 Lp 1563607 * Apt-mirror is not used in containers with maas provider Lp 1560391 * Proxy updater fails with "permission denied" Lp 1564694 * Can-upgrade-to suggests a downgrade Lp 1319890 Finally We encourage everyone to subscribe the mailing list at j...@lists.ubuntu.com, or join us on #juju on freenode. -- 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
Thunderbirds are Go 1.6
Ladies and Gentlemen, We build with Go 1.6 everywhere. Take a moment to consider the implications, because that means we do not use Go 1.2, 1.3, or 1.5. Juju 1.x and 2.x for Windows, OS X, and Linux (precise, trusty, wily, xenial, and centos7) are built with Go 1.6. There was concern about how to support precise if the code grew 1.2 incompatibilities. Michael Hudson-Doyle's fabulous package was trivial to backport to precise. We don't need to create a new process to support precise. The golang-1.6 packages was also easy to copy to wily. since the Go 1.5 unit tests are less reliable than the Go 1.6 unit tests, the hour spent setting up wily to build with golang-1.6 will pay for itself in a day. Some unit tests combinations are still using Go 1.2 because the tests assume OS features because of the Golang version instead of checking the OS: 1. The Makefile rules for installing deps are very stale. Precise unit tests will fail when forced to use Go 1.6 because they cannot start mongo: error command line: unknown option sslOnNormalPorts But we see that actual deployments of precise built with Go 1.6 work. 2. Centos and Windows unit test are still Go 1.2 because many lxd related tests fail when run with Go 1.6. The git-merge-juju job is using the xenial daily image to gate merges. The released image it too stale to do an unattended dist-upgrade The unit test runs for xenial-amd64, xenial-arm64, xenial-s390x, xenial-ppc64el, wily-amd64, trusty-amd64, trusty-i386, and trusty-ppc64el will use the golang (1.6) or golang-1.6 (1.6) packages. The go1.2 trusty unit tests amd64, arm64, i386, and ppc64el are gone. Ubuntu source packages prefer the golang-1.6 package, and fallback to golang (>= 1.2). We needed a new builder because Go 1.6 needs more memory. We saw errors like this with 2G of memory golang-1.6/pkg/tool/linux_amd64/link: running gcc failed: fork/exec /usr/bin/gcc: cannot allocate memory Centos is created using the same Go package as trusty. Windows is cross compiled as 64 bit for agent and 32 bit for clients. OS X is natively compiled using Go 1.6 on CI's OS X host. We also got word is was safe to upgrade our arm64 host to xenial. This is done. The ppc64el hosts were also upgraded this week. We are expanding tests for arm64 and ppc64el -- 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
Juju stable 1.25.5 is proposed for release
# juju-core 1.25.5 A new proposed stable release of Juju, juju-core 1.25.5, is now available. This release may replace version 1.25.3 on Tuesday April 12. ## Getting Juju juju-core 1.25.5 is available for Xenial and backported to earlier series in the following PPA: https://launchpad.net/~juju/+archive/proposed Windows, Centos, and OS X users will find installers at: https://launchpad.net/juju-core/+milestone/1.25.5 Proposed releases use the "proposed" simple-streams. You must configure the `agent-stream` option in your environments.yaml to use the matching juju agents. ## Notable Changes This releases addresses stability and performance issues. ## Resolved issues * 1.25.4: units attempt to go through the proxy to download charm from state server Lp 1556207 * Xenial juju 1.25.3 unable to deploy to lxc containers Lp 1557345 * Provider/maas bridge script is not idempotent Lp 1553915 * Unable to bootstrap lxd provider on s390x Lp 1554675 * Gce invalid volume id destroying environment Lp 1556293 * Juju_availability_zone not set in maas Lp 1559099 * Handle multi-series charms in 1.25 Lp 1563607 * Apt-mirror is not used in containers with maas provider Lp 1560391 * Proxy updater fails with "permission denied" Lp 1564694 * Can-upgrade-to suggests a downgrade Lp 1319890 Finally We encourage everyone to subscribe the mailing list at juju-...@lists.canonical.com, or join us on #juju-dev on freenode. -- 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
Re: armhfentures
On Sat, Mar 12, 2016 at 2:26 PM, Michael Hudson-Doyle <michael.hud...@canonical.com> wrote: > Yes, my advice would definitely be to not worry about fixing this. I hope to > have 1.6 in trusty (-updates BTW, not backports) within a week - just need > to get some time from the over subscribed people who can make it happen. Updates, not backports? great. I favour going to 1.6, but this doesn't solve the precise go 1.2 compilation error. One option is to stop building precise agents in Lp. The process that created the centos agent could also make the precise agent. We still don't have a means to deliver armhf precise client via PPA. -- 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
Juju stable 1.25.4 is proposed for release
# juju-core 1.25.4 A new proposed stable release of Juju, juju-core 1.25.4, is now available. This release may replace version 1.25.3 on Tuesday March 15. ## Getting Juju juju-core 1.25.4 is available for Xenial and backported to earlier series in the following PPA: https://launchpad.net/~juju/+archive/proposed Windows, Centos, and OS X users will find installers at: https://launchpad.net/juju-core/+milestone/1.25.4 Proposed releases use the "proposed" simple-streams. You must configure the 'agent-stream' option in your environments.yaml to use the matching juju agents. ## Notable Changes This releases addresses stability and performance issues. ## Resolved issues * Jujud offers poodle vulnerable sslv3 on 17070 Lp 1536269 * Leadership dependency failures in ci deploy tests Lp 1539656 * Upgrade 1.24.7 -> 1.25.3 fails Lp 1546100 * Destroyed leader, new leader not elected. Lp 1511659 * New ec2 korea region Lp 1530957 * Maas bridge script handles vlan nics incorrectly Lp 1532167 * 1.25.0: bootstrap failure - warning discarding api open error: eof Lp 1538303 * Bootstrap node does not use the proxy to fetch tools from streams.c.c Lp 1515289 * Payload/persistence intermittent failure Lp 1519061 * 1.25.3 can't bootstrap xenial environments Lp 1550306 * Enable daily image stream in juju local provider Lp 1554073 * Juju's maas bridge script is echoed to the console by cloud-init during bootstrap Lp 1536587 * Cookies file locked for too long Lp 1534643 Finally We encourage everyone to subscribe the mailing list at juju-...@lists.canonical.com, or join us on #juju-dev on freenode. -- 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
Re: juju 2.0-alpha2 with lxd
Hi Daniel >>> > On Sun, Feb 14, 2016 at 6:14 PM Daniel Bidwell <drbidw...@gmail.com> >>> > wrote: >>> > > I am trying to bootstrap lxd. ... >>> > > 2016-02-14 23:04:46 ERROR cmd supercommand.go:448 no registered >>> > > provider for "lxd" ... >>> > > >>> > > What do I have to do to "register the lxd provider"? Is this done >>> > > before the boostrap command, during, or after? ... >>> > > What am I missing? >>> > > -- >>> > > Daniel Bidwell <drbidw...@gmail.com> As stated before, The trusty clients in in the PPA were built with an older Go lang Since Juju clients are statically built, you can use any package built for any Ubuntu series on any other Ubuntu series (and centos 7). You can download the wily or xenial package and install it on your host. No need to build. at https://launchpad.net/~juju/+archive/ubuntu/devel/+packages you can find all the packages. I suggest: https://launchpad.net/~juju/+archive/ubuntu/devel/+files/juju-core_2.0-alpha2-0ubuntu1~15.10.1~juju1_amd64.deb -- 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
Juju stable 1.25.3 is now released
# juju-core 1.25.3 A new stable release of Juju, juju-core 1.25.3, is now available. This release replaces version 1.25.0. ## Getting Juju juju-core 1.25.3 is available for Xenial and backported to earlier series in the following PPA: https://launchpad.net/~juju/+archive/stable Windows, Centos, and OS X users will find installers at: https://launchpad.net/juju-core/+milestone/1.25.3 ## Notable Changes This releases addresses stability and performance issues. ## Resolved issues * Unit loses network connectivity during bootstrap: juju 1.25.2 + maas 1.9 Lp 1534795 * "cannot allocate memory" when running "juju run" Lp 1382556 * Bootstrap with the vsphere provider fails to log into the virtual machine Lp 1511138 * Add-machine with vsphere triggers machine-0: panic: juju home hasn't been initialized Lp 1513492 * Using maas 1.9 as provider using dhcp nic will prevent juju bootstrap Lp 1512371 * Worker/storageprovisioner: machine agents attempting to attach environ-scoped volumes Lp 1483492 * Restore: agent old password not found in configuration Lp 1452082 * "ignore-machine-addresses" broken for containers Lp 1509292 * Deploying a service to a space which has no subnets causes the agent to panic Lp 1499426 * /var/lib/juju gone after 1.18->1.20 upgrade and manual edit of agent.conf Lp 1444912 * Juju bootstrap fails to successfully configure the bridge juju-br0 when deploying with wily 4.2 kernel Lp 1496972 * Incompatible cookie format change Lp 1511717 * Error environment destruction failed: destroying storage: listing volumes: get https://x.x.x.x:8776/v2//volumes/detail: local error: record overflow Lp 1512399 * Replica set emptyconfig maas bootstrap Lp 1412621 * Juju can't find daily image streams from cloud- images.ubuntu.com/daily Lp 1513982 * Rsyslog certificate fails when using ipv6/4 dual stack with prefer-ipv6: true Lp 1478943 * Improper address:port joining Lp 1518128 * Juju status broken Lp 1516989 * 1.25.1 with maas 1.8: devices dns allocation uses non-unique hostname Lp 1525280 * Increment minimum juju version for 2.0 upgrade to 1.25.3 Lp 1533751 * Make assignment of units to machines use a worker Lp 1497312 * `juju environments` fails due to missing ~/.juju/current- environment Lp 1506680 * Juju 1.25 misconfigures juju-br0 when using maas 1.9 bonded interface Lp 1516891 * Destroy-environment on an unbootstrapped maas environment can release all my nodes Lp 1490865 * On juju upgrade the security group lost ports for the exposed services Lp 1506649 * Support centos and windows image metadata Lp 1523693 * Upgrade-juju shows available tools and best version but did not output what it decided to do Lp 1403655 * Invalid binary version, version "1.23.3--amd64" or "1.23.3--armhf" Lp 1459033 * Add xenial to supported series Lp 1533262 Finally We encourage everyone to subscribe the mailing list at juju-...@lists.canonical.com, or join us on #juju-dev on freenode. -- 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
Testing Juju devel 2.0-alpha1 in AWS, Azure, and Joyent
We are investigating an issue with the agent stream mirrors in AWS, Azure, and Joyent. Bootstrapping will fail with a report there are not matching tools. There are. The work-around is to set this in the environments.yaml: agent-metadata-url: https://streams.canonical.com/juju/tools ^ this is non-obvious since it should be a no-op, but in fact restores the 1.x default behaviour. Agents are indeed found in the public cloud. Users GCE, Rackspace, and private clouds are not affected by this issue. We believe this is a temporary issue. We will send announcement to this list when the issue is resolved and the work-around is not needed. -- 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
Juju devel 2.0-alpha1 is available for testing
ine (machine-N.log) and per unit
(unit-*-N.log) log files that exist on each Juju managed host. These
continue to function as they did before.
A new 'juju-dumplogs' tool is also now available. This can be run on
Juju controllers to extract the logs from Juju's database even when the
Juju server isn't available. It is intended to be used as a last resort
in emergency situations. 'juju-dumplogs' will be available on the system
$PATH and requires no command line options in typical usage.
### API Login with Macaroons
Juju 2.0 supports an alternate API long method based on macaroons. This
will support the new charm publishing workflow coming future releases
### Unit Agent Improvements
We've made improvements to worker lifecycle management in the unit agent
in this release. The resource dependencies (API connections, locks,
etc.) shared among concurrent workers that comprise the agent are now
well-defined, modeled and coordinated by an engine, in a design inspired
by Erlang supervisor trees.
This improves the long-term testability of the unit agent, and should
improve the agent's resilience to failure. This work also allows hook
contexts to execute concurrently, which supports features in development
targeting 2.0.
### MAAS 1.8 Compatibility
Juju 2.0-alpha1 includes the fix for bug #1483879: MAAS provider:
terminate-machine --force or destroy-environment don't DHCP release
container IPs. The fix uses the "devices" feature of MAAS, which has a
known bug on MAAS 1.8 (bug #1527068: MAAS retains child devices' IP
addresses when a parent node is released). There is a work around to
clean up the leaked IPs available in bug #1527068:
https://bugs.launchpad.net/juju-core/+bug/1527068/comments/10
Users on MAAS 1.8 should also set the default gateway for the interface
used by juju to avoid problems with container networking. You can
verify whether a default gateway has been set on an interface by looking
at the network details in the "Networks" tab.
## Known issues
* Some providers release wrong resources when destroying hosted models
Lp 1536792
* Destroying a hosted model in the local provider leaves the controller
unusable
Lp 1534636
* Unable to create hosted environments with MAAS provider
Lp 1535165
## Resolved issues
* Unit loses network connectivity during bootstrap: juju 1.25.2 +
maas 1.9
Lp 1534795
* Juju debug-log and eof
Lp 1390585
* I/o timeout errors can cause non-atomic service deploys
Lp 1486553
* Azure provider does not appear to be opening ports
Lp 1527681
* 1.25.2 doesn't set up dns information with maas
Lp 1528217
* Lxd: cannot create multiple environments
Lp 1531064
* Wrong command displayed when trying to destroy a controller with
destroy-environment
Lp 1534353
Finally
We encourage everyone to subscribe the mailing list at
juju-...@lists.canonical.com, or join us on #juju-dev on freenode.
--
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
Juju stable 1.25.3 is proposed for release
# juju-core 1.25.3 A new proposed stable release of Juju, juju-core 1.25.3, is now available. This release may replace version 1.25.0 on Thursday January 21. ## Getting Juju juju-core 1.25.3 is available for Xenial and backported to earlier series in the following PPA: https://launchpad.net/~juju/+archive/proposed Windows, Centos, and OS X users will find installers at: https://launchpad.net/juju-core/+milestone/1.25.3 Proposed releases use the "proposed" simple-streams. You must configure the `agent-stream` option in your environments.yaml to use the matching juju agents. ## Notable Changes This releases addresses a defect discovered in proposed 1.25.2 ## Resolved issues * Unit loses network connectivity during bootstrap: juju 1.25.2 + maas 1.9 Lp 1534795 * "cannot allocate memory" when running "juju run" Lp 1382556 * Bootstrap with the vsphere provider fails to log into the virtual machine Lp 1511138 * Add-machine with vsphere triggers machine-0: panic: juju home hasn't been initialized Lp 1513492 * Using maas 1.9 as provider using dhcp nic will prevent juju bootstrap Lp 1512371 * Worker/storageprovisioner: machine agents attempting to attach environ-scoped volumes Lp 1483492 * Restore: agent old password not found in configuration Lp 1452082 * "ignore-machine-addresses" broken for containers Lp 1509292 * Deploying a service to a space which has no subnets causes the agent to panic Lp 1499426 * /var/lib/juju gone after 1.18->1.20 upgrade and manual edit of agent.conf Lp 1444912 * Juju bootstrap fails to successfully configure the bridge juju-br0 when deploying with wily 4.2 kernel Lp 1496972 * Incompatible cookie format change Lp 1511717 * Error environment destruction failed: destroying storage: listing volumes: get https://x.x.x.x:8776/v2//volumes/detail: local error: record overflow Lp 1512399 * Replica set emptyconfig maas bootstrap Lp 1412621 * Juju can't find daily image streams from cloud- images.ubuntu.com/daily Lp 1513982 * Rsyslog certificate fails when using ipv6/4 dual stack with prefer-ipv6: true Lp 1478943 * Improper address:port joining Lp 1518128 * Juju status broken Lp 1516989 * 1.25.1 with maas 1.8: devices dns allocation uses non-unique hostname Lp 1525280 * Increment minimum juju version for 2.0 upgrade to 1.25.3 Lp 1533751 * Make assignment of units to machines use a worker Lp 1497312 * `juju environments` fails due to missing ~/.juju/current- environment Lp 1506680 * Juju 1.25 misconfigures juju-br0 when using maas 1.9 bonded interface Lp 1516891 * Destroy-environment on an unbootstrapped maas environment can release all my nodes Lp 1490865 * On juju upgrade the security group lost ports for the exposed services Lp 1506649 * Support centos and windows image metadata Lp 1523693 * Upgrade-juju shows available tools and best version but did not output what it decided to do Lp 1403655 * Invalid binary version, version "1.23.3--amd64" or "1.23.3--armhf" Lp 1459033 * Add xenial to supported series Lp 1533262 Finally We encourage everyone to subscribe the mailing list at juju-...@lists.canonical.com, or join us on #juju-dev on freenode. -- 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
Juju devel 1.26-alpha3 is realeased
earching published Ubuntu images found on http://cloud-images.ubuntu.com, Windows and Centos image metadata will be published to https://streams.canonical.com/juju/images. This will allow Windows and Centos workloads to be deployed to AWS and other supported clouds. ### Azure provider changes The new Azure provider announced in 1.26-alpha2 was updated in response to your feedback. The 'application-key' in the config was renamed to 'application-password'. To use the new Azure support, you need the following configuration in environments.yaml: type: azure application-id: application-password: subscription-id: tenant-id: location: westus # or any other Azure location To obtain these values, it is recommended that you use the Azure CLI: https://azure.microsoft.com/en-us/documentation/articles/xplat-cli/. You will need to create an "application" in Azure Active Directory for Juju to use, per the following documentation: https://azure.microsoft.com/en-us/documentation/articles/resource-group-authenticate-service-principal/#authenticate-service-principal-with-password---azure-cli (NOTE: you should assign the role "Owner", not "Reader", to the application.) Take a note of the "Application Id" output when issuing "azure ad app create". This is the value that you must use in the 'application-id' configuration for Juju. The password you specify is the value to use in 'application-password'. To obtain your subscription ID, you can use "azure account list" to list your account subscriptions and their IDs. To obtain your tenant ID, you should use "azure account show", passing in the ID of the account subscription you will use. You may need to register some resources using the azure CLI when updating an existing Azure account: azure provider register Microsoft.Compute azure provider register Microsoft.Network azure provider register Microsoft.Storage ## Known Issues ARM-HF clients and agents are not available Precise, Trusty and Vivid. Clients and agents are available for Wily. ## Resolved issues * Bootstrap with the vsphere provider fails to log into the virtual machine Lp 1511138 * Using maas 1.9 as provider using dhcp nic will prevent juju bootstrap Lp 1512371 * Add-machine with vsphere triggers machine-0: panic: juju home hasn't been initialized Lp 1513492 * 'debug-log' fails when logs are large when using db-log Lp 1524135 * Upgrade-juju shows available tools and best version but did not output what it decided to do Lp 1403655 * Invalid binary version, version "1.23.3--amd64" or "1.23.3--armhf" Lp 1459033 * Output from metadata generate-image looks bad Lp 1489215 * Addresses logged by apiaddressupdater aren't accurate Lp 1497098 * Session closed in data source Lp 1497829 * 'juju environments' fails due to missing ~/.juju/current- environment Lp 1506680 * Juju can't find daily image streams from cloud- images.ubuntu.com/daily Lp 1513982 * Juju 1.25 misconfigures juju-br0 when using maas 1.9 bonded interface Lp 1516891 * Lxd cannot bootstrap with image streams Lp 1519027 * Support centos and windows image metadata Lp 1523693 * Deploy incompatible charm using --to should error earlier Lp 1524527 * Deploy charm with --series --force doesn't reject invalid os Lp 1526296 * Juju should check common failure conditions before upgrading Lp 1521354 Finally We encourage everyone to subscribe the mailing list at juju-...@lists.canonical.com, or join us on #juju-dev on freenode. -- 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
Re: Juju devel 1.26-alpha2 is available for testing
There are other options to play with juju+lxd on trusty... On Fri, Nov 27, 2015 at 2:26 PM, Rick Harding <rick.hard...@canonical.com> wrote: > > On Fri, Nov 27, 2015 at 11:35 AM Mark Shuttleworth <m...@ubuntu.com> wrote: >> >> On 27/11/15 16:21, Aaron Bentley wrote: >> >> It's dependent on what compiler was used to create the jujud binary. >> AIUI, the Ubuntu policy is that nothing goes into a distroseries which >> cannot be compiled with the tools in that distroseries. Thus the >> jujud for Trusty is compiled with the version of Go provided by that >> platform. >> >> >> My understanding is that a Go 1.5 backport to Trusty is part of the >> current cycle planned work. > > > Yes, the work for Go 1.5 into Trusty moves forward. For this alpha it's not > yet ready to provide the build so my understanding is that the alpha build > for Trusty is done with the current outdated tool chain. Once the Go > toolchain is updated for Trusty the builds released will be in order. > > Aaron, please correct me if I'm mistaken there. The Juju clients and agents built with Go lang are statically compiled. They are Ubuntu release agnostic. The wily-built Juju runs fine on Trusty and Precise (and Centos 7). You can install the wily juju-core and juju-local packages to play with the lxd feature now. Per the conversation above, the Juju PPAs build with a deps that provides the Juju teams minimum and preferred Golang. We used this to get newer Gos for precise without waiting on Ubuntu. We plan to switch to switch to Go 1.5 soon at a part of our plan to change Juju's minimum version of Go. -- 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
Re: Upgrading minimum Go version?
On Mon, Nov 30, 2015 at 10:36 AM, John Meinel <j...@arbash-meinel.com> wrote: > Given how often people still use "--upload-tools" for things like private > clouds (and is definitely the one used for local provider), I'd really worry > about having a jujud on your local machine that wasn't built with the same > toolchain as the one you get from "juju bootstrap" in other cases. Very easy > to end up with hard to understand/reproduce bugs. I share your concerns John. We have seen several bugs marked invalid because the agent uploads is essentially unknown origin because Juju is more than willing to fake a version when uploading. There are also reports of Juju attempting to build agents from source: https://bugs.launchpad.net/juju-core/+bug/1399606 We do want everyone using the agent in streams, which have a lot more testing behind them. The agent (jujud) on users of the Juju stable PPA is the same that was used to make streams. This is not true for users of Ubuntu's packages, and we know Ubuntu can change its tool chain between the time we create official agents and it builds its packages. We do testing to certify they Ubuntu clients and agents are functionally equivalent to those in the PPA and streams. As Ubuntu Wily+ prefers system Go dev packages to the embedded go packages we provide, Ubuntu's packages will contain more divergence than Trusty. We are obligated to do on-demand testing to certify a change to a system Go dev package. Ideally, We would separate the jujud from juju-core package that provides the client. Users don't get a jujud when they install a client. Instead, Juju can get the desired agents from streams. -- 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
Re: Upgrading minimum Go version?
Good discussion. I have one nuance that I think we want to discuss in SFO. Namely, controlling the Juju tool chain. Juju QA uses CI to make many of the things we releases, such as win agents. We use Launchpad/Ubuntu to make Ubuntu agents and clients. Juju QA qill soon have access to ARM hardware. When we do, we can choose to by-pass Lp/Ubuntu for agents. The agents that were built and tested by CI are the agents we release in streams. This permits us to choose the best tool chain to create each series+arch combination. This also introduces drift between what Juju officially releases, and and Ubuntu releases. On Thu, Nov 26, 2015 at 8:27 PM, Andrew Wilkins <andrew.wilk...@canonical.com> wrote: > On Fri, Nov 27, 2015 at 7:49 AM Michael Hudson-Doyle > <michael.hud...@canonical.com> wrote: >> >> On 27 November 2015 at 09:39, Tim Penhey <tim.pen...@canonical.com> wrote: >> > On 27/11/15 08:43, Michael Hudson-Doyle wrote: >> >> On 27 November 2015 at 02:24, Martin Packman >> >> <martin.pack...@canonical.com> wrote: >> >>> On 26/11/2015, Andrew Wilkins <andrew.wilk...@canonical.com> wrote: >> >>>> Hi (mostly Curtis), >> >>>> >> >>>> Is there a plan to bump the minimum Go version? Some of our >> >>>> dependencies do >> >>>> not build with Go 1.2. The LXD provider only builds with Go 1.3 (I >> >>>> think?), >> >>>> and I've got a PR up that updates the azure-sdk-for-go dependency, >> >>>> but it's >> >>>> blocked because the newer doesn't build with Go 1.2. >> >> >> >> Is this something we've done to ourselves or is there a third-party >> >> library we're depending on that doesn't work with Go 1.2? >> > >> > The two main ones I know about are lxd and the new azure go bindings. >> >> By the azure go bindings you mean something Canonical didn't write, >> like https://github.com/Azure/azure-sdk-for-go? That sort of thing >> sounds like a good argument for the 1.5-in-trusty SRU thing. -- 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
Re: lxd provider in master
On Mon, Nov 23, 2015 at 10:53 AM, Eric Snow <eric.s...@canonical.com> wrote: > On Sun, Nov 22, 2015 at 8:50 PM, Tim Penhey <tim.pen...@canonical.com> wrote: >> But when I try to bootstrap, I get the following: >> >> $ juju bootstrap --debug Also note that the lxd-deploy-wily-amd64 test still fails when lxd provider tries to use streams. The bootstrap command does not "just work" http://reports.vapour.ws/releases/3338/job/lxd-deploy-wily-amd64/attempt/41 Bootstrap with --upload-tools until this lxd is fixed. juju bootstrap --debug --upload-tools -- 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
Juju stable 1.25.1 is proposed
# juju-core 1.25.1 A new proposed stable release of Juju, juju-core 1.25.1, is now available. This release may replace version 1.25.0 on Tuesday Dec 1. ## Getting Juju juju-core 1.25.1 is available for Wily and backported to earlier series in the following PPA: https://launchpad.net/~juju/+archive/proposed Windows, Centos, and OS X users will find installers at: https://launchpad.net/juju-core/+milestone/1.25.1 Proposed releases use the "proposed" simple-streams. You must configure the `agent-stream` option in your environments.yaml to use the matching juju agents. ## Notable Changes This releases addresses stability and performance issues. ## Resolved issues * "cannot allocate memory" when running "juju run" Lp 1382556 * Bootstrap with the vsphere provider fails to log into the virtual machine Lp 1511138 * Add-machine with vsphere triggers machine-0: panic: juju home hasn't been initialized Lp 1513492 * Using maas 1.9 as provider using dhcp nic will prevent juju bootstrap Lp 1512371 * Worker/storageprovisioner: machine agents attempting to attach environ-scoped volumes Lp 1483492 * Restore: agent old password not found in configuration Lp 1452082 * "ignore-machine-addresses" broken for containers Lp 1509292 * Deploying a service to a space which has no subnets causes the agent to panic Lp 1499426 * /var/lib/juju gone after 1.18->1.20 upgrade and manual edit of agent.conf Lp 1444912 * Maas provider: terminate-machine --force or destroy-environment don't dhcp release container ips Lp 1483879 * Juju bootstrap fails to successfully configure the bridge juju-br0 when deploying with wily 4.2 kernel Lp 1496972 * Incompatible cookie format change Lp 1511717 * Error environment destruction failed: destroying storage: listing volumes: get https://x.x.x.x:8776/v2//volumes/detail: local error: record overflow Lp 1512399 * Replica set emptyconfig maas bootstrap Lp 1412621 * Juju can't find daily image streams from cloud- images.ubuntu.com/daily Lp 1513982 * Rsyslog certificate fails when using ipv6/4 dual stack with prefer-ipv6: true Lp 1478943 * Improper address:port joining Lp 1518128 Finally We encourage everyone to subscribe the mailing list at juju-...@lists.canonical.com, or join us on #juju-dev on freenode. -- 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
Re: Juju stable 1.24.7 is released
I have a correction. 1.24.7 is now in the stable juju PPA. On Thu, Oct 22, 2015 at 11:57 AM, Curtis Hovey-Canonical <cur...@canonical.com> wrote: ... > ## Getting Juju > > juju-core 1.24.7 is available for Wily and backported to earlier > series in the following PPA: > >https://launchpad.net/~juju/+archive/proposed > > Windows, Centos7, and OS X users will find installers at: > >https://launchpad.net/juju-core/+milestone/1.24.7 ## Getting Juju juju-core 1.24.7 is available for Wily and backported to earlier series in the following PPA: https://launchpad.net/~juju/+archive/stable Windows, Centos7, and OS X users will find installers at: https://launchpad.net/juju-core/+milestone/1.24.7 -- 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
Juju stable 1.24.7 is released
# juju-core 1.24.7 A new stable release of Juju, juju-core 1.24.7, is now available. This release replaces version 1.24.6. ## Getting Juju juju-core 1.24.7 is available for Wily and backported to earlier series in the following PPA: https://launchpad.net/~juju/+archive/proposed Windows, Centos7, and OS X users will find installers at: https://launchpad.net/juju-core/+milestone/1.24.7 ## Notable Changes ### The default EC2 instance is m3.medium AWS deprecated the m1.* instance type. Juju now uses the m3.medium as the default instance type when provisioning machines in EC2. * m1.* instances will only be selected when specified using the "instance-type" constraint. * When no constraints are specified, the m3.medium type will be selected. * When constraints are specified, m1 instance types which satisfy the constraints will be ignored. ### Use the "storage" feature flag to try charms that support storage. Storage was classified as experimental in 1.24, and has been found to be problematic. Since storage is used implicitly by charms with default stores, the feature was placed behind a feature flag. You can test charms that support storage by bootstrapping a new environment with "storage" enabled like so: JUJU_DEV_FEATURE_FLAG=storage juju bootstrap ## Resolved issues * Maas provider with maas 1.9 - /etc/network/interfaces "auto eth0" gets removed and bridge is not setup Lp 1494476 * Switch default instance type from m1.small to t2.small/m3.medium for ec2 provider Lp 1373516 * Destroy-environment reports warning cannot delete security group Lp 1335885 * Storage should be behind a feature flag in 1.24 Lp 1503740 * Configstore should break fslock if time > few seconds Lp 1500613 * Config-changed error does not cause error state Lp 1494542 * Setapihostports shouldn't record just one address per api server Lp 1497094 * Failed worker can result in large number of goroutines and open socket connections and eventually gets picked on by the oom killer Lp 1496750 * Upgrade in progress reported, but panic happening behind scenes Lp 1493123 * juju occasionally switches a units public-address if an additional interface is added post-deployment Lp 1435283 Finally We encourage everyone to subscribe to the mailing list at juju-...@lists.canonical.com, or join us on #juju-dev on freenode. -- 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
Re: Juju stable 1.24.4 is released
On Mon, Aug 17, 2015 at 4:09 PM, Mark Shuttleworth m...@ubuntu.com wrote: These release updates are very helpful, thanks Curtis. Would it be possible to tag the resolved issues a particular way if they are regressions? Sometimes we put out a point release which fixes longstanding issues, sometimes there are items which regressed, and it would be useful to get a feel for the balance of those. We sure can. * Juju 1.22.6 cannot upgrade to 1.24.3/1.24.4 Lp 1479931 ^ This was a regression. -- 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
Juju stable 1.24.5 is released
# juju-core 1.24.5 A new stable release of Juju, juju-core 1.24.5, is now available. This release replaces version 1.24.4. ## Getting Juju juju-core 1.24.5 is available for Wily and backported to earlier series in the following PPA: https://launchpad.net/~juju/+archive/stable Windows, Centos, and OS X users will find installers at: https://launchpad.net/juju-core/+milestone/1.24.5 ## Notable Changes This releases addresses stability and performance issues. ## Resolved issues * Deploy hangs: jujud-machine-0 upstart process running but juju status shows it down Lp 1481368 * Juju uses proxy to access bootstrap node Lp 1478660 Finally We encourage everyone to subscribe the mailing list at juju-...@lists.canonical.com, or join us on #juju-dev on freenode. -- 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
juju supported 1.22.8 is released
# juju-core 1.22.8 A new supported release of Juju, juju-core 1.22.8, is now available. This release replaces version 1.22.6. ## Getting Juju juju-core 1.22.8 is available for Wily and backported to earlier series in the following PPA: https://launchpad.net/~juju/+archive/1.22 Windows and OS X users will find installers at: https://launchpad.net/juju-core/+milestone/1.22.8 ## Notable Changes This releases addresses stability and performance issues. ## Resolved issues * Juju uses proxy to access bootstrap node Lp 1478660 * Juju environment not usable after the upgrade Lp 1473517 Finally We encourage everyone to subscribe the mailing list at juju-...@lists.canonical.com, or join us on #juju-dev on freenode. -- 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
Juju stable 1.24.5 is proposed
# juju-core 1.24.5 A new proposed stable release of Juju, juju-core 1.24.5, is now available. This release may replace version 1.24.4 on Monday August 17. ## Getting Juju juju-core 1.24.5 is available for Wily and backported to earlier series in the following PPA: https://launchpad.net/~juju/+archive/proposed Windows and OS X users will find installers at: https://launchpad.net/juju-core/+milestone/1.24.5 Proposed releases use the proposed simple-streams. You must configure the `agent-stream` option in your environments.yaml to use the matching juju agents. ## Notable Changes This releases addresses stability and performance issues. ## Resolved issues * Deploy hangs: jujud-machine-0 upstart process running but juju status shows it down Lp 1481368 * Juju uses proxy to access bootstrap node Lp 1478660 Finally We encourage everyone to subscribe the mailing list at juju-...@lists.canonical.com, or join us on #juju-dev on freenode. -- 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
Juju stable 1.24.4 is released
# juju-core 1.24.4 A new stable release of Juju, juju-core 1.24.4, is now available. This release replaces version 1.24.3. ## Getting Juju juju-core 1.24.4 is available for Wily and backported to earlier series in the following PPA: https://launchpad.net/~juju/+archive/stable Windows OS X, and Centos users will find installers at: https://launchpad.net/juju-core/+milestone/1.24.4 ## Notable Changes This releases addresses stability and performance issues. ## Resolved issues * Looping config-changed hooks in fresh juju-core 1.24.3 openstack deployment Lp 1478024 * Cannot boostrap from custom image-metadata-url or by specifying metadata-source Lp 1452422 * No output from ssh problems during bootstrap Lp 1477358 * Leadership unreliable in HA Lp 1461890 * Juju 1.22.6 cannot upgrade to 1.24.3/1.24.4 Lp 1479931 Finally We encourage everyone to subscribe the mailing list at juju-...@lists.canonical.com, or join us on #juju-dev on freenode. -- 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
Juju supported 1.22.8 is proposed
# juju-core 1.22.8 A new proposed stable release of Juju, juju-core 1.22.8, is now available. This release may replace version 1.22.6 on Thursday August 13. ## Getting Juju juju-core 1.22.8 is available for Wily and backported to earlier series in the following PPA: https://launchpad.net/~juju/+archive/1.22-proposed Windows and OS X users will find installers at: https://launchpad.net/juju-core/+milestone/1.22.8 Proposed releases use the proposed simple-streams. You must configure the `agent-stream` option in your environments.yaml to use the matching juju agents. ## Notable Changes This releases addresses stability and performance issues. ## Resolved issues * Juju uses proxy to access bootstrap node Lp 1478660 * Juju environment not usable after the upgrade Lp 1473517 Finally We encourage everyone to subscribe the mailing list at juju-...@lists.canonical.com, or join us on #juju-dev on freenode. -- 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
Juju supported 1.22.7 is proposed
# juju-core 1.22.7 A new proposed supported release of Juju, juju-core 1.22.7, is now available. This release may replace version 1.22.6 on Thursday August 13. The 1.20.x series of Juju is supported, though it is an older version than the current stable version. The current stable of juju is 1.24.3 ## Getting Juju juju-core 1.22.7 is available for Wily and backported to earlier series in the following PPA: https://launchpad.net/~juju/+archive/1.22-proposed Windows and OS X users will find installers at: https://launchpad.net/juju-core/+milestone/1.22.7 Proposed releases use the proposed simple-streams. You must configure the `agent-stream` option in your environments.yaml to use the matching juju agents. ## Notable Changes This releases addresses stability and performance issues. ## Resolved issues * Juju environment not usable after the upgrade Lp 1473517 Finally We encourage everyone to subscribe the mailing list at juju-...@lists.canonical.com, or join us on #juju-dev on freenode. -- 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
Juju statbe 1.24.4 is proposed
# juju-core 1.24.4 A new proposed stable release of Juju, juju-core 1.24.4, is now available. This release may replace version 1.24.3 on Monday August 10. ## Getting Juju juju-core 1.24.4 is available for Wily and backported to earlier series in the following PPA: https://launchpad.net/~juju/+archive/proposed Windows and OS X users will find installers at: https://launchpad.net/juju-core/+milestone/1.24.4 Proposed releases use the proposed simple-streams. You must configure the `agent-stream` option in your environments.yaml to use the matching juju agents. ## Notable Changes This releases addresses stability and performance issues. ## Resolved issues * Looping config-changed hooks in fresh juju-core 1.24.3 openstack deployment Lp 1478024 * Cannot boostrap from custom image-metadata-url or by specifying metadata-source Lp 1452422 * No output from ssh problems during bootstrap Lp 1477358 * Leadership unreliable in HA Lp 1461890 * Juju 1.22.6 cannot upgrade to 1.24.3/1.24.4 Lp 1479931 Finally We encourage everyone to subscribe the mailing list at juju-...@lists.canonical.com, or join us on #juju-dev on freenode. -- 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
Juju stable 1.24.3 is proposed
# juju-core 1.24.3 A new proposed stable release of Juju, juju-core 1.24.3, is now available. This release may replace version 1.24.2 on Monday July 27. ## Getting Juju juju-core 1.24.3 is available for Wily and backported to earlier series in the following PPA: https://launchpad.net/~juju/+archive/proposed Windows, OS X, and Centos users will find installers at: https://launchpad.net/juju-core/+milestone/1.24.3 Proposed releases use the proposed simple-streams. You must configure the `agent-stream` option in your environments.yaml to use the matching juju agents. ## Notable Changes This releases addresses stability and performance issues. ## Resolved issues * Upgrade fails on windows machines Lp 1471332 * Juju 1.24.0: wget cert issues causing failure to create containers on 14.04.2 with lxc 1.07 Lp 1472014 * Juju environment not usable after the upgrade Lp 1473517 * Rsyslog connections fail with certificate verification errors after upgrade to 1.24.2 Lp 1474614 * Rebooting the virtual machines breaks juju networking Lp 1474508 * Failed upgrade, mixed up ha addresses Lp 1463480 * Debug-log does not work with local provider Lp 1464335 * Jujud hanging after upgrading from 1.24.0 to 1.24.1(and 1.24.2) Lp 1468653 * Juju bootstrap fails - waiting for api to become available error cannot get all blocks: eof Lp 1468581 * Tools migration fails when upgrading 1.20.14 to 1.24.1 on ec2 Lp 1469130 * State server seems to have died Lp 1469199 * Github.com/juju/utils has contradictory licences Lp 1472749 * Transient error with juju-unit-agent on windows hosts Lp 1430245 * Agent shutdown can cause cert updater channel already closed panic Lp 1472729 * Juju 1.24 memory leakage Lp 1474195 * $set updates may clear out the env-uuid field Lp 1474606 * Ec2: provisioning machines sometimes fails with tagging instance: the instance id id does not exist Lp 1474788 * When the uniter fails to run an operation due to an error, the agent state is not set to failed Lp 1475163 Finally We encourage everyone to subscribe the mailing list at juju-...@lists.canonical.com, or join us on #juju-dev on freenode. -- 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
Juju stable 1.24.2 is released
# juju-core 1.24.2 A new stable release of Juju, juju-core 1.24.2, is now available. This release replaces version 1.24.0. ## Getting Juju juju-core 1.24.2 is available for Wily and backported to earlier series in the following PPA: https://launchpad.net/~juju/+archive/stable Windows, Centos, and OS X users will find installers at: https://launchpad.net/juju-core/+milestone/1.24.2 ## Notable Changes This releases addresses stability and performance issues. ## Resolved issues * Destroy-machine --force no longer forceably destroys machine Lp 1464616 * Inconsistent juju status from cli vs api Lp 1467690 * Dhcp addresses for containers should be released on teardown Lp 1348663 * relation-set --file - doesn't seem to work Lp 1454678 * Debug-hooks no longer works with 1.24-beta6 Lp 1466167 * Panic if jujud restarts while action is running Lp 1447895 * Mysterious env.lock held message Lp 1454323 * Upgrade fails moving syslog config files invalid argument Lp 1468815 * Leadership settings documents written out without env-uuid field Lp 1468994 * Debug-log does not work with local provider Lp 1464335 * A subordinate charm hook scheduled to run(but waiting for the principal charm hook to release the lock) goes to an error state after the principal charm hook triggers a reboot. Lp 1464470 * Upgrading 1.20.14 - 1.24.0 fails Lp 1466969 * Subordinate charm action data not reported by api Lp 1457205 * Centos fails to bootstrap using juju 1.24 Lp 1470150 Finally We encourage everyone to subscribe the mailing list at juju-...@lists.canonical.com, or join us on #juju-dev on freenode. -- 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
Juju supported 1.22.6 is released
# juju-core 1.22.6 A new supported release of Juju, juju-core 1.22.6, is now available. This release replaces version 1.22.5. Juju 1.22.x is an older supported version of Juju. The current Juju version is 1.24.0. ## Getting Juju juju-core 1.22.6 is available for vivid and backported to earlier series in the following PPA: https://launchpad.net/~juju/+archive/1.22 Windows and OS X users will find installers at: https://launchpad.net/juju-core/+milestone/1.22.6 ## Notable Changes This releases addresses stability and performance issues. ## Resolved issues * State: availability zone upgrade fails if containers are present Lp 1441478 * LXC provisioning fails on joyent Lp 1461150 * Worker/diskmanager sometimes goes into a restart loop due to failing to update state Lp 1461871 * Package github.com/juju/txn has conflicting licences Lp 1463455 Finally We encourage everyone to subscribe the mailing list at juju-...@lists.canonical.com, or join us on #juju-dev on freenode. -- 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
Juju supported 1.22.6 is proposed
# juju-core 1.22.6 A new proposed supported release of Juju, juju-core 1.22.6, is now available. This release may replace version 1.22.5 on Tuesday June 23. Juju 1.22.x is an older supported version of juju. The current Juju version is 1.24.0 . ## Getting Juju juju-core 1.22.6 is available for vivid and backported to earlier series in the following PPA: https://launchpad.net/~juju/+archive/proposed Windows and OS X users will find installers at: https://launchpad.net/juju-core/+milestone/1.22.6 Proposed releases use the proposed simple-streams. You must configure the `agent-stream` option in your environments.yaml to use the matching juju agents. ## Notable Changes This releases addresses stability and performance issues. ## Resolved issues * State: availability zone upgrade fails if containers are present Lp 1441478 * Lxc provisioning fails on joyent Lp 1461150 * Worker/diskmanager sometimes goes into a restart loop due to failing to update state Lp 1461871 * Package github.com/juju/txn has conflicting licences Lp 1463455 Finally We encourage everyone to subscribe the mailing list at juju-...@lists.canonical.com, or join us on #juju-dev on freenode. -- 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
Juju stable 1.24.0 is released
instances for containers; cannot retry containers at all Lp 1428439 * Debug-hooks exit 1 , doesn't mark hook as failed Lp 1415176 * Default storage constraints are not quite correct Lp 1452535 * Maas: implement root-disk constraint Lp 1212689 * Juju upgrade-juju failed to configure mongodb replicasets Lp 1441913 * Provider/openstack: volumes are recorded with 0 size Lp 1450740 * Persist iptables rules / routes for addressable containers across host reboots Lp 1442012 * Deployer sometimes fails with a unit status not found error Lp 1451283 * Logs don't rotate Lp 1452285 * Collect-metric hook failure, metric batch uuid already exists Lp 1452487 * Juju machine service for windows creates incorrect tools symlinks Lp 1453280 * /var/spool/rsyslog grows without bound Lp 1453801 * Instancepoller compares wrong address list and always requests updated state addresses Lp 1454043 * Agents see too many open files errors after many failed api attempts Lp 1420057 * Container destruction doesn't mark ip addresses as dead Lp 1441206 * Debug-hooks not working with manually provisioned machines Lp 1429790 * Joyent machines get stuck in provisioning Lp 1446264 * Cannot process charms: finding charm revision info: cannot get metadata from the charm store: verification failed: no macaroon cookies in request Lp 1453238 * Juju log spams error juju.worker.diskmanager lsblk.go:111 error checking if sr0 is in use: open /dev/sr0: no medium found Lp 1454481 * Failed to retrieve the template to clone - 500 internal server error - error creating container juju-trusty-lxc-template - Lp 1454676 * 1.20.x client cannot communicate with 1.22.x env Lp 1454829 * Received disconnect from ...: 2: too many authentication failures for ubuntu Lp 1456315 * Lxc network.mtu setting not set consistently across hosts Lp 1442257 * Transaction collection (txns) grows without bound Lp 1453785 * Firewaller gets an exception if a machine is not provisioned Lp 1454599 * Jujud leaking file handles Lp 1454697 * Destroying a machine with a placed unit errors then destroys anyway. Lp 1455158 * Intermittent panic: rescanned document Lp 1449054 * `juju upgrade-juju --upload-tools` leaves local environment unusable Lp 1457728 * warning: log line attempted over max size - leadership related Lp 1457645 * Debug-log eof: invalid tag and panic seen in state server logs Lp 1461354 * Juju has conf files in /var/log/juju on instances Lp 1370896 * Juju restore fails with /var/lib/juju/agents: no such file or directory Lp 1431372 * Cannot destroy-environment with 'juju user add' .jenv file Lp 1403165 * Juju cannot create vivid containers Lp 1442308 * State: availability zone upgrade fails if containers are present Lp 1441478 * 1.23.2.1, mongo: document is larger than capped size Lp 1454891 * relation-set --file - doesn't seem to work Lp 1454678 * Maas provider doesn't know about failed deployment instance status Lp 1376246 * Juju status --utc does not display utc and is confused Lp 1459611 * Juju agent opens api when upgrade is pending Lp 1459912 * 'juju status' wall clock timestamps should display offset not tz abbrev Lp 1459616 * Harvest mode setting not used by container provisioner Lp 1459885 * Allow status-set/get to a service by its leader unit Lp 146 * Unit storage add should only accept count as constraint Lp 1461342 * Golang.org/x/sys/windows requires go 1.4 Lp 1463439 * Erroneous juju user data on windows for juju version 1.23 Lp 1451626 * Cmd/juju/storage: add fails to dynamically add filesystem for storage Lp 1462146 * Worker/diskmanager sometimes goes into a restart loop due to failing to update state Lp 1461871 * Juju 1.24-beta6.1 unit commands in debug-hooks hang indefinitely Lp 1463117 Finally We encourage everyone to subscribe the mailing list at juju-...@lists.canonical.com, or join us on #juju-dev on freenode. -- 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
Juju stable 1.24.0 is proposed for release
shouldn't use Ubuntu specific calls (such as apt). There is a guide for setting up a MaaS environment using CentOS at http://wiki.cloudbase.it/juju-centos Note that Centos 7 agents are already in streams. There is no need install Go, compile, tar, and running juju metadata. You can sync the streams to a web server visible to your Juju environment. mkdir local juju sync-tools --local-dir local cp -r local/tools path/to/webserver Some of the known issues are: * Containers are not yet supported * There is a lack of mongo tools at the moment so any functionality depending on those is not available(for example backups) * There is no way to currently specify a proxy or mirror for yum in the environment configuration. The values that you specific for apt packages will be used for yum packages as well. This limitation will be fixed as soon as possible. ### Storage (experimental) Juju now models storage, charms can request storage (volumes and filesystems), and you can specify constraints on how to satisfy those requests (which provider, what options, how large, how many). Initially, Juju supports native volumes for the EC2 (EBS) and OpenStack (Cinder), and MAAS providers. Juju also supports several cloud-independent storage providers: tmpfs, loop (loop devices), root filesystem. Future versions of Juju will extend this set with providers for Ceph, NFS, and others. The storage feature is experimental: it has some known caveats, and has not yet been battle hardened. Instructions on use and caveats are documented at https://jujucharms.com/docs/devel/wip-storage. ### Storage (experimental) MAAS Provider Support The MAAS provider now supports storage. Storage directives are used to select machines which have the requisite number and size of volumes available on the machine (usually physical volumes such as SSD or magnetic drives). Storage pools may be created to select volumes with specified tags. juju storage create pool maas-ssd maas tags=ssd The above creates a pool called maas-ssd and when used, will select volumes tagged in MAAS with the ssd tag. Tags may be a comma separated list. Then to deploy a charm: juju deploy mycharm --storage data=maas-ssd,50G The above deploys a charm to a MAAS machine with the data store mounted on a volume at least 50GiB in size with the tag ssd. It is also possible to specify the size of the root-disk using the root disk constraint. This works the same way as for the AWS provider juju deploy mysql --constraints root-disk=50G Storage directives and root disk constraints may be combined. juju deploy mysql --constraints root-disk=50G --storage data=maas-ssd,500G NOTE: the root disk support has only just landed in MAAS trunk. the Juju/MAAS storage support has been smoke tested using the NEC MAAS test lab. It needs much more extensive testing! NOTE: when using MAAS which does not support storage, if MAAS storage is requested, an error is returned and the node is cleaned up. The storage feature is experimental: it has some known caveats, and has not yet been battle hardened. Instructions on use and caveats are documented at https://jujucharms.com/docs/devel/wip-storage. ### Storage (experimental) Unit Placement It is now possible to deploy units with storage to existing machines. This applies when using storage that is dynamically created, such as EBS/Cinder volumes, loop devices, TMPFS, rootfs. It can't be used with machine volumes on MAAS, but can be used to deploy charms to an existing MAAS machine if a dynamic storage source is specified. eg. juju deploy charm --to 2 --storage data=loop,2G An Openstack deployment example: juju deploy charm --to 2 --storage data=cinder,2G ## Resolved issues * Golang.org/x/sys/windows requires go 1.4 Lp 1463439 * Erroneous juju user data on windows for juju version 1.23 Lp 1451626 * Cmd/juju/storage: add fails to dynamically add filesystem for storage Lp 1462146 * Worker/diskmanager sometimes goes into a restart loop due to failing to update state Lp 1461871 * Juju 1.24-beta6.1 unit commands in debug-hooks hang indefinitely Lp 1463117 Finally We encourage everyone to subscribe the mailing list at juju-...@lists.canonical.com, or join us on #juju-dev on freenode. -- 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
Juju 1.24-beta6 is ready for testing
# juju-core 1.24-beta6 A new development release of Juju, juju-core 1.24-beta6, is now available. This release replaces version 1.24-beta5. ## Getting Juju juju-core 1.24-beta6 is available for vivid and backported to earlier series in the following PPA: https://launchpad.net/~juju/+archive/devel Windows and OS X users will find installers at: https://launchpad.net/juju-core/+milestone/1.24-beta6 Development releases use the devel simple-streams. You must configure the `agent-stream` option in your environments.yaml to use the matching juju agents. Upgrading from stable releases to development releases is not supported. You can upgrade test environments to development releases to test new features and fixes, but it is not advised to upgrade production environments to 1.24-beta6. ## Notable Changes This releases addresses stability and performance issues. ## Resolved issues * Intermittent panic: rescanned document Lp 1449054 * `juju upgrade-juju --upload-tools` leaves local environment unusable Lp 1457728 * warning: log line attempted over max size - leadership related Lp 1457645 * Debug-log eof: invalid tag and panic seen in state server logs Lp 1461354 * Juju has conf files in /var/log/juju on instances Lp 1370896 * Juju restore fails with /var/lib/juju/agents: no such file or directory Lp 1431372 * Cannot destroy-environment with 'juju user add' .jenv file Lp 1403165 * Juju cannot create vivid containers Lp 1442308 * State: availability zone upgrade fails if containers are present Lp 1441478 * 1.23.2.1, mongo: document is larger than capped size Lp 1454891 * relation-set --file - doesn't seem to work Lp 1454678 * Maas provider doesn't know about failed deployment instance status Lp 1376246 * Juju status --utc does not display utc and is confused Lp 1459611 * Juju agent opens api when upgrade is pending Lp 1459912 * 'juju status' wall clock timestamps should display offset not tz abbrev Lp 1459616 * Harvest mode setting not used by container provisioner Lp 1459885 * Allow status-set/get to a service by its leader unit Lp 146 * Unit storage add should only accept count as constraint Lp 1461342 Finally We encourage everyone to subscribe the mailing list at juju-...@lists.canonical.com, or join us on #juju-dev on freenode. -- 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
Juju supported stable 1.22.5 is released
# juju-core 1.22.5 A new stable release of Juju, juju-core 1.22.5, is now available. This release replaces version 1.22.1. Juju 1.22.x is an older supported version of juju. The current Juju version is 1.23.3 ## Getting Juju juju-core 1.22.5 is available for vivid and backported to earlier series in the following PPA: https://launchpad.net/~juju/+archive/1.22 Windows and OS X users will find installers at: https://launchpad.net/juju-core/+milestone/1.22.5 ## Notable Changes This releases addresses stability and performance issues. ## Resolved issues * Transaction collection (txns) grows without bound Lp 1453785 * /var/spool/rsyslog grows without bound Lp 1453801 * Instancepoller compares wrong address list and always requests updated state addresses Lp 1454043 * Firewaller gets an exception if a machine is not provisioned Lp 1454599 * Jujud leaking file handles Lp 1454697 * Agents see too many open files errors after many failed api attempts Lp 1420057 * 1.20.x client cannot communicate with 1.22.x env Lp 1454829 * Intermittent panic: rescanned document Lp 1449054 * Harvest mode setting not used by container provisioner Lp 1459885 Finally We encourage everyone to subscribe the mailing list at juju-...@lists.canonical.com, or join us on #juju-dev on freenode. -- 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
Juju 1.22.4 is proposed for the supported 1.22 series
`# juju-core 1.22.4 A new proposed stable release of Juju, juju-core 1.22.4, is now available. This release may replace version 1.22.3 on Thursday June 04. Juju 1.22.x is an older supported version of juju. The current Juju version is 1.23.3 ## Getting Juju juju-core 1.22.4 is available for vivid and backported to earlier series in the following PPA: https://launchpad.net/~juju/+archive/proposed Windows and OS X users will find installers at: https://launchpad.net/juju-core/+milestone/1.22.4 Proposed releases use the proposed simple-streams. You must configure the `agent-stream` option in your environments.yaml to use the matching juju agents. ## Notable Changes This releases addresses stability and performance issues. ## Resolved issues * Transaction collection (txns) grows without bound Lp 1453785 * /var/spool/rsyslog grows without bound Lp 1453801 * Instancepoller compares wrong address list and always requests updated state addresses Lp 1454043 * Firewaller gets an exception if a machine is not provisioned Lp 1454599 * Jujud leaking file handles Lp 1454697 * Agents see too many open files errors after many failed api attempts Lp 1420057 * 1.20.x client cannot communicate with 1.22.x env Lp 1454829 Finally We encourage everyone to subscribe the mailing list at juju-...@lists.canonical.com, or join us on #juju-dev on freenode. -- 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
Juju 1.24-beta5 is available for testing
# juju-core 1.24-beta5 A new development release of Juju, juju-core 1.24-beta5, is now available. This release replaces version 1.24-beta4. ## Getting Juju juju-core 1.24-beta5 is available for vivid and backported to earlier series in the following PPA: https://launchpad.net/~juju/+archive/devel Windows and OS X users will find installers at: https://launchpad.net/juju-core/+milestone/1.24-beta5 Development releases use the devel simple-streams. You must configure the `agent-stream` option in your environments.yaml to use the matching juju agents. Upgrading from stable releases to development releases is not supported. You can upgrade test environments to development releases to test new features and fixes, but it is not advised to upgrade production environments to 1.24-beta5. ## Notable Changes This releases addresses stability and performance issues. ## Resolved issues * Lxc network.mtu setting not set consistently across hosts Lp 1442257 * Transaction collection (txns) grows without bound Lp 1453785 * Firewaller gets an exception if a machine is not provisioned Lp 1454599 * Jujud leaking file handles Lp 1454697 * Destroying a machine with a placed unit errors then destroys anyway. Lp 1455158 Finally We encourage everyone to subscribe the mailing list at juju-...@lists.canonical.com, or join us on #juju-dev on freenode. -- 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
Juju devel 1.24-beta4 is available for testing
# juju-core 1.24-beta4 A new development release of Juju, juju-core 1.24-beta4, is now available. This release replaces version 1.24-beta3. ## Getting Juju juju-core 1.24-beta4 is available for vivid and backported to earlier series in the following PPA: https://launchpad.net/~juju/+archive/devel Windows and OS X users will find installers at: https://launchpad.net/juju-core/+milestone/1.24-beta4 Development releases use the devel simple-streams. You must configure the `agent-stream` option in your environments.yaml to use the matching juju agents. Upgrading from stable releases to development releases is not supported. You can upgrade test environments to development releases to test new features and fixes, but it is not advised to upgrade production environments to 1.24-beta4. ## Notable Changes This releases addresses stability and performance issues. ## Resolved issues * Agents see too many open files errors after many failed api attempts Lp 1420057 * Container destruction doesn't mark ip addresses as dead Lp 1441206 * Debug-hooks not working with manually provisioned machines Lp 1429790 * Joyent machines get stuck in provisioning Lp 1446264 * Cannot process charms: finding charm revision info: cannot get metadata from the charm store: verification failed: no macaroon cookies in request Lp 1453238 * Juju log spams error juju.worker.diskmanager lsblk.go:111 error checking if sr0 is in use: open /dev/sr0: no medium found Lp 1454481 * Failed to retrieve the template to clone - 500 internal server error - error creating container juju-trusty-lxc-template - Lp 1454676 * 1.20.x client cannot communicate with 1.22.x env Lp 1454829 * Received disconnect from ...: 2: too many authentication failures for ubuntu Lp 1456315 Finally We encourage everyone to subscribe the mailing list at juju-...@lists.canonical.com, or join us on #juju-dev on freenode. -- 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
Juju stable 1.23.3 is released
# juju-core 1.23.3 A new stable stable release of Juju, juju-core 1.23.3, is now available. This release replaces version 1.23.2. ## Getting Juju juju-core 1.23.3 is available for vivid and backported to earlier series in the following PPA: https://launchpad.net/~juju/+archive/stable Windows and OS X users will find installers at: https://launchpad.net/juju-core/+milestone/1.23.3 ## Notable Changes This releases addresses stability and performance issues. ## Resolved issues * Broken db field ordering when upgrading to juju compiled with go 1.3+ Lp 1451674 * Log files are lost when agents are restarted under systemd Lp 1452113 * Jujud does not restart after upgrade-juju on systemd hosts Lp 1452511 * Environment variables are not propagated to jujud on vivid Lp 1449436 * Local charms are not added to storage on upgrade to 1.22.x Lp 1447853 * Jujud won't start if apt-get of juju-mongodb package fails Lp 1441904 * Upgrade from 1.18 to 1.23 fails: password for machine agent can't be set Lp 1451297 * Juju 1.23-beta4 introduces ssh key bug when used w/ dhx Lp 1444861 * Debug-hooks exit 1 , doesn't mark hook as failed Lp 1415176 * Unnecessary errors emitted during init system discovery Lp 1452114 -- 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
Juju devel 1.24-beta3 is ready for testing
# juju-core 1.24-beta3 A new development release of Juju, juju-core 1.24-beta3, is now available. This release replaces version 1.24-beta2. ## Getting Juju juju-core 1.24-beta3 is available for vivid and backported to earlier series in the following PPA: https://launchpad.net/~juju/+archive/devel Windows and OS X users will find installers at: https://launchpad.net/juju-core/+milestone/1.24-beta3 Development releases use the devel simple-streams. You must configure the `agent-stream` option in your environments.yaml to use the matching juju agents. Upgrading from stable releases to development releases is not supported. You can upgrade test environments to development releases to test new features and fixes, but it is not advised to upgrade production environments to 1.24-beta3. ## Notable Changes This releases addresses stability and performance issues. ## Resolved issues * Persist iptables rules / routes for addressable containers across host reboots Lp 1442012 * Deployer sometimes fails with a unit status not found error Lp 1451283 * Logs don't rotate Lp 1452285 * Collect-metric hook failure, metric batch uuid already exists Lp 1452487 * Juju machine service for windows creates incorrect tools symlinks Lp 1453280 * /var/spool/rsyslog grows without bound Lp 1453801 * Instancepoller compares wrong address list and always requests updated state addresses Lp 1454043 Finally We encourage everyone to subscribe the mailing list at juju-...@lists.canonical.com, or join us on #juju-dev on freenode. -- 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
Juju devel 1.24-beta2 is available to test
# juju-core 1.24-beta2 A new development release of Juju, juju-core 1.24-beta2, is now available. This release replaces version 1.24-beta1. ## Getting Juju juju-core 1.24-beta2 is available for vivid and backported to earlier series in the following PPA: https://launchpad.net/~juju/+archive/devel Windows and OS X users will find installers at: https://launchpad.net/juju-core/+milestone/1.24-beta2 Development releases use the devel simple-streams. You must configure the `agent-stream` option in your environments.yaml to use the matching juju agents. Upgrading from stable releases to development releases is not supported. You can upgrade test environments to development releases to test new features and fixes, but it is not advised to upgrade production environments to 1.24-beta2. ## Notable Changes This releases addresses stability and performance issues. ## Resolved issues * Juju upgrade-juju failed to configure mongodb replicasets Lp 1441913 * Provider/openstack: volumes are recorded with 0 size Lp 1450740 Finally We encourage everyone to subscribe the mailing list at juju-...@lists.canonical.com, or join us on #juju-dev on freenode. -- 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
Juju 1.23.3 is proposed for release
# juju-core 1.23.3 A new proposed stable release of Juju, juju-core 1.23.3, is now available. This release may replace version 1.23.2 on Thursday May 14. ## Getting Juju juju-core 1.23.3 is available for vivid and backported to earlier series in the following PPA: https://launchpad.net/~juju/+archive/proposed Windows and OS X users will find installers at: https://launchpad.net/juju-core/+milestone/1.23.3 Proposed releases use the proposed simple-streams. You must configure the `agent-stream` option in your environments.yaml to use the matching juju agents. ## Notable Changes This releases addresses stability and performance issues. ## Resolved issues * Broken db field ordering when upgrading to juju compiled with go 1.3+ Lp 1451674 * Log files are lost when agents are restarted under systemd Lp 1452113 * Jujud does not restart after upgrade-juju on systemd hosts Lp 1452511 * Environment variables are not propagated to jujud on vivid Lp 1449436 * Local charms are not added to storage on upgrade to 1.22.x Lp 1447853 * Jujud won't start if apt-get of juju-mongodb package fails Lp 1441904 * Upgrade from 1.18 to 1.23 fails: password for machine agent can't be set Lp 1451297 * Juju 1.23-beta4 introduces ssh key bug when used w/ dhx Lp 1444861 * Debug-hooks exit 1 , doesn't mark hook as failed Lp 1415176 * Unnecessary errors emitted during init system discovery Lp 1452114 Finally We encourage everyone to subscribe the mailing list at -- 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
Juju devel 1.24-beta1 is available
* Log files are lost when agents are restarted under systemd Lp 1452113 * Worker/uniter: charm does not install properly if storage isn't provisioned before uniter starts Lp 1452207 * Jujud does not restart after upgrade-juju on systemd hosts Lp 1452511 * Maas provider chokes on unexpected device labels Lp 1452725 * Juju 1.23-beta4 introduces ssh key bug when used w/ dhx Lp 1444861 * Retry-provisioning launches instances for containers; cannot retry containers at all Lp 1428439 * Debug-hooks exit 1 , doesn't mark hook as failed Lp 1415176 * Default storage constraints are not quite correct Lp 1452535 * Maas: implement root-disk constraint Lp 1212689 Finally We encourage everyone to subscribe the mailing list at juju-...@lists.canonical.com, or join us on #juju-dev on freenode. -- 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
[no subject]
* Log files are lost when agents are restarted under systemd Lp 1452113 * Worker/uniter: charm does not install properly if storage isn't provisioned before uniter starts Lp 1452207 * Jujud does not restart after upgrade-juju on systemd hosts Lp 1452511 * Maas provider chokes on unexpected device labels Lp 1452725 * Juju 1.23-beta4 introduces ssh key bug when used w/ dhx Lp 1444861 * Retry-provisioning launches instances for containers; cannot retry containers at all Lp 1428439 * Debug-hooks exit 1 , doesn't mark hook as failed Lp 1415176 * Default storage constraints are not quite correct Lp 1452535 * Maas: implement root-disk constraint Lp 1212689 Finally We encourage everyone to subscribe the mailing list at juju-...@lists.canonical.com, or join us on #juju-dev on freenode. -- 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
Juju 1.24-alpha1 is released for testing
for agent initialization to finish 01 May 2015 17:33:20 EST agent allocating 01 May 2015 17:36:37 EST agent executingrunning install hook 01 May 2015 17:36:37 EST workload maintenance installing charm software 01 May 2015 17:36:38 EST workload maintenance installing dependencies 01 May 2015 17:39:11 EST workload maintenance installing components 01 May 2015 17:39:18 EST agent executingrunning leader-elected hook 01 May 2015 17:39:18 EST agent executingrunning config-changed hook 01 May 2015 17:39:19 EST workload maintenance configuring nginx 01 May 2015 17:39:34 EST workload maintenance restarting services 01 May 2015 17:39:38 EST workload blocked Waiting for database 01 May 2015 17:39:39 EST agent executingrunning start hook 01 May 2015 17:39:44 EST agent idle ### storage (experimental) Juju now models storage, charms can request storage (volumes and filesystems), and you can specify constraints on how to satisfy those requests (which provider, what options, how large, how many). Initially, Juju supports native volumes for the EC2 (EBS) and OpenStack (Cinder) providers. Juju also supports several cloud-independent storage providers: tmpfs, loop (loop devices), root filesystem. Future versions of Juju will extend this set with providers for Ceph, NFS, and others. The storage feature is experimental: it has some known caveats, and has not yet been battle hardened. Instructions on use and caveats are documented at https://jujucharms.com/docs/devel/wip-storage. ## Resolved issues * Deploying into kvm with local provider, hostnames are not unique Lp 1326091 * Juju status complains config has no uuid when no .jenv is present Lp 1436925 * Agent panic on maas network with uppercase characters Lp 1446608 * Debug-log spammed with leader-election messages Lp 1437015 * Eu-central-1 aws region v4 signing required and not supported Lp 1447841 * Environment variables are not propagated to jujud on vivid Lp 1449436 * Rsyslog-gnutls is not installed when enable-os-refresh-update is false Lp 1424892 * Juju stop responding after juju-upgrade Lp 1438489 * Jujud won't start if apt-get of juju-mongodb package fails Lp 1441904 * Juju cli compatibility option Lp 1450701 * Upgrade from 1.18 to 1.23 fails: password for machine agent can't be set Lp 1451297 Finally We encourage everyone to subscribe the mailing list at juju-...@lists.canonical.com, or join us on #juju-dev on freenode. -- 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
Juju stable 1.23.2 is released
1424069 * Juju status --format=tabular Lp 1424590 * Ec2 provider unaware of c3 types in sa-east-1 Lp 1427840 * Ec2 eu-central-1 region not in provider Lp 1428117 * Ec2 provider does not include c4 instance family Lp 1428119 * Allwatcher does not remove last closed port for a unit, last removed service config Lp 1428430 * Make kvm containers addressable (esp. on maas) Lp 1431130 * Fix container addressability issues with cloud-init, precise, when lxc-clone is true Lp 1431134 * Dhcp's option interface-mtu 9000 is being ignored on bridge interface br0 Lp 1403955 * Juju-1.23beta3 breaks glance - mysql relation when glance is hosted in a container Lp 1441811 * Juju ensure-availability should be able to target existing machines Lp 1394755 * Juju 1.23b4 vivid panic: runtime error: invalid memory address or nil pointer dereference Lp 1443541 * 1.23-beta4 sporadically fails autotests Lp 1443440 * 1.23.1: bootstrap failure, vivid, local provider Lp 1447446 * Hooks don't fire after upgrade 1.23.0 Lp 1447846 Finally We encourage everyone to subscribe the mailing list at juju-...@lists.canonical.com, or join us on #juju-dev on freenode. -- 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
Juju 1.23.1 is proposed for stable release
# juju-core 1.23.1 A new proposed stable release of Juju, juju-core 1.23.1, is now available. This release may replace version 1.23.0 on Thursday April 23. ## Getting Juju juju-core 1.23.1 is available for vivid and backported to earlier series in the following PPA: https://launchpad.net/~juju/+archive/proposed Windows and OS X users will find installers at: https://launchpad.net/juju-core/+milestone/1.23.1 Proposed releases use the proposed simple-streams. You must configure the `agent-stream` option in your environments.yaml to use the matching juju agents. ## Notable Changes since 1.23.0 ### Experimental: Addressable LXC Containers and KVM Instances on AWS and MAAS The Juju AWS and MAAS providers now support starting LXC containers. The MAAS providers also supports networking on KVM. Containers and Virtual Machines will be given statically allocated private IP addresses from the same subnet as their host machine. For example on MAAS you can now: juju deploy wordpress --to lxc:0 juju add-unit mysql --to kvm:1 This experimental feature can be enabled when the environment is bootstrapped like so: JUJU_DEV_FEATURE_FLAGS=address-allocation juju bootstrap These two units can now talk directly on the private subnet. ## Resolved issues * Addressable containers cannot resolve non-fqdn in maas Lp 1445063 * Vivid bootstrap and destroy-environment intermittently fails Lp 1446662 Finally We encourage everyone to subscribe the mailing list at juju-...@lists.canonical.com, or join us on #juju-dev on freenode. -- 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
1.24-alpha1 (AKA master) has not passed in 36 days
1.24-alpha1 has failed for a few reasons over the last 36 days. There isn't a single revision of 1.24-alpha1 that has passed. There is nothing we could release if we wanted too. Many of the issues pertain to ppc64el and ggcgo, and Martin has proposed some test fixes that will improve the chances of success. There is one regression that Core needs to fix. The 8 deployer and quickstart tests failed at the start of this month. The tests use either the landscape-scalable bundle or a trivial bundle with containers. https://bugs.launchpad.net/juju-core/+bug/1441826 -- 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
Juju 1.23.0 is proposed for release
default logging leaks credentials Lp 1423272 * Juju resolve doesn't recognize error state Lp 1424069 * Juju status --format=tabular Lp 1424590 * Ec2 provider unaware of c3 types in sa-east-1 Lp 1427840 * Ec2 eu-central-1 region not in provider Lp 1428117 * Ec2 provider does not include c4 instance family Lp 1428119 * Allwatcher does not remove last closed port for a unit, last removed service config Lp 1428430 * Make kvm containers addressable (esp. on maas) Lp 1431130 * Fix container addressability issues with cloud-init, precise, when lxc-clone is true Lp 1431134 * Dhcp's option interface-mtu 9000 is being ignored on bridge interface br0 Lp 1403955 * Juju-1.23beta3 breaks glance - mysql relation when glance is hosted in a container Lp 1441811 * Juju ensure-availability should be able to target existing machines Lp 1394755 * Juju 1.23b4 vivid panic: runtime error: invalid memory address or nil pointer dereference Lp 1443541 * 1.23-beta4 sporadically fails autotests Lp 1443440 Finally We encourage everyone to subscribe the mailing list at juju-...@lists.canonical.com, or join us on #juju-dev on freenode. -- 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
Juju devel 1.23-beta3 is release
# juju-core 1.23-beta3 A new development release of Juju, juju-core 1.23-beta3, is now available. This release replaces version 1.23-beta2. ## Getting Juju juju-core 1.23-beta3 is available for utopic and backported to earlier series in the following PPA: https://launchpad.net/~juju/+archive/devel Windows and OS X users will find installers at: https://launchpad.net/juju-core/+milestone/1.23-beta3 Development releases use the devel simple-streams. You must configure the `agent-stream` option in your environments.yaml to use the matching juju agents. Upgrading from stable releases to development releases is not supported. You can upgrade test environments to development releases to test new features and fixes, but it is not advised to upgrade production environments to 1.23-beta3. ## Notable Changes This releases addresses stability and performance issues. ## Resolved issues * Aws v4 signing does not work Lp 1439761 * Max_args is reached when calling relation-set Lp 1437366 * Gce: bootstrap instance has no network rule for api Lp 1436191 * Gce provider config should support extracting auth info from json file Lp 1436390 * Gce provider should stop using deprecated zone europe-west1-a Lp 1436655 * Can't deploy local charm in non-server environment Lp 1435152 * Juju backup/restore is upstart-specific Lp 1436988 * Apt-http-proxy being reset to bridge address Lp 1437296 * 1.23b2 fails to get ip from maas for containers, falls back to lxcbr0 Lp 1437038 * Juju 1.23 doesn't release ip addresses for containers Lp 1438168 * Containers stuck allocating, interface not up Lp 1438683 * Use of /tmp/discover_init_system.sh is a security vulnerability. Lp 1438748 * Ip address life field upgrade step and addresser worker don't play well together Lp 1438820 * Gce provider often can't find its own instances Lp 1437220 * Error in logs: environment does not support networking Lp 1439364 * Gce low-level removeinstances fails if firewalls are not found Lp 1439398 Finally We encourage everyone to subscribe the mailing list at juju-...@lists.canonical.com, or join us on #juju-dev on freenode. -- 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
Juju devel 1.23-beta2 is released
# juju-core 1.23-beta2 A new development release of Juju, juju-core 1.23-beta2, is now available. This release replaces 1.23-beta1. ## Getting Juju juju-core 1.23-beta2 is available for utopic and backported to earlier series in the following PPA: https://launchpad.net/~juju/+archive/devel Windows and OS X users will find installers at: https://launchpad.net/juju-core/+milestone/1.23-beta2 Development releases use the 'devel' simple-streams. You must configure the 'agent-stream' option in your environments.yaml to use the matching juju agents. agent-stream: devel Upgrading from stable releases to development releases is not supported. You can upgrade test environments to development releases to test new features and fixes, but it is not advised to upgrade production environments to 1.23-beta2. ## Notable Changes * Google Cloud Compute (GCE) * Service Leader Elections ### Google Cloud Compute (GCE) You must specify 'region' in your environments.yaml file. For example: region: us-central1 If you extracted the 'private-key' by hand from the GCE project json, change \u003d to =. You should not use the europe-west1-a availability zone. It has been deprecated and will be shut down on March 29, 2015. See https://cloud.google.com/compute/docs/release-notes#october152014. Juju gets a list of availability zones at run-time through the GCE API, so after that date it will not be a zone you may select anyway. ### Service Leader Elections Services running in an environment bootstrapped with the leader-election feature flag now have access to three new hook tools: is-leader - returns true only if the executing unit is guaranteed service leadership for the next 30s leader-get - as relation-get; accessible only within the service leader-set - as relation-set; will fail if not executed on leader ...and two new hooks: leader-elected - runs when the unit takes service leadership leader-settings-changed - runs when another unit runs leader-set When a unit starts up, it will always run either leader-elected or leader-settings-changed as soon as possible, delaying only doing so only to run the install hook; complete any queued or in-flight operation; or resolve a hook or upgrade error. You can enable the leader-election feature flag in a new env by bootstrapping with 'JUJU_DEV_FEATURE_FLAGS=leader-election' defined. JUJU_DEV_FEATURE_FLAGS=leader-election juju bootstrap ## Resolved issues * Juju-br0 is not configured correctly on maas machines without ethx interfaces Lp 1423372 * Juju cannot deploy when distro-info-data gets a new series Lp 1427879 * Juju backup fails when journal files are present Lp 1423936 Finally We encourage everyone to subscribe the mailing list at juju-...@lists.canonical.com, or join us on #juju-dev on freenode. -- 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
Re: GCE provider
On Wed, Mar 25, 2015 at 3:04 AM, Andrew Wilkins andrew.wilk...@canonical.com wrote: Hey folks, I just signed up for a GCE trial, and tested out the provider on master. Found a couple of issues. I've filed https://bugs.launchpad.net/juju-core/+bug/1436191. I suspect the same issue would exist on 1.23, but haven't tested. I haven't set the status/importance, because I don't know what the importance is (there's no CI or docs?), and I'd like for someone to confirm the bug. I just got CI credentials yesterday evening. As CI is using a project shared by several Canonical staff, it isn't clear to me if I should be creating new client ids or how to generate keys and not interfere with other people. Contrary to text generated by init, 'region' is required. Second, a UX thing. It was mostly clear how to generate keys, but it wasn't super clear what format to put them into environments.yaml. Obviously this'll be documented, but I think it'd be nice if in environments.yaml we could just specify the location of the JSON file that GCE spits out, and have Juju extract the info it needs, like we do with certs and SSH keys. I assumed I could use authorized-keys. -- 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
Juju stable 1.22.0 is released
is not supported. Local provider relies on LXC
or KVM and it deploys a state-server to the host, which is
not supported on Windows.
* Debug hooks are not yet supported yet. The current implementation
requires SSH and tmux to work, which is very platform specific. This
will be implemented for Windows soon.
### New annotations client includes charms and bulk calls
The new api.annotations.client supports annotating charms, the
environment, machines, services, and units. It supports bulk calls. The
old api.client annotation functions are deprecated.
The SET annotations call takes this form:
{
Type: Annotations,
Request: Set,
Params: {
Annotations: {{
EntityTag: a, Annotations: pairs1
},{
EntityTag: b, Annotations: pairs2
}}
}
The corresponding GET annotations call takes this form:
{
Type: Annotations,
Request: Get,
Params: {
Entities: {
{Entity {Tag: a}},
{Entity {Tag: b},
}
}
}
The GET response looks like this:
{
Results: {
{EntityTag: a, Annotations: pairs1, Error: nil},
{EntityTag: b, Annotations: pairs2, Error: nil},
}
}
### Juju upgrade robustness
During Juju upgrades (the 'upgrade-juju' command), steps specific to
Juju state-servers are now run before other upgrade steps. Database
migrations on the state-server are completed before machine updates and
updates of the Juju agents on deployed units.
### Multi-environment infrastructure
Juju will soon be able to support multiple environments managed by a
single state server (or state server cluster). Although this is not yet
visible, version 1.22 includes much of the infrastructure changes for
multi-environment support.
## Resolved issues
* Interface mtu management across maas/juju
Lp 1355813
* State server certificate has empty san list
Lp 1397909
* Api server restarts soon after state server comes up
Lp 1403721
* Cmdline: implement juju environment jenv
Lp 1409784
* Juju should wait until a node's status is 'deployed' to attempt
ssh'ing into it
Lp 1394680
* Lock contention running apt in bootstrap
Lp 1384259
* Juju status --format summary panics with unresolvable ips
Lp 1410320
* Machine hasvote/wantsvote should be included in allwatcher deltas
Lp 1402965
* Open-stack provider breaks swift with standard config
Lp 1312217
* 'juju switch' should not require an entry in environments.yaml
Lp 1334768
* Provider/maas: stopinstances may fail if nodes are removed out of
band
Lp 1319016
* Unit (anycharm) is not assigned to a machine when deploying with
juju 1.22-beta5
Lp 1430049
Finally
We encourage everyone to subscribe the mailing list at
juju-...@lists.canonical.com, or join us on #juju-dev on freenode.
--
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
1.23-beta1 needs features for release notes.
Our release notes document is looking sparse. Thank you Anastasia for keeping me posted. https://docs.google.com/a/canonical.com/document/d/1V6AU2mEbTOXQygsn-9eZg-DHjxcVpMylyq017KS78mU/edit I was expecting these topics: juju charms list MESS (Shared State Server ??) GCE Provider Systemd Support Leader Elections Actions Container Addressability on AWS and MAAS Charm Annotations HA Improvements - HA using Containers You don't need to provide a final draft of the new features and notable changes. Just get a draft into this document so that we can collectively bring this document to a final state -- 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
1.23 is branched and ready for your stable fixes
We branch juju master at commit 5b193d8 to create 1.23 https://github.com/juju/juju/commits/1.23 http://reports.vapour.ws/releases/2441 Master was one commit ahead of the blessed commit. Dimiter will backport that change to 1.23. If you have a fix for 1.23, please merge into 1.23 first, them merge into master. -- 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
juju 1.22.0 is proposed for release
, and restore state backups. The new backup
features are also available using the API endpoints too.
You can create a backup like this:
juju backups create
Backups are kept on the state-server by default, but you can use the
'download' and 'upload' subcommands to move backups between locations.
juju backups download id
juju backups upload filename
You can list the backups and see info about a specific backup using
these subcommands:
juju backups list
juju backups info id
You can remove unwanted backups like this:
juju backups remove id
The juju 'restore' command is unchanged. You can learn more about
backups by reading the details of 'juju help backups'.
### The instance availability zone is exposed to charms
Charms can query the 'JUJU_AVAILABILITY_ZONE' environmental variable to
learn the instance's availability zone. Not all clouds/providers support
availability zones, but this information is available when the charm is
deployed in EC2 and HP Cloud for example.
### Relaxed checked for container scoped relations
Container scoped relations are now allowed as long a there is at least
one subordinate service involved. Previously there had to be exactly one
subordinate service in the relation.
### Static internal route for Joyent instances
When running in Joyent, Juju creates a static route to ensure that it is
always possible for instance to communicate over the internal network
interface.
### New annotations client includes charms and bulk calls
The new api.annotations.client supports annotating charms, the
environment, machines, services, and units. It supports bulk calls. The
old api.client annotation functions are deprecated.
The SET annotations call takes this form:
{
Type: Annotations,
Request: Set,
Params: {
Annotations: {{
EntityTag: a, Annotations: pairs1
},{
EntityTag: b, Annotations: pairs2
}}
}
The corresponding GET annotations call takes this form:
{
Type: Annotations,
Request: Get,
Params: {
Entities: {
{Entity {Tag: a}},
{Entity {Tag: b},
}
}
}
The GET response looks like this:
{
Results: {
{EntityTag: a, Annotations: pairs1, Error: nil},
{EntityTag: b, Annotations: pairs2, Error: nil},
}
}
### Juju upgrade robustness
During Juju upgrades (the 'upgrade-juju' command), steps specific to
Juju state-servers are now run before other upgrade steps. Database
migrations on the state-server are completed before machine updates and
updates of the Juju agents on deployed units.
### Multi-environment infrastructure
Juju will soon be able to support multiple environments managed by a
single state server (or state server cluster). Although this is not yet
visible, version 1.22 includes much of the infrastructure changes for
multi-environment support.
## Resolved issues
* Interface mtu management across maas/juju
Lp 1355813
* State server certificate has empty san list
Lp 1397909
* Api server restarts soon after state server comes up
Lp 1403721
* Cmdline: implement juju environment jenv
Lp 1409784
* Juju should wait until a node's status is 'deployed' to attempt
ssh'ing into it
Lp 1394680
* Lock contention running apt in bootstrap
Lp 1384259
* Juju status --format summary panics with unresolvable ips
Lp 1410320
* Machine hasvote/wantsvote should be included in allwatcher deltas
Lp 1402965
* Open-stack provider breaks swift with standard config
Lp 1312217
* 'juju switch' should not require an entry in environments.yaml
Lp 1334768
* Provider/maas: stopinstances may fail if nodes are removed out of
band
Lp 1319016
* Unit (anycharm) is not assigned to a machine when deploying with
juju 1.22-beta5
Lp 1430049
Finally
We encourage everyone to subscribe the mailing list at
juju-...@lists.canonical.com, or join us on #juju-dev on freenode.
--
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
Re: Trivial bugs hurting progress
On Wed, Mar 4, 2015 at 8:44 AM, Martin Packman martin.pack...@canonical.com wrote: On 04/03/2015, Andrew Wilkins andrew.wilk...@canonical.com wrote: Curtis and I have talked about also doing a ppc64 test run as part of the gating job, that gets us the map ordering stuff as a newer go would, and other gccgo quirks covered as well. We don't want to bump the compiler version yet I think, as we want to be able to build with the trusty toolchain still, and not accidentally let in regressions by depending on newer gos. I assume Core developers are like myself. I have run the test suite just like the lander. I know a failure to merge is probably a bad test. As CI is running more compilers, series, and archs, We could prevent regressions in master by using lesser combination that must pass. We could: - catch and fix map order bugs - skip tests that wont pass on an arch/compiler combinations - discover and fix real arch and series issues without ever breaking the build, never blocking other engineers from merging. We cannot achieve my ideal combination of precise, gcc-4.9+patches, and ppc64el or i386. Precise doesn't work with ppc64el, and it is hard to get a run 386 test quickly. -- 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
Re: Trivial bugs hurting progress
On Wed, Mar 4, 2015 at 1:05 AM, Andrew Wilkins andrew.wilk...@canonical.com wrote: The bot is currently running (I think) Go 1.2. I'm running 1.4, Ian's running 1.3, and I'm sure Dave's running tip ;) Go 1.3+ made map iteration less deterministic, so these sorts of bugs are much more likely to occur after 1.2. It'd be good to either bump the compiler version to something more recent, unless we want to gate things on multiple compilers (maybe gc and gccgo, seeing as we currently use both). While we add our golang archive to all the slaves to ensure golang 1.2.1 is available, apt prefers to use the latest version. On Vivid, that is golang 1.3, and it very erratic success rate is probably because of tests aren't ready for a newish golang. Fixing the test suite will give allow us to make the vivid unit tests voting. Our test runner script accepts a PPA option. We have added newer golang and mongos to our experimental PPA, then setup a test to run with it to prove the Juju was ready for the newer versions. We can do this again. -- 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
Re: juju devel 1.22-beta4 is available for testing.
Could caching be an issue? On Fri, Feb 27, 2015 at 1:17 PM, Ryan Beisner ryan.beis...@canonical.com wrote: Ditto, also seeing that. On Fri, Feb 27, 2015 at 11:16 AM, Jason Hobbs jason.ho...@canonical.com wrote: ... Thanks,https://streams.canonical.com/juju/tools/streams/v1/com.ubuntu.juju:devel:tools.sjson or https://streams.canonical.com/juju/tools/streams/v1/com.ubuntu.juju-devel-tools.sjson (unsure which one gets used). Jason The index https://streams.canonical.com/juju/tools/streams/v1/index2.json points devel streams to http://streams.canonical.com/juju/tools/streams/v1/com.ubuntu.juju-devel-tools.json which does contain 28 1.22-beta4 agents which I can also see at http://streams.canonical.com/juju/tools/devel/ Index2 was updated on Thu, 26 Feb 2015 15:09:44 + and the devel product file on Thu, 26 Feb 2015 15:09:44 + ahh. The json was not signed! The signed json is from the previous release. We will look into this now. I will reply with an update soon. -- 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
Re: juju devel 1.22-beta4 is available for testing.
Index2 was updated on Thu, 26 Feb 2015 15:09:44 + and the devel product file on Thu, 26 Feb 2015 15:09:44 + ahh. The json was not signed! The signed json is from the previous release. We will look into this now. I will reply with an update soon. We queued the resigning. The time the changes will be republished isn't constant. I expect under 90 minutes. I will follow when the signed streams is confirmed to contain beta4 -- 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
juju 1.21.3 is proposed for release
# juju-core 1.21.3 A new stable release of Juju, juju-core 1.21.3, is proposed. This release may replace 1.21.1 on 2015-02-23 after a period of evaluation. ## Getting Juju juju-core 1.21.3 is available for utopic and backported to earlier series in the following PPA: https://launchpad.net/~juju/+archive/proposed The proposed packages in this archive use the proposed simple-streams. You must configure the 'agent-stream' option in your environments.yaml to use the matching juju agents. agent-stream: proposed ## Notable Changes This releases addresses stability and performance issues. ## Resolved issues * Juju agent using lxcbr0 address as apiaddress instead of juju-br0 breaks agents Lp 1416928 * Juju-quickstart: bad api server response: 'nonetype' object is not iterable Lp 1420403 * Error juju.worker runner.go:219 exited rsyslog: x509: certificate signed by unknown authority Lp 1417875 * Juju references old dns-name and ip addresses after restore. (failed juju ssh) Lp 1420316 * Ensure-availability fails with 'failed to find any voting machines' after backup/restore. Lp 1420306 Finally We encourage everyone to subscribe the mailing list at juju-...@lists.canonical.com, or join us on #juju-dev on freenode. -- 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
juju-core 1.21.2 is proposed for release
# juju-core 1.21.2 A new stable release of Juju, juju-core 1.21.2, is proposed. This release may replace 1.21.1 on 2015-02-12 after a period of evaluation. ## Getting Juju juju-core 1.21.2 is available for utopic and backported to earlier series in the following PPA: https://launchpad.net/~juju/+archive/proposed The proposed packages in this archive use the proposed simple-streams. You must configure the 'agent-stream' option in your environments.yaml to use the matching juju agents. agent-stream: proposed ## Notable Changes This releases addresses stability and performance issues. ## Resolved issues * Unable to override network-bridge if container type is kvm (local provider) Lp 1416134 * Src/bitbucket.org/kardianos/osext/license is wrong Lp 1416425 * Github.com/juju/syslog has contradicting licensing info Lp 1416433 * Some files refer to an include license file that is not included Lp 1416430 * Github.com/juju/utils has contradictory licence info Lp 1416436 * Juju restore no longer works with azure: error: cannot re-bootstrap environment: cannot determine state server instances: environment is not bootstrapped Lp 1417178 * Unit ports not populated by api megawatcher Lp 1418433 * Apt-proxy can be incorrectly set when the fallback from http-proxy is used Lp 1417617 Finally We encourage everyone to subscribe the mailing list at juju-...@lists.canonical.com, or join us on #juju-dev on freenode. -- 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
Re: NETWORKER ALERT: network worker causing problems in 1.21
On Thu, Feb 5, 2015 at 2:56 AM, Dimiter Naydenov dimiter.nayde...@canonical.com wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 However, the networker even in 1.21 is only causing issues when modifying /etc/network/interfaces inappropriately it *does not* decide what addresses a machine should use or modifies them in any way. That's done by the machiner. The networker just discovers the NICs on the machine and watches in-state NIC documents for changes. We can backport the fix that totally disables the networker to 1.22 and 1.21 as well, which will require a point release for 1.21. We are already committed to a 1.21.2. Lets get this backported to close several bugs. -- 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
Juju stable 1.21.1 is released
1309260 * Provider/azure: boilerplate uses inconsistently around values that require replacing Lp 1381289 * Juju set should give feedback that the value is already set Lp 1384622 * Logs are not logrotated Lp 1078213 * Juju db should use numactl when running mongo on multi-socket nodes Lp 1350337 * Juju status panic if state conn is shutdown || closing. Lp 1361316 * Container failed to start with lxc-clone-aufs=true Lp 1364939 * No defined 'state-servers' on environment file after bootstrap, works after run 'juju status' Lp 1370149 * Juju add-unit --to non-existing-machine fails too late, leaving unit unassigned Lp 1384732 * Ec2 says agent-state-info: 'cannot run instances: no default subnet for availability zone: ''us-east-1e''. (invalidinput)' Lp 1388860 * Provider/ec2: try alternative az on insufficientinstancecapacity error Lp 1389037 * Provider should test and verify credentials as first operation before bootstrap Lp 1362072 * Non subordinate container scoped relations broken Lp 1382751 * --debug dumps sensitive information to terminal Lp 1289038 * Juju destroy-environment could fail on MaaS with disk erasing enabled, or manually released nodes Lp 1381619 * Unit-get public-address on ec2 returns split horizon dns Lp 1308374 * Juju tries to use lxcbr0 when local provider is configured with kvm containers Lp 1307677 * Add juju_machine_id to the hooks environment Lp 1359714 * Openstack provider, instance-state doesn't change on instance shutdown Lp 1382709 * Config-get error inside config-changed: settings not found Lp 1301996 * Open-stack provider breaks swift with standard config Lp 1312217 Finally We encourage everyone to subscribe the mailing list at juju-...@lists.canonical.com, or join us on #juju-dev on freenode. -- 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
Juju 1.21.1 is proposed for release.
# juju-core 1.21.1 A new proposed stable release of Juju, juju-core 1.21.1, is now available. This release may replace 1.20.14 on Thursday January 29 after a period of evaluation. ## Getting Juju juju-core 1.21.1 is available for utopic and backported to earlier series in the following PPA: https://launchpad.net/~juju/+archive/proposed The proposed packages in this archive use the proposed simple-streams. You must configure the 'agent-stream' option in your environments.yaml to use the matching juju agents. agent-stream: proposed ## Notable Changes This releases addresses stability and performance issues. ## Resolved issues * Osx versionpanic: osversion reported an error: unknown series Lp 1414800 Finally We encourage everyone to subscribe the mailing list at juju-...@lists.canonical.com, or join us on #juju-dev on freenode. -- 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
juju devel 1.22-beta1 is released
delete
--help' for more details.
### Juju state backup improvements
The backup CLI plugin is replaced by the native 'backups' command. The
command can create, manage, and restore state backups. The new backup
features are also available using the API endpoints too.
You can create a backup like this:
juju backups create
Backups are kept on the state-server by default, but you can use the
'download' and 'upload' subcommands to move backups between locations.
juju backups download id
juju backups upload filename
You can list the backups and see info about a specific backup using
these subcommands:
juju backups list
juju backups info id
You can remove unwanted backups like this:
juju backups remove id
The juju 'restore' command is unchanged. You can learn more about
backups by reading the details of 'juju help backups'.
### The instance availability zone is exposed to charms
Charms can query the 'JUJU_AVAILABILITY_ZONE' environmental variable to
learn the instance's availability zone. Not all clouds/providers support
availability zones, but this information is available when the charm is
deployed in EC2 and HP Cloud for example.
### Relaxed checked for container scoped relations
Container scoped relations are now allowed as long a there is at least
one subordinate service involved. Previously there had to be exactly one
subordinate service in the relation.
### Static internal route for Joyent instances
When running in Joyent, Juju creates a static route to ensure that it is
always possible for instance to communicate over the internal network
interface.
### New annotations client includes charms and bulk calls
The new api.annotations.client supports annotating charms, the
environment, machines, services, and units. It supports bulk calls. The
old api.client annotation functions are deprecated.
The SET annotations call takes this form:
{
Type: Annotations,
Request: Set,
Params: {
Annotations: {{
EntityTag: a, Annotations: pairs1
},{
EntityTag: b, Annotations: pairs2
}}
}
The corresponding GET annotations call takes this form:
{
Type: Annotations,
Request: Get,
Params: {
Entities: {
{Entity {Tag: a}},
{Entity {Tag: b},
}
}
}
The GET response looks like this:
{
Results: {
{EntityTag: a, Annotations: pairs1, Error: nil},
{EntityTag: b, Annotations: pairs2, Error: nil},
}
}
### Juju upgrade robustness
During Juju upgrades (the 'upgrade-juju' command), steps specific to
Juju state-servers are now run before other upgrade steps. Database
migrations on the state-server are completed before machine updates and
updates of the Juju agents on deployed units.
### Multi-environment infrastructure
Juju will soon be able to support multiple environments managed by a
single state server (or state server cluster). Although this is not yet
visible, version 1.22 includes much of the infrastructure changes for
multi-environment support.
## Resolved issues
* Interface mtu management across maas/juju
Lp 1355813
* State server certificate has empty san list
Lp 1397909
* Api server restarts soon after state server comes up
Lp 1403721
* Cmdline: implement juju environment jenv
Lp 1409784
* Juju should wait until a node's status is 'deployed' to attempt
ssh'ing into it
Lp 1394680
* Lock contention running apt in bootstrap
Lp 1384259
* Juju status --format summary panics with unresolvable ips
Lp 1410320
* Machine hasvote/wantsvote should be included in allwatcher deltas
Lp 1402965
* Open-stack provider breaks swift with standard config
Lp 1312217
* 'juju switch' should not require an entry in environments.yaml
Lp 1334768
* Provider/maas: stopinstances may fail if nodes are removed out of
band
Lp 1319016
Finally
We encourage everyone to subscribe the mailing list at
juju-...@lists.canonical.com, or join us on #juju-dev on freenode.
--
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
juju devel 1.21-rc1 is released
juju-core 1.21-rc1 A new development release of Juju, juju-core 1.21-rc1, is now available. This release replaces 1.21-beta5. Getting Juju juju-core 1.21-rc1 is available for utopic and backported to earlier series in the following PPA: https://launchpad.net/~juju/+archive/devel The devel packages in this archive use the devel simple-streams. You must configure the 'agent-stream' option in your environments.yaml to use the matching juju agents. agent-stream: devel Upgrading from stable releases to development releases is not supported. You can upgrade test environments to development releases to test new features and fixes, but it is not advised to upgrade production environments to 1.21-rc1. Notable Changes This releases addresses stability and performance issues. Resolved issues * Error upgrade in progress - juju functionality is limited Lp 1411502 Finally We encourage everyone to subscribe the mailing list at juju-...@lists.canonical.com, or join us on #juju-dev on freenode. -- 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
Re: Joyent networking issues
Thank you Menno. On Fri, Dec 12, 2014 at 12:01 AM, Menno Smits menno.sm...@canonical.com wrote: For the last day and a half I've been looking at this bug: https://bugs.launchpad.net/juju-core/+bug/1401130 There's a lot of detail attached to the ticket but the short story is that the Joyent cloud often allocates different internal networks to instances, meaning that they can't communicate. From what I can tell from relevant LP tickets, this has been a problem for a long time (perhaps always). It's very hit and miss - sometimes you get allocated 10 machines in a row that all end up with the same internal network, but more often than not it only takes 2 or 3 machine additions before running into one that can't talk to the others. Your analysis explains a lot about the the intermittent failures we have observed in Juju CI for months. ... Given that this is looking like a problem/feature at Joyent's end that needs clarification from them, may I suggest that this issue is no longer allowed to block CI? Speaking for users, there is a regression. We have extensively tested master (1.22), 1.21, and 1 20 this week in Joyent. Master always fails, where as 1.21 and 1.20 pass, and are more reliable than aws were we often see instances not available. Juju 1.22 and joyent just don't work (even for small deployments). We know that 1.22 must get the agent from the state-server, whereas 1.20 and 1.21 will get it from streams or a local container. After the machine agent is started, it is calling home. Maybe the network changes between the the time of cloud-init and starting the agent. Maybe it doesn't change fast enough and we get an intermittent failure. As the for extensive testing. We have unlimted resources in joyent, so Juju QA is using it test changes to industrial testing (repeatability). Using 1.22 built last week, and 1.21 and 1.20, we say high success rates, some times 100% for all jujus. We tested bundle deployments with 1.20.14 which gave us 100% success. We do see intermittent failures using 1.20 in the joyent cloud health check. so we know statistically, the problem does exists for every juju, but we are seeing 100% failure for master tip. The success rates were better for master last week, and the rates for 1.20 and 1.21 are great for all weeks. -- 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
Re: Joyent networking issues
On Fri, Dec 12, 2014 at 2:17 PM, John Meinel j...@arbash-meinel.com wrote: Is that after Dimiter's patch to disable Networker on Joyent ? yes. -- 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
