group.of.nepali.translators team mailing list archive

Thread
Date

[Bug 1772010] Re: [SRU] MAAS 2.3.4

To: group.of.nepali.translators@xxxxxxxxxxxxxxxxxxx
From: Andres Rodriguez <andreserl@xxxxxxxxxxxxx>
Date: Wed, 01 Aug 2018 20:37:22 -0000
Reply-to: Bug 1772010 <1772010@xxxxxxxxxxxxxxxxxx>
Sender: bounces@xxxxxxxxxxxxx

** Summary changed:

- [SRU] MAAS 2.3.3
+ [SRU] MAAS 2.3.4

** Description changed:

[Impact]
This is a new upstream release that addresses various issues present in 2.3.0.

- MAAS 2.3.3 fixes various issues that were present on MAAS 2.3.0.
+ MAAS 2.3.4 fixes various issues that were present on MAAS 2.3.0.

https://launchpad.net/maas/+milestone/2.3.1
https://launchpad.net/maas/+milestone/2.3.2
https://launchpad.net/maas/+milestone/2.3.3
+ https://launchpad.net/maas/+milestone/2.3.4

This point release includes fixes/enhancements for hardware enablement
and to address customer related issues:

* Bug 1750622 "[feature] Add ability to select the BIOS boot method for
IPMI - To address issues with newer firmware"

This adds a new option to power manage machines, that are oriented at
addressing changes in upstream hardware firmware's (that have broken
compatibility with older versions). Causes no behavior changes for MAAS
as it continues to do the same.

Bug 1758760 "[enhancement] Support Lenovo’s new password policy (Lenovo
SR550)"

Fixes the password generation process for IPMI discovery to consider new
password policies that are being added to newer hardware or firmware
versions.

Bug 1739761 [adds support to deploy Precise on MAAS 2.3]

Re-adds the ability to deploy precise, which was dropped on MAAS 2.3
initially.

Bug 1730751 "LACP rate fast by default"

Changes the default LACP rate to fast, which addresses issues in that
our IS department was facing. Note that this only changes how often the
control packets are set and it is recommended/preferred to be set to
fast, and the use of slow is discouraged.

[Test Case]

MAAS Testing
------------
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.

Solutions QA
------------
MAAS releases are also now vetted by the Solutions QA team. The test they run ensure there are no regression for their use cases. This release has been accepted / vetted by them.

[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.

Since this is a point release, this has been tested thoroughly to
confirm that no regressions have been introduced.

** Description changed:

[Impact]
This is a new upstream release that addresses various issues present in 2.3.0.

MAAS 2.3.4 fixes various issues that were present on MAAS 2.3.0.

https://launchpad.net/maas/+milestone/2.3.1
https://launchpad.net/maas/+milestone/2.3.2
https://launchpad.net/maas/+milestone/2.3.3
https://launchpad.net/maas/+milestone/2.3.4

This point release includes fixes/enhancements for hardware enablement
and to address customer related issues:

* Bug 1750622 "[feature] Add ability to select the BIOS boot method for
IPMI - To address issues with newer firmware"

Bug 1758760 "[enhancement] Support Lenovo’s new password policy (Lenovo
SR550)"

Fixes the password generation process for IPMI discovery to consider new
password policies that are being added to newer hardware or firmware
versions.

Bug 1739761 [adds support to deploy Precise on MAAS 2.3]
-
- Re-adds the ability to deploy precise, which was dropped on MAAS 2.3
- initially.
+ Re-adds the ability to deploy precise, which was dropped on MAAS 2.3 initially.

Bug 1730751 "LACP rate fast by default"
+ Changes the default LACP rate to fast, which addresses issues in that our IS department was facing. Note that this only changes how often the control packets are set and it is recommended/preferred to be set to fast, and the use of slow is discouraged.

- Changes the default LACP rate to fast, which addresses issues in that
- our IS department was facing. Note that this only changes how often the
- control packets are set and it is recommended/preferred to be set to
- fast, and the use of slow is discouraged.
+ Bug 1767137 "Default install is now importing bionic by default instead of xenial"
+ This is an issue that MAAS automatically started selection Bionic for commissioning instead of Xenial as it was intended. This ensure that Xenial is selected by default. Note that in case of upgrades, if Bionic is already selected, MAAS won't change this to Xenial. It will *only* affect to new installs.

[Test Case]

MAAS Testing
------------
MAAS testing has been done in various cases, partially documented https://wiki.ubuntu.com/MAASUpdates. This include:

All of this includes verifying normal operation, issues fixed, and
ensuring that Canonical Cloud solutions can inter-operate.

