** 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 we need to - request a feature freeze exception for the following features: + 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. - - Juju-GUI in Core - - Removal of LXC from 2.0 codebase - - Model migration - - MAAS 2.0 support - - Keystone 3 support - - Resources (validation of file extension, notification of resource updates available from the charm store) - - Multi-model backup / restore enhancements - - Additional cloud credentials requirements - - Additional MAAS Spaces support + 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. - These features are critical for a final Juju 2.0 release. + 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 juju2 version updated. The current juju-core package will become juju-core1. Users upgrading from wily and trusty will get juju2 as part of the upgrade. Update-alternatives will provide support for toggling /usr/bin/juju between juju1 and juju2 binaries. + + We have tested to ensure the intended behavior occurs for the following + scenarios; + + Trusty + No juju -> install juju on xenial, juju-core is installed. + Juju-core -> juju-core-1.25 and juju-core installed, update-alternatives toggles + + + Wily + No juju -> install juju on xenial, juju-core is installed. + Juju-core -> juju-core-1.25 and juju-core installed, update-alternatives toggles + + 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 adopting 2.0, and is dependent upon 2.0 being inside xenial. + + * Multiple external customers are depending on 2.0 inside xenial + * Charm store fully supports 2.0 features + * Community charmers + * Gitlab, openstack and other charms already are using 2.0 features + * Many other charms are dependent upon multi-model/controller features + * Public demo and feedback sessions @ charmers summit + * Public talks accepted for discussing juju 2.0 at conferences + * 2 packages (conjure, bigdata) currently in the upload queue have been built and depend upon the new version of juju 2.0. + + Packaging + --------- + 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.
** 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. 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 juju2 version updated. The current juju-core package will become juju-core1. Users upgrading from wily and trusty will get juju2 as part of the upgrade. Update-alternatives will provide support for toggling /usr/bin/juju between juju1 and juju2 binaries. We have tested to ensure the intended behavior occurs for the following scenarios; Trusty No juju -> install juju on xenial, juju-core is installed. Juju-core -> juju-core-1.25 and juju-core installed, update-alternatives toggles - Wily No juju -> install juju on xenial, juju-core is installed. Juju-core -> juju-core-1.25 and juju-core installed, update-alternatives toggles 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 + * 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 adopting 2.0, and is dependent upon 2.0 being inside xenial. * Multiple external customers are depending on 2.0 inside xenial * Charm store fully supports 2.0 features * Community charmers * Gitlab, openstack and other charms already are using 2.0 features * Many other charms are dependent upon multi-model/controller features * Public demo and feedback sessions @ charmers summit * Public talks accepted for discussing juju 2.0 at conferences * 2 packages (conjure, bigdata) currently in the upload queue have been built and depend upon the new version of juju 2.0. Packaging --------- - The security team has requested changes to the current juju packaging with the ultimate goal of breaking out the embedded non-juju golang dependencies. + 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 ~15 dependencies have been packaged and will be uploaded + to the archive once the archive has opened again for Y development. We + will not be attempting to add these additional packages as part of this + FFE. -- 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
