With regards to the upgrade path, what testing is done around partial
upgrades that leave a region and rack controller at different versions?

** Description changed:

  [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. This include:
+ 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.
  
  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.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1696752

Title:
  [SRU] MAAS 2.2.0

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to