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

[Richard Harding]

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 instead"

The Juju team defers to the distro team in regards to Juju upgrades and
will move forward with this plan during updates and update the juju2
command such that if it detects you're a new juju2 user with existing
juju1 environments.yaml file we will direct you to the new command to
run as a helpful hint.

Please direct feedback on this decision to slangasek.

-- 
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:
https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1545913/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

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

[Richard Harding]

- 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 package upload for 
16.10

Added section to the FFe under the heading "Future release planning"


- move the juju binary metapackage suggest juju-1.25 so that upgrades will make 
sure that juju 1 stays available

This change is made and new builds are being done.


- make juju1 the higher update-alternatives priority.

We cannot make this change due to direction from product management. We
have filed this for record under
https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1564670.

We've also created the Juju bug to perform the update that outputs the 
mitigating messaging to help the user in the 2.0 Juju.
https://bugs.launchpad.net/juju-core/+bug/1564622


- trim the binary size of the juju package by reducing the duplication

See bug https://bugs.launchpad.net/juju-core/+bug/1564677 for the work
to perform this. This will be a goal of the next full release to perform
this action to reduce the Juju binary size.


- investigate the ability to perform stripping to reduce size

See bug https://bugs.launchpad.net/juju-core/+bug/1564662 for this work.
This will be a goal for the next full release to perform this action and
reduce the Juju binary size. However, we need time to validate that it
is 100% safe and we feel the risk is too high to push it through today.

-- 
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:
https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1545913/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1564670] Re: After upgrade Juju 1.X should still be the default

[Richard Harding]

See bug https://bugs.launchpad.net/juju-core/+bug/1564622 for the fix in
Juju to properly output the messaging to the user.

** Description changed:

  When upgrading to Xenial the new default Juju version is going to be
  2.0.
  
  Because 2.0 clients are not compatible with 1.X environments, this means
  existing environments will be inaccessible unless the 1.X client is
  switched to. The plan is to give a warning when creating Juju 2
  configuration for the first time, something along the lines of:
  
- $ sudo apt-get update
- $ juju status
- WARNING Creating new juju 2 configuration.
- Use `update-alternatives --config juju` to switch for 1.X environments.
- $ juju status
- ERROR Unable to connect to model "".
- Please check your credentials or use 'juju bootstrap' to create a new model.
+ Feedback suggests that we should correct this by having juju 1.X be the
+ higher priority in update alternatives.
  
- There has been some concern that this is still too confusing and 1.X
- should remain the default juju without explicit user intervention.
+ Product management has give feedback that the preference it to push
+ toward the direction of Juju 2 at all times. Since this process would
+ default to Juju 1 if a Juju 2 users installs Juju 1 for legacy reasons,
+ we are instead going to implement the following:
+ 
+ $ sudo apt-get update
+ $ juju status
+ WARNING Creating new juju 2 configuration.
+ Use `update-alternatives --config juju` to switch for 1.X environments.
+ $ juju status
+ ERROR Unable to connect to model "".
+ Please check your credentials or use 'juju bootstrap' to create a new 
model.

** Description changed:

  When upgrading to Xenial the new default Juju version is going to be
  2.0.
  
  Because 2.0 clients are not compatible with 1.X environments, this means
  existing environments will be inaccessible unless the 1.X client is
  switched to. The plan is to give a warning when creating Juju 2
  configuration for the first time, something along the lines of:
  
  Feedback suggests that we should correct this by having juju 1.X be the
  higher priority in update alternatives.
  
  Product management has give feedback that the preference it to push
  toward the direction of Juju 2 at all times. Since this process would
  default to Juju 1 if a Juju 2 users installs Juju 1 for legacy reasons,
  we are instead going to implement the following:
  
