[Bug 1545913] Re: [FFe] juju-core 2.0

The proposed packaging updates are now available in Adam's PPA: This includes: * Switch from golang-go.net-dev to golang-x-net-dev as mentioned by ~jdstrand * Use of Suggests to keep Juju 1.X tools around through upgrade from

[Bug 1545913] Re: [FFe] juju-core 2.0

These updates were presented to slangasek and the point of the making juju1 the default is the one point left that we requested feedback on. Feedback from slangasek is that if we're not prepared to make juju1 the default then: "upon upgrade, juju == juju2; if you want juju1, run juju-1.$fwibble

[Bug 1545913] Re: [FFe] juju-core 2.0

- adding a comment to the juju 2.0 FFe that clarifies that the juju client is built and runs on all architectures, including 32bit. Comment added under the heading Mongodb to this effect since that's where the confusion derived from. - document the process for avoiding a late stage FFe and

[Bug 1545913] Re: [FFe] juju-core 2.0

** Description changed: The juju team is requesting an FFE for juju-core. Juju2 represents API changes and new features and bugfixes for juju. We are NOT requesting a place on any image for xenial. This FFE is intended to cover the acceptance of the updated juju-core package, as well as

[Bug 1545913] Re: [FFe] juju-core 2.0

** Description changed: The juju team is requesting an FFE for juju-core. Juju2 represents API changes and new features and bugfixes for juju. We are NOT requesting a place on any image for xenial. This FFE is intended to cover the acceptance of the updated juju-core package, as well as

[Bug 1545913] Re: [FFe] juju-core 2.0

Add item - document the process for avoiding a late stage FFe and package upload for 16.10 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju-core in Ubuntu. https://bugs.launchpad.net/bugs/1545913 Title: [FFe] juju-core 2.0 To

[Bug 1545913] Re: [FFe] juju-core 2.0

In an IRC conversation with: stgraber, infinity, mgz We agreed that the outstanding issues are the following: - adding a comment to the juju 2.0 FFe that clarifies that the juju client is built and runs on all architectures, including 32bit. - move the juju binary metapackage suggest juju-1.25

[Bug 1545913] Re: [FFe] juju-core 2.0

I've edited the bug the clarify the juju-mongodb situation. There's a change to both tweak the version of mongodb and make the unit tests more reliable, which was held from landing for beta3 waiting on the package in ubuntu. It will be included in the rc. -- You received this bug notification

[Bug 1545913] Re: [FFe] juju-core 2.0

** Description changed: The juju team is requesting an FFE for juju-core. Juju2 represents API changes and new features and bugfixes for juju. We are NOT requesting a place on any image for xenial. This FFE is intended to cover the acceptance of the updated juju-core package, as well as

[Bug 1545913] Re: [FFe] juju-core 2.0

"The security team has requested changes to the current juju packaging with the ultimate goal of breaking out the embedded non-juju golang dependencies. As part of this FFE, the juju-core package depends upon all currently packaged golang depends that are already in the archive. The remaining

[Bug 1545913] Re: [FFe] juju-core 2.0

** Description changed: The juju team is requesting an FFE for juju-core. Juju2 represents API changes and new features and bugfixes for juju. We are NOT requesting a place on any image for xenial. This FFE is intended to cover the acceptance of the updated juju-core package, as well as

[Bug 1545913] Re: [FFe] juju-core 2.0

** Description changed: The juju team is requesting an FFE for juju-core. Juju2 represents API changes and new features and bugfixes for juju. We are NOT requesting a place on any image for xenial. This FFE is intended to cover the acceptance of the updated juju-core package, as well as

[Bug 1545913] Re: [FFe] juju-core 2.0

Adam has built the initial version desired for upload: https://launchpad.net/~adam-stokes/+archive/ubuntu/juju-pkg -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju-core in Ubuntu. https://bugs.launchpad.net/bugs/1545913 Title:

[Bug 1545913] Re: [FFe] juju-core 2.0

No, there is no KVM local provider in Juju 2.0. Product management has made the determination that the lxd tool provides the needed functionality for both the lxc and kvm use cases. lxd in Juju 2.0 will be the answer. -- You received this bug notification because you are a member of Ubuntu

[Bug 1545913] Re: [FFe] juju-core 2.0

xnox, there is this bug: https://bugs.launchpad.net/juju- core/+bug/1547665 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju-core in Ubuntu. https://bugs.launchpad.net/bugs/1545913 Title: [FFe] juju-core 2.0 To manage

[Bug 1545913] Re: [FFe] juju-core 2.0

local-kvm provider is not available in the beta, and is a regression compared with juju-core 1.25. Is there going to be a local kvm provider? (or e.g. libvirt provider on par with lxd provider) -- You received this bug notification because you are a member of Ubuntu Server Team, which is

[Bug 1545913] Re: [FFe] juju-core 2.0

Updated the description with the example upgrade testing using the test packages in the ppa. ** Description changed: The juju team is requesting an FFE for juju-core. Juju2 represents API changes and new features and bugfixes for juju. We are NOT requesting a place on any image for

[Bug 1545913] Re: [FFe] juju-core 2.0

** Description changed: - The Juju team is preparing for a 2.0-beta1 release in time for the - xenial feature freeze date (18-Feb), but not all features required for - 2.0 will be ready by that date. We believe we will have a complete and - stable Juju 2.0 by the time of the xenial release, but

[Bug 1545913] Re: [FFe] juju-core 2.0

Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: juju-core (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju-core in Ubuntu.

[Bug 1545913] Re: [FFe] juju-core 2.0

** Tags added: conjure -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju-core in Ubuntu. https://bugs.launchpad.net/bugs/1545913 Title: [FFe] juju-core 2.0 To manage notifications about this bug go to:

[Bug 1545913] Re: [FFe] juju-core 2.0

Also want to mention the openstack package as well. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju-core in Ubuntu. https://bugs.launchpad.net/bugs/1545913 Title: [FFe] juju-core 2.0 To manage notifications about this bug go

[Bug 1545913] Re: [FFe] juju-core 2.0

As part of our exception, we're blocking the inclusion of two other packages: https://bugs.launchpad.net/ubuntu/+bug/1561043 https://bugs.launchpad.net/ubuntu/+bug/1561037 As we update Juju around this exception those will be effected and will need to have some leeway in the process. -- You

[Bug 1545913] Re: [FFe] juju-core 2.0

** Changed in: juju-core (Ubuntu) Status: Confirmed => New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju-core in Ubuntu. https://bugs.launchpad.net/bugs/1545913 Title: [FFe] juju-core 2.0 To manage notifications about

[Bug 1545913] Re: [FFe] juju-core 2.0

Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: juju-core (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju-core in Ubuntu.

[Bug 1545913] Re: [FFe] juju-core 2.0

That's in favor of LXD. All LXC code from JuJu has been or is in the process of being rewritten to use LXD instead. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju-core in Ubuntu. https://bugs.launchpad.net/bugs/1545913 Title:

[Bug 1545913] Re: [FFe] juju-core 2.0

** Description changed: The Juju team is preparing for a 2.0-beta1 release in time for the xenial feature freeze date (18-Feb), but not all features required for 2.0 will be ready by that date. We believe we will have a complete and stable Juju 2.0 by the time of the xenial release, but