group.of.nepali.translators team mailing list archive

[Launchpad Bug Tracker <1696752@xxxxxxxxxxxxxxxxxx>]

This bug was fixed in the package maas - 2.2.0+bzr6054-0ubuntu2~16.10.1

---------------
maas (2.2.0+bzr6054-0ubuntu2~16.10.1) yakkety-proposed; urgency=medium

  * Stable Release Update. New MAAS upstream release 2.2.0 (LP: #1696752)
    - Support for Intel Rack Scale Design as a MAAS Pod.
    - Support for KVM as a MAAS Pod.
    - Support for Hardware Testing.
    - Support for Unmanaged Subnets.
    - Support for L2 Spaces.
    - Support for DHCP Relay.
    - Support for FB Wedge 40 & 100 switch discovery and deployment.
    - Improve Windows deployment.
    - Improved Commissioning environment.
    - Improved UX & UI.

 -- Andres Rodriguez <andreserl@xxxxxxxxxx>  Thu, 08 Jun 2017 19:42:04
-0400

** Changed in: maas (Ubuntu Yakkety)
       Status: Fix Committed => Fix Released

** Changed in: maas (Ubuntu Xenial)
       Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1696752

Title:
  [SRU] MAAS 2.2.0

Status in maas package in Ubuntu:
  New
Status in maas source package in Xenial:
  Fix Released
Status in maas source package in Yakkety:
  Fix Released
Status in maas source package in Zesty:
  Fix Released

Bug description:
  [Impact]
  This is a new upstream release that addresses various issues present in 2.1 and introduces various features that improve the robustness, and feature set of MAAS.

  MAAS 2.2.0 introduces the following features:

   * Intel Rack Scale Design support (via MAAS Pods).
   * Hardware Testing
   * DHCP Relay support
   * Unmanaged Subnets
   * L2 spaces
   * Improve Windows deployment support.
   * Facebook's wedge 40 & 100 discovery and deployment
   * Various UI & UX improvements
   * More robust commissioning environment

  [Test Case]
  MAAS testing has been done in various cases, partially documented https://wiki.ubuntu.com/MAASUpdates. This include:

  1. Manual Fresh installation of MAAS
  2. Manual upgrade from the previous Ubuntu Release.
  3. Automated (CI) testing of MAAS install and operation as per the MAAS' CI.
  4. Automated (CI) testing of MAAS install and operation against other Canonical's product (juju, Canonical OpenStack & Kubernetes) provided by the Canonical Solutions QA Team.
  5. Manual split region/rack test are performed. This is to ensure that if we upgrade a MAAS Region to a newer version, the MAAS rack of the older version remains connected and operational.

  All of this includes verifying normal operation, issues fixed, and
  ensuring that Canonical Cloud solutions can inter-operate. MAAS
  releases are also now vetted by the Solutions QA team.

  [Regression Potential]
  Minimal (For MAAS itself). MAAS is fully backwards compatible and handles upgrades from previous releases which result in the continuous operation of MAAS. Users will continue to use this new version of MAAS as they used it before.

  Medium (For not tested set of hardware) - A new version of Curtin has
  been SRU'd, and as such, this could impact the deployment of untested
  hardware Paths. MAAS, in itself, has not changed the way it deploys
  machines, but curtin (the one in charge of network, disk & boot-order)
  has.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1696752/+subscriptions