[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.

- Since this is a point release, this has been tested thoroughly to
- confirm that no regressions have been introduced.
+ 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.
+
+ Minimal (for deployments).
+ LP: #1730751 is fixed in this release, which changes the default LACP rate to fast. This doesn't provide any regression for MAAS itself, machines deployed with bonds will have the LACP rate to fast, which will yield discovery of errors much faster.
+
+ Since this is a point release, this has been tested thoroughly to confirm that no regressions have been introduced.

** No longer affects: maas (Ubuntu Artful)

** Description changed:

[Impact]
This is a new upstream release that addresses various issues present in 2.3.0.

MAAS 2.3.4 fixes various issues that were present on MAAS 2.3.0.

https://launchpad.net/maas/+milestone/2.3.1
https://launchpad.net/maas/+milestone/2.3.2
https://launchpad.net/maas/+milestone/2.3.3
https://launchpad.net/maas/+milestone/2.3.4

This point release includes fixes/enhancements for hardware enablement
and to address customer related issues:

* Bug 1750622 "[feature] Add ability to select the BIOS boot method for
IPMI - To address issues with newer firmware"

Bug 1758760 "[enhancement] Support Lenovo’s new password policy (Lenovo
SR550)"

Fixes the password generation process for IPMI discovery to consider new
password policies that are being added to newer hardware or firmware
versions.
+
+ For backward compatibility, MAAS will use the previous password policy,
+ if it is not successful, it will try the new password policy.

Bug 1739761 [adds support to deploy Precise on MAAS 2.3]
Re-adds the ability to deploy precise, which was dropped on MAAS 2.3 initially.

Bug 1730751 "LACP rate fast by default"
Changes the default LACP rate to fast, which addresses issues in that our IS department was facing. Note that this only changes how often the control packets are set and it is recommended/preferred to be set to fast, and the use of slow is discouraged.

Bug 1767137 "Default install is now importing bionic by default instead of xenial"
This is an issue that MAAS automatically started selection Bionic for commissioning instead of Xenial as it was intended. This ensure that Xenial is selected by default. Note that in case of upgrades, if Bionic is already selected, MAAS won't change this to Xenial. It will *only* affect to new installs.

[Test Case]

MAAS Testing
------------
MAAS testing has been done in various cases, partially documented https://wiki.ubuntu.com/MAASUpdates. This include:

All of this includes verifying normal operation, issues fixed, and
ensuring that Canonical Cloud solutions can inter-operate.

[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.

Minimal (for deployments).
LP: #1730751 is fixed in this release, which changes the default LACP rate to fast. This doesn't provide any regression for MAAS itself, machines deployed with bonds will have the LACP rate to fast, which will yield discovery of errors much faster.
-
- Since this is a point release, this has been tested thoroughly to confirm that no regressions have been introduced.
+
+ Since this is a point release, this has been tested thoroughly to
+ confirm that no regressions have been introduced.

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

Title:
[SRU] MAAS 2.3.4

Status in maas package in Ubuntu:
New
Status in maas source package in Xenial:
New

Bug description:
[Impact]
This is a new upstream release that addresses various issues present in 2.3.0.

MAAS 2.3.4 fixes various issues that were present on MAAS 2.3.0.

https://launchpad.net/maas/+milestone/2.3.1
https://launchpad.net/maas/+milestone/2.3.2
https://launchpad.net/maas/+milestone/2.3.3
https://launchpad.net/maas/+milestone/2.3.4

This point release includes fixes/enhancements for hardware enablement
and to address customer related issues:

* Bug 1750622 "[feature] Add ability to select the BIOS boot method
for IPMI - To address issues with newer firmware"

Bug 1758760 "[enhancement] Support Lenovo’s new password policy
(Lenovo SR550)"

Fixes the password generation process for IPMI discovery to consider
new password policies that are being added to newer hardware or
firmware versions.

For backward compatibility, MAAS will use the previous password
policy, if it is not successful, it will try the new password policy.

Bug 1739761 [adds support to deploy Precise on MAAS 2.3]
Re-adds the ability to deploy precise, which was dropped on MAAS 2.3 initially.

[Test Case]

MAAS Testing
------------
MAAS testing has been done in various cases, partially documented https://wiki.ubuntu.com/MAASUpdates. This include:

All of this includes verifying normal operation, issues fixed, and
ensuring that Canonical Cloud solutions can inter-operate.

[Regression Potential]

Since this is a point release, this has been tested thoroughly to
confirm that no regressions have been introduced.

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