[SRU] New upstream Release 1.7.2
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| | maas (Ubuntu) |
Undecided
|
Unassigned | ||
| | Trusty |
Undecided
|
Unassigned | ||
| | Utopic |
Undecided
|
Unassigned | ||
Bug Description
MAAS 1.7.2 is a new MAAS upstream release. This new upstream release of MAAS introduces completely new features that improve the robustness of MAAS as a whole, the usability, fixing major usability issues with previous MAAS releases
[Impact]
MAAS 1.7.2 is a new upstream that improves MAAS in several different ways:
1. Contains an Image Store to ensure that images are up to date across all cluster controllers
2. More robust. MAAS tracks progress of its various operations, to ensure that nodes are in the state they should be. If nodes failed to commission, MAAS will know about it. If nodes fail to Install, MAAS will know about it.
3. MAAS tracks the power status of each machine, to ensure they reflect reality.
4. Enablement for various hardware chassis.
5. MAAS 1.7 provides various UI improvements and fixes to improve the user experience and usability.
6. RPC Security. New security authentication mechanism is in place.
7. Support for third Party OS's (Windows, CentOS, SLES) and Custom Images.
8. Removal of Celery and RabbitMQ in favor of RPC.
9. New maas-proxy instead of the use of squid-deb-proxy
[Test Case]
1. sudo apt-get update && sudo apt-get dist-upgrade
2. Enlist nodes.
3. Commission nodes.
4. Deploy new nodes.
[Regression Potential]
MAAS 1.7.2 is fully API compatible with previous MAAS Releases. Users upgrading to MAAS 1.7 will need to re-import the image so these are stored in the Image Store. Users also need to be aware that if they have custom preseeds include a new file name to account for non-Ubuntu OS's. Users using remote cluster controller will have to ensure they have the authentication key.
| description: | updated |
| Changed in maas (Ubuntu): | |
| status: | New → Fix Released |
| Adam Conrad (adconrad) wrote : | #1 |
| Changed in maas (Ubuntu Trusty): | |
| status: | New → Invalid |
| Changed in maas (Ubuntu Utopic): | |
| status: | New → Invalid |
"Users upgrading to MAAS 1.7 will need to re-import the image so these are stored in the Image Store."
This is not an acceptable thing for an SRU to do. When we first talked about this "new upstream versions as SRUs" thing, and all the bullet points you'd need to tick off to be able to do it, automated migration of user data was pretty high on the list.
If users have to manually intervene on upgrade, it's not a suitable stable upgrade.