[SRU] MAAS 2.2.0
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
maas (Ubuntu) |
Fix Released
|
High
|
Unassigned | ||
Xenial |
Fix Released
|
Undecided
|
Unassigned | ||
Yakkety |
Fix Released
|
Undecided
|
Unassigned | ||
Zesty |
Fix Released
|
Undecided
|
Unassigned |
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:/
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.
Changed in maas (Ubuntu): | |
importance: | Undecided → High |
description: | updated |
description: | updated |
description: | updated |
description: | updated |
description: | updated |
description: | updated |
Changed in maas (Ubuntu): | |
status: | New → Fix Released |
Hello Andres, or anyone else affected,
Accepted maas into zesty-proposed. The package will build now and be available at https:/ /launchpad. net/ubuntu/ +source/ maas/2. 2.0+bzr6054- 0ubuntu2~ 17.04.1 in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See https:/ /wiki.ubuntu. com/Testing/ EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users.
If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification- needed- zesty to verification- done-zesty. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed- zesty. In either case, details of your testing will help us make a better decision.
Further information regarding the verification process can be found at https:/ /wiki.ubuntu. com/QATeam/ PerformingSRUVe rification . Thank you in advance!