Re: Juju 2.0-beta12 ETA

There are no API changes planned for beta12, but if any do come up, they will be announced on the mailing lists. On Wed, Jul 6, 2016 at 8:59 PM, Marco Ceppi wrote: > On Wed, Jul 6, 2016 at 3:51 PM Cheryl Jennings < > cheryl.jenni...@canonical.com> wrote: > >> Hi Everyone

Juju 2.0-beta12 ETA

Hi Everyone, Due to the US holidays and with much of the team at core and networking sprints, we will be releasing 2.0-beta12 next week. There are currently 6 assigned critical bugs [0] that need to be addressed for the next beta. This next beta is targeted to replace the out of date beta7 curre

Re: Juju 2.0-beta9 ETA

Hi Everyone, Due to a critical bug [0] found in the daily PPA, the release of 2.0-beta9 will be delayed while we test the fix. We are aiming for a release tomorrow. Thanks! -Cheryl [0] https://bugs.launchpad.net/juju-core/+bug/1592210 On Fri, Jun 10, 2016 at 1:20 PM, Cheryl Jennings

Juju 2.0-beta9 ETA

The team has been busily working on 2.0-beta9 with an aim to address usability feedback and ensure that beta9 will be upgradeable to subsequent releases. Ensuring upgradeability has required a significant amount of work to finalize internal details, and the team needs a few extra days to make sure

Re: Unable to add machine that uses public/private key based authentication

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

Re: go test github.com/juju/juju/state takes > 10 minutes to run

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 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 minu

Re: Connecting to the controller database w/mongodb 3.2

The QA team is looking at adding the mongo client into the juju-mongodb3.2 package. In the meantime, I've been bootstrapping with a trusty controller if I need to be able to examine the db. On Fri, May 13, 2016 at 11:17 AM, Horacio Duran wrote: > so, for case 1) this link explains how to add th

Please run go test -race before pushing code

Hey everyone, There have been some new races showing up in the CI race detector test. As you're making your bug fixes, please make sure you run go test -race before pushing your code up for review to make sure you have not introduced new races. Thanks! -Cheryl -- Juju-dev mailing list Juju-dev@

Master is blocked - do not JFDI

Hey guys, In the transition to go 1.6 everywhere, we have found a number of failures in our unit tests on Windows and CentOS with go 1.6. We had been using go 1.2 in our unit tests for those platforms, but have decided to make the go 1.6 unit tests voting and eliminate the go 1.2 unit tests. Thi

Re: Command rename: create-model -> add-model

Copying juju list. On Tue, Apr 26, 2016 at 5:15 PM, Cheryl Jennings < cheryl.jenni...@canonical.com> wrote: > Hi Everyone, > > Just a heads up that I'm merging a PR to rename the create-model command > to add-model to be more consistent in our terminology. > > The

Command rename: create-model -> add-model

Hi Everyone, Just a heads up that I'm merging a PR to rename the create-model command to add-model to be more consistent in our terminology. The next 2.0 release will contain this rename, and those of you building from master will need to use add-model once the PR lands. Thanks! -Cheryl -- Juju

Master is blocked in preparation for 2.0-beta4

Hi Everyone, Master is currently blocked to allow us to get to a stable 2.0-beta4. While we are working towards that goal, please do not JFDI changes into master. We are aiming to have a release tomorrow or Wednesday, so this window should be short. Please let me know if you have questions or co

Re: Thunderbirds are Go 1.6

Thank you for all your work on this, Curtis! On Sun, Apr 10, 2016 at 11:55 AM, Curtis Hovey-Canonical < cur...@canonical.com> wrote: > 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. Juj

Re: Unable to kill-controller

Another relevant bug: https://bugs.launchpad.net/juju-core/+bug/1566426 Maybe kill-controller tries to destroy through the API, but has a time out if things get "stuck" where it will fall back to the provider. I was joking when I suggested yesterday in IRC that we should bring back --force for k

Re: Unable to kill-controller

Relevant bug: https://bugs.launchpad.net/juju-core/+bug/1553059 We should provide a way to clean up controllers without making the user manually edit juju's files. On Mon, Apr 4, 2016 at 7:05 AM, Nate Finch wrote: > This just happened to me, too. Kill-controller needs to work if at all > poss

Re: Go 1.6 is now in trusty-proposed

These intermittently failing unit tests are often due to unreliable unit tests, rather than problems in the code. As nice as it would be to not have to retry tests (particularly unit tests), I'd much rather we spend our precious resources on fixing bugs that are causing pain for our users. There

Re: Go 1.6 is now in trusty-proposed