- $ sudo apt-get update
- $ juju status
- WARNING Creating new juju 2 configuration.
- Use `update-alternatives --config juju` to switch for 1.X environments.
- $ juju status
- ERROR Unable to connect to model "".
- Please check your credentials or use 'juju bootstrap' to create a new 
model.
+ $ sudo apt-get update
+ $ juju status
+ WARNING Creating new juju 2 configuration.
+ Use `update-alternatives --config juju` to switch 
+ for 1.X environments.
+ $ juju status
+ ERROR Unable to connect to model "".
+ Please check your credentials or use 'juju bootstrap' to 
+ create a new model.

** Description changed:

  When upgrading to Xenial the new default Juju version is going to be
  2.0.
  
  Because 2.0 clients are not compatible with 1.X environments, this means
  existing environments will be inaccessible unless the 1.X client is
  switched to. The plan is to give a warning when creating Juju 2
  configuration for the first time, something along the lines of:
  
  Feedback suggests that we should correct this by having juju 1.X be the
  higher priority in update alternatives.
  
  Product management has give feedback that the preference it to push
  toward the direction of Juju 2 at all times. Since this process would
  default to Juju 1 if a Juju 2 users installs Juju 1 for legacy reasons,
  we are instead going to implement the following:
  
  $ sudo apt-get update
- $ juju status
+ 
+ $ juju status
  WARNING Creating new juju 2 configuration.
- Use `update-alternatives --config juju` to switch 
- for 1.X environments.
- $ juju status
+ Use `update-alternatives --config juju` to switch
+ for 1.X environments.
+ 
+ $ juju status
  ERROR Unable to connect to model "".
- Please check your credentials or use 'juju bootstrap' to 
- create a new model.
+ Please check your credentials or use 'juju bootstrap' to
+ create a new model.

** Also affects: juju-core
   Importance: Undecided
   Status: New

** No longer affects: juju-core

-- 
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/1564670

Title:
  After upgrade Juju 1.X should still be the default

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1564670/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 

[Bug 1564670] Re: After upgrade Juju 1.X should still be the default

[Richard Harding]

See https://bugs.launchpad.net/juju-core/+bug/1564622 for the reasoning
of this path.

-- 
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/1564670

Title:
  After upgrade Juju 1.X should still be the default

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1564670/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1564662] Re: Juju binaries should be stripped

[Richard Harding]

This will be a target for the Juju team to update and verify that the
stripping of the binary is safe and passes all testing. This requires
building in some gating based on if the binary is golang vs gccgo.


** Also affects: juju-core
   Importance: Undecided
   Status: New

** Changed in: juju-core
   Status: New => Triaged

** Changed in: juju-core
   Importance: Undecided => High

** Changed in: juju-core
Milestone: None => 2.1.0

-- 
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/1564662

Title:
  Juju binaries should be stripped

To manage notifications about this bug go to:
https://bugs.launchpad.net/juju-core/+bug/1564662/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

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

[Richard Harding]

** 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 the new package
  juju-core-1.25, which is a new version of the existing juju-core package
  allowing the existing juju1 binary to be installed.
  
  Related FFes
  
  
  Required for Juju 2.0:
  
  juju-mongodb3.2: bug 1557852
  juju-mongodb2.6: bug 1557830
  juju-mongo-tools3.2: bug 1558336
  
  (see note below about mongodb for details)
  
  Required consumers:
  
  conjure: bug 1561037
  bigdata: bug 1561043
  openstack: Already in universe, dep wait on conjure -> juju 2.0
  charm-tools: bug 1546776
  
  User-Facing Features / Changes
  --
  * New Terminology
  * Command Name Changes
  * New Juju home directory
  * Multi-Model Support Active by Default
  * New Bootstrap and Cloud Management Experience
  * Native Support for Charm Bundles
  * Multi Series Charms
  * Improved Local Charm Deployment
  * LXC Local Provider No Longer Available
  * LXD Provider
  * LXD Containers
  * Microsoft Azure Resource Manager Provider
  * Bootstrap Constraints, Series
  * Juju Logging Improvements
  * Unit Agent Improvements
  * API Login with Macaroons
  * MAAS Spaces
  * Resources
  * Juju Status Improvements
  * Relation Get and Set Compatibility
  * Support for new AWS M4 Instance Types
  * Support for win10 and win2016
  
  The full list of changes can be found here: 