t!) bugs. > > Put another way, flaky tests are indirectly causing pain for our users. > > > On 03/28/2016 10:24 AM, Cheryl Jennings wrote: > > These intermittently failing unit tests are often due to unreliable unit > tests, rather than problems in the code. As nice as it wo

Merge master for your feature branches

Hi everyone, The admin-controller-model branch which merged into master yesterday brought the new behavior of two models being created upon bootstrap - "admin" and "default". Significant changes were needed in CI to support this new behavior. You will need to merge master into your feature branc

Master is blocked in preparation for 2.0-beta3

Hi Everyone, Master is currently blocked to allow us to get to a stable 2.0-beta3. While we are working towards that goal, please do not JFDI changes into master. Please let me know if you have questions or concerns. Thanks! -Cheryl -- Juju-dev mailing list Juju-dev@lists.ubuntu.com Modify sett

Preparing for the next beta - CI runs on feature branches

Hey Everyone! The cutoff for the next beta is just around the corner (Monday, March 21)! In order to meet this cutoff, please pay attention to the CI reports [0] on your branches and address failures on your branch when they arise. To avoid wasting CI test time on branches with known errors, we w

Juju 2.0-beta2 update

The Juju Core team is working towards a stable release of 2.0-beta2, but will need to delay the release due to some issues that arose in the last two weeks. The outstanding issues are: [0] 1549545 - Bundle deploys fail at lxc-start when bridge br-eth1 is created Found in CI; proposed fix is being

Master is unblocked (for now)

Hi Everyone, Given the decision that we are releasing alpha2 next week instead of a separate alpha3, I have unblocked master so that people can get some changes in before the next alpha stabilization period. Please merge your bug fixes / blessed feature branches into master before 18:00 UTC on Mo

Juju 2.0-alpha2

Hi Everyone, In preparing for Juju 2.0-alpha2, CI caught a race condition exposed by some of the new feature code to support 2.0. Because of this, we are going to move 2.0-alpha2 out to next week to allow time to fix the race. Features that were targeted to 2.0-alpha3, planned for next week, will

API / command renames coming for 2.0-alpha2

Hi Everyone, There will soon be a feature branch landing that changes internal names, message strings and commands to use the new model / controller terminology. Significant CI changes were made to support this rename. Once this branch lands, you will need to merge master into your feature branc

Re: Build errors

Neale, make sure you check out the section on godeps. I've run into errors like yours before I ran that command. Thanks! -Cheryl On Mon, Feb 1, 2016 at 4:15 PM, Neale Ferguson wrote: > The “Getting Started” part of that document says that the: > go get -d -v github.com/juju/juju/... > comman

Master is unblocked

Hi Everyone, Yesterday we had a blessed CI run on master which we will be releasing as our 2.0-alpha1. The final touches will be put on the release notes and we will turn the crank to get an official release shortly. In the meantime, I've unblocked master. So, let the thundering herd of merges

Re: Juju 1.26-alpha3 moving to 2.0-alpha1

Hi Everyone, While we are still moving towards a 2.0 release, not all of the CLI / behavior changes that will occur in Juju 2.0 are ready for an alpha release. To allow consumers to test new functionality in a timely manner, we will be releasing a new development version called 1.26-alpha3. This

Re: Juju 1.26-alpha3 moving to 2.0-alpha1

> > > Is there a feature mapping to what's landing in each Alpha? > > We will be working on that list next week when the core team has their sprint. Once it is complete, I will send it out to the juju list. Thanks! -Cheryl -- Juju-dev mailing list Juju-dev@lists.ubuntu.com Modify settings or uns

Re: Feature Request: -about-to-depart hook

Rick Harding wrote: > Thank you Cheryl! > > On Mon, Nov 23, 2015, 6:33 PM Cheryl Jennings < > cheryl.jenni...@canonical.com> wrote: > >> This is already on my list. I'm still figuring out a good way to >> organize / record these in a publicly viewable place

Re: Feature Request: -about-to-depart hook

This is already on my list. I'm still figuring out a good way to organize / record these in a publicly viewable place. I'll send out a link once I get something together. (Hopefully tonight!) Thanks! -Cheryl On Nov 23, 2015 5:20 PM, "Rick Harding" wrote: > Thanks for the feedback. I think thi

Cut-off for 1.25.1 Release - This Thursday

Hi Everyone, The cut-off for changes going into 1.25.1 will be this Thursday, Nov 19th at 18:00 UTC. Any changes that aren't Fix Committed by then will be deferred to 1.25.2. We hope to have a 1.25.1 release next week, depending on test results. Please let me know if you have any questions. Tha