https://lists.ubuntu.com/archives/juju/2016-March/006922.html
  and in the final release notes.
  
  Timeline
  
  We have released 2 alphas, and 3 betas for juju2 so far, in addition 3 alpha 
builds of 1.26 which became 2.0.  All targeted 2.0 features are now 
implemented, and we anticipate releasing one release candidate before a final 
stable build. Juju missed uploading any versions of 2.0 to the archive itself,  
as well as the initial projected date of having beta1 in xenial before feature 
freeze. However, juju has been released regularly during the development cycle 
inside the juju ppa. You can see the details on the delivered features and 
milestones on https://launchpad.net/juju-core/2.0. The final stable build will 
be ready in time for the xenial release.
  
  Upgrades
  
  Users upgrading from trusty will find their juju version updated. The current 
juju-core package will be provided as juju-1.25. Update-alternatives will 
provide support for toggling /usr/bin/juju between juju-1.25 and juju-2.0 
binaries.
  
  We have tested to ensure the intended behavior occurs for the following
  scenarios:
  
  New Xenial:
  No juju, apt-get install juju, juju version will be 2.0.
  Example using ppa: 
  
  Upgrading Trusty/Wily/old Xenial:
  Already installed juju 1.X, upgraded to latest 1.25.4, 2.0 also installed and 
is the default juju, update-alternatives used to switch between the two.
  Example using ppa: 
  
  Risks
  -
  Although juju itself is now feature complete for 2.0, the MAAS 2.0 support 
will require additional work to be fully supported. MAAS 2.0 is currently under 
development as well, and is an alpha3 at the time of this writing. Juju will 
need to add support for the final version of MAAS 2.0, and this is a risk of 
occurring after xenial is released. If so, we expect to release an sru for 
juju-core soon after xenial releases to provide this support.
  
  Quality / Testing
  -
  As this version breaks API with 1.0, testing for features regressions as well 
as fixing old bugs and avoiding new bugs has been important. The juju team and 
the greater juju community has been testing 2.0 to ensure it’s stable and ready 
to support all of the 1.0 workloads in addition to making use of the new 2.0 
features.
  
  In comparison to juju-1.25:
  
  * Tests improvements including
  * MAAS testing improved
  * Container networking
  * 9 non-voting tests are now voting
  * New tests for all 2.0 features
  * Powerpc toolchain is vastly improved
  * No test regressions!
  * S390 builds reliably, is fully tested and is treated the same as other 
supported architectures
  * 114 bugs has been fixed
  
  Juju practices continuous integration and testing of the juju source
  tree. All voting tests must pass for ubuntu before release. For example,
  for beta3, you can see all tests are passing on ubuntu. The full details
  are here: http://reports.vapour.ws/releases/3815.
  
  The community has also been actively involved with testing, providing
  feedback, and adopting 2.0 throughout the development cycle.
  
  * 250 bugs and wishlist items filed
  * 4 bugs fixed by community members
  * ~100-125 downloads for each ppa release
  
  Community Adoption
  --
  The community has already begun 

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

[Richard Harding]

** 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 the new package
  juju-core-1.25, which is a new version of the existing juju-core package
  allowing the existing juju1 binary to be installed.
  
  Related FFes
  
  
  Required for Juju 2.0:
  
  juju-mongodb3.2: bug 1557852
  juju-mongodb2.6: bug 1557830
  juju-mongo-tools3.2: bug 1558336
  
  (see note below about mongodb for details)
  
  Required consumers:
  
  conjure: bug 1561037
  bigdata: bug 1561043
  openstack: Already in universe, dep wait on conjure -> juju 2.0
  charm-tools: bug 1546776
  
  User-Facing Features / Changes
  --
  * New Terminology
  * Command Name Changes
  * New Juju home directory
  * Multi-Model Support Active by Default
  * New Bootstrap and Cloud Management Experience
  * Native Support for Charm Bundles
  * Multi Series Charms
  * Improved Local Charm Deployment
  * LXC Local Provider No Longer Available
  * LXD Provider
  * LXD Containers
  * Microsoft Azure Resource Manager Provider
  * Bootstrap Constraints, Series
  * Juju Logging Improvements
  * Unit Agent Improvements
  * API Login with Macaroons
  * MAAS Spaces
  * Resources
  * Juju Status Improvements
  * Relation Get and Set Compatibility
  * Support for new AWS M4 Instance Types
  * Support for win10 and win2016
  
  The full list of changes can be found here: 
https://lists.ubuntu.com/archives/juju/2016-March/006922.html
  and in the final release notes.
  
  Timeline
  
  We have released 2 alphas, and 3 betas for juju2 so far, in addition 3 alpha 
builds of 1.26 which became 2.0.  All targeted 2.0 features are now 
implemented, and we anticipate releasing one release candidate before a final 
stable build. Juju missed uploading any versions of 2.0 to the archive itself,  
as well as the initial projected date of having beta1 in xenial before feature 
freeze. However, juju has been released regularly during the development cycle 
inside the juju ppa. You can see the details on the delivered features and 
milestones on https://launchpad.net/juju-core/2.0. The final stable build will 
be ready in time for the xenial release.
  
  Upgrades
  
  Users upgrading from trusty will find their juju version updated. The current 
juju-core package will be provided as juju-1.25. Update-alternatives will 
provide support for toggling /usr/bin/juju between juju-1.25 and juju-2.0 
binaries.
  
  We have tested to ensure the intended behavior occurs for the following
  scenarios:
  
  New Xenial:
  No juju, apt-get install juju, juju version will be 2.0.
  Example using ppa: 
  
  Upgrading Trusty/Wily/old Xenial:
  Already installed juju 1.X, upgraded to latest 1.25.4, 2.0 also installed and 
is the default juju, update-alternatives used to switch between the two.
  Example using ppa: 
  
  Risks
  -
  Although juju itself is now feature complete for 2.0, the MAAS 2.0 support 
will require additional work to be fully supported. MAAS 2.0 is currently under 
development as well, and is an alpha3 at the time of this writing. Juju will 
need to add support for the final version of MAAS 2.0, and this is a risk of 
occurring after xenial is released. If so, we expect to release an sru for 
juju-core soon after xenial releases to provide this support.
  
  Quality / Testing
  -
  As this version breaks API with 1.0, testing for features regressions as well 
as fixing old bugs and avoiding new bugs has been important. The juju team and 
the greater juju community has been testing 2.0 to ensure it’s stable and ready 
to support all of the 1.0 workloads in addition to making use of the new 2.0 
features.
  
  In comparison to juju-1.25:
  
  * Tests improvements including
  * MAAS testing improved
  * Container networking
  * 9 non-voting tests are now voting
  * New tests for all 2.0 features
  * Powerpc toolchain is vastly improved
  * No test regressions!
  * S390 builds reliably, is fully tested and is treated the same as other 
supported architectures
  * 114 bugs has been fixed
  
  Juju practices continuous integration and testing of the juju source
  tree. All voting tests must pass for ubuntu before release. For example,
  for beta3, you can see all tests are passing on ubuntu. The full details
  are here: http://reports.vapour.ws/releases/3815.
  
  The community has also been actively involved with testing, providing
  feedback, and adopting 2.0 throughout the development cycle.
  
  * 250 bugs and wishlist items filed
  * 4 bugs fixed by community members
  * ~100-125 downloads for each ppa release
  
  Community Adoption
  --
  The community has already begun 

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

[Richard Harding]

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 manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1545913/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

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

[Richard Harding]

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 so that upgrades will make 
sure that juju 1 stays available
- make juju1 the higher update-alternatives priority.
- trim the binary size of the juju package by reducing the duplication
- investigate the ability to perform stripping to reduce size

-- 
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:
https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1545913/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

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

[Richard Harding]

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
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:
https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1545913/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

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

[Richard Harding]

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 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:
https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1545913/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1408280] Re: juju-quickstart fails with SSL verification errors

[Richard Harding]

Curtis, did you have a bug filed I can look back at the history there? I
faintly recall the conversation but I don't remember if we had some
documentation/bug to go with it.

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-quickstart in Ubuntu.
https://bugs.launchpad.net/bugs/1408280

Title:
  juju-quickstart fails with SSL verification errors

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/juju-quickstart/+bug/1408280/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1359938] [NEW] [FFE] request to update juju-quickstart to support JUJU env var

[Richard Harding]

Public bug reported:

We'd like to complete updating juju-quickstart to support a $JUJU env
variable to help enable and aid CI and testing. This would allow the
user to specify which Juju client to use which would open the doors to
testing quickstart on one system against several versions of Juju.

This does not require any changes to dependencies or functionality.

The list of changes suggested include:

- If $JUJU is set, use that for bootstrap on all systems that do not require 
juju-quickstart to be run with sudo (due to old LXC requirements)
- If $JUJU is set and we are on an older LXC requiring sudo we output a warning 
and refuse to run against the $JUJU specified in the env variable.

Work on this is in progress and can be seen at
https://codereview.appspot.com/132770043/

This work is not complete, but should be ready soon and so we'd like to
request a FFE to complete this work.

** Affects: juju-quickstart (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-quickstart in Ubuntu.
https://bugs.launchpad.net/bugs/1359938

Title:
  [FFE] request to update juju-quickstart to support JUJU env var

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/juju-quickstart/+bug/1359938/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1359944] [NEW] [FFE] Update juju-quickstart to support MAAS as a configurable provider

[Richard Harding]

Public bug reported:

We have the goal this cycle of updating juju-quickstart to be able to
build the environments.yaml block for MAAS as it can for local, ec2,
hpcloud, etc. This work is not yet complete, but we'd like to request an
exception to get it in.

There is little risk that adding another provider will create issues for
juju-quickstart users. We already support five providers and so this new
one should not require any deep changes to the way quickstart operates.

The changes required are

- The first time you launch quickstart you'd see a new item in the new provider 
list, MAAS.
- Selecting that needs to populate a form UI for entering all the provider 
specific information required by MAAS.
- Saving that form updates your environments.yaml with the new provider block 
as it does for the others.
- We do not currently believe that adding this provider will require 
fundamental changes in the way juju-quickstart works once the provider is 
available.

We'll be looking to complete this work before the end of September and
have the final juju-quickstart release ready one month before the
release of Utopic.

** Affects: juju-quickstart (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-quickstart in Ubuntu.
https://bugs.launchpad.net/bugs/1359944

Title:
  [FFE] Update juju-quickstart to support MAAS as a configurable
  provider

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/juju-quickstart/+bug/1359944/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1325013] Re: juju-quickstart has no dep8 tests so can break when juju-core changes

[Richard Harding]

** Changed in: juju-quickstart
   Status: New = Triaged

** Changed in: juju-quickstart
   Importance: Undecided = High

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-quickstart in Ubuntu.
https://bugs.launchpad.net/bugs/1325013

Title:
  juju-quickstart has no dep8 tests so can break when juju-core changes

To manage notifications about this bug go to:
https://bugs.launchpad.net/juju-quickstart/+bug/1325013/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1149410] Re: Stuck on Trying to connect to the Juju environment

[Richard Harding]

Brian, can you do me a favor and check out the network inspector tool of
the browser in your scenario? The client you load the GUI from needs to
be able to login/pull down the JS from the GUI charm, however it also
needs to talk on other ports as it holds a websocket connection to the
juju state server. If the screen is spinning that it's unable to connect
to the environment, I suspect the proxy is not proxying the secure
websocket connection through to the juju state server.

A look at the network tab while loading the GUI should show the
websocket connection attempting but failing.

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju in Ubuntu.
https://bugs.launchpad.net/bugs/1149410

Title:
  Stuck on Trying to connect to the Juju environment

To manage notifications about this bug go to:
https://bugs.launchpad.net/juju-gui/+bug/1149410/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1316291] Re: juju-quickstart hangs on machine 1 provisioning is pending

[Richard Harding]

*** This bug is a duplicate of bug 1306537 ***
https://bugs.launchpad.net/bugs/1306537

Marked as a dupe. This is corrected in juju-quickstart 1.3.2. We'll work
on getting it updated in Trusty after the holiday this week.

** This bug has been marked a duplicate of bug 1306537
   LXC local provider fails to provision precise instances from a trusty host

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-quickstart in Ubuntu.
https://bugs.launchpad.net/bugs/1316291

Title:
  juju-quickstart hangs on machine 1 provisioning is pending

To manage notifications about this bug go to:
https://bugs.launchpad.net/juju-quickstart/+bug/1316291/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1282630] Re: [FFe] Upgrade juju-quickstart to new upstream release 1.3.0

[Richard Harding]

Yes, we were originally told the feature we were waiting on would be in
release 1.18. It ended up they cut additional releases ahead of 1.18
that implemented what was required. The 1.18 note is no longer valid.

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-quickstart in Ubuntu.
https://bugs.launchpad.net/bugs/1282630

Title:
  [FFe] Upgrade juju-quickstart to new upstream release 1.3.0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/juju-quickstart/+bug/1282630/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1273865] Re: [MIR] juju-quickstart, python-jujuclient, urwid, websocket-client

[Richard Harding]

@Michael

 - Can you explain what all the PPA adding and pulling in packages from
universe is about? Why not depend on juju-core directly, or is this
installation done on other machines?

Quickstart is meant to provide a nice single point to get developers and
users started with Juju as fast and effortlessly as possible. It's meant
to be a useful tool for users that will be expecting to work on Juju and
the latest versions so that they're developing against current and
upcoming work. It's not intended to be a production tool for managing
your critical production deployments.

This is something that we came at from our typical user point of view,
and didn't properly consider the implications for the repositories.
We've started work to support a --distro-only flag to quickstart that
will allow it to function without adding and fetching Juju from the PPA.
This should allow users that wish to stick with the version in distro to
do so, but allow most users to quickly get a development environment on
the current version going with a single command.

Let me know if you'd prefer to approach this differently. Our goal is to
help ease the onramp to Juju for users and, and eventually we hope to
get quickstart on the cd so that, from  a fresh install, you'd be able
to get Juju running with a local LXC environment right away. The goal
would not be to get Juju, mongodb, and lxc all built into the cd or on
main. It's a starting point and not a complete wrapper.

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-quickstart in Ubuntu.
https://bugs.launchpad.net/bugs/1273865

Title:
  [MIR] juju-quickstart, python-jujuclient, urwid, websocket-client

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/juju-quickstart/+bug/1273865/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1149410] Re: Stuck on Trying to connect to the Juju environment

[Richard Harding]

Marking invalid as fixes have been released and things have been quite
for a while. If the issue returns please open a new bug.

** Changed in: juju-gui
   Status: Incomplete = Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju in Ubuntu.
https://bugs.launchpad.net/bugs/1149410

Title:
  Stuck on Trying to connect to the Juju environment

To manage notifications about this bug go to:
https://bugs.launchpad.net/juju-gui/+bug/1149410/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 418897] Re: Segfaults in apache2 with libapache2-mod-php5 installed

[Richard Harding]

** Changed in: php5 (Ubuntu)
   Status: New = Confirmed

-- 
Segfaults in apache2 with libapache2-mod-php5 installed
https://bugs.launchpad.net/bugs/418897
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to php5 in ubuntu.

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 418897] Re: Segfaults in apache2 with libapache2-mod-php5 installed

[Richard Harding]

Just to verify the workaround above of disabling the session encryption
seems to be working so far.

-- 
Segfaults in apache2 with libapache2-mod-php5 installed
https://bugs.launchpad.net/bugs/418897
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to php5 in ubuntu.

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs