[Bug 1509147] Re: [SRU] MAAS 1.9.0
** Description changed: We would like to request a SRU for MAAS 1.9. This follow the approval by the Ubuntu Technical Board for backporting new MAAS upstream releases. [Impact] This is a new version of MAAS that provides new features as well as various bug fixes against various issues. It increases MAAS' reliability and serviceability and greatly improves MAAS as a whole. [Regression Potential] Minimal. MAAS has been thoroughly tested stand alone and upgrading from 1.7 and 1.8. It has been QA'd in a CI lab as well as other production deployments: Tests done: 1. Upgraded a production lab from 1.7.6 to 1.9.0 (and 1.9.0 later on). MAAS 1.9 has proven to be more robust, and higher deployment rates without failures than 1.9.0. This lab is a high load lab that stress tests deployments with MAAS. 2. Every MAAS release is thoroughly tested for upgrades. For 1.9, upgrade tests include: - Upgrading from 1.5 to 1.9 directly - Upgrading from 1.5 to 1.7 to 1.8 to 1.9 - Upgrading from 1.7 to 1.9 3. MAAS CI Lab: - Tests Installation (from pkgs), configuration / customization of MAAS, enlistment, commissioning. It also tests deployments with Juju. - Tests various API's - Tests are performed against Trusty. 4. Other manual testing include: - Installation (both fresh and upgrades) - Configuration - Taking nodes through the lifecycle for regression testing. - Custom configuration to ensure proper operation. - Tests API's for regressions, and keeping backwards compatibility. - - 5. Landscape has thoroughly tested 1.9 before moving away from 1.7, not - only to ensure backwards compatibility but also to test new features and - capabilities. = Changelog = 1.9.0 = Important announcements --- **New Networking Concepts and API's: Fabrics, Spaces and Subnets** With the introduction of new MAAS networking concepts, new API's are also been introduced. These are: * fabrics * spaces * subnets * vlans * fan-networks MAAS 1.9.0 will continue to provide backwards compatibility with the old network API for reading purposes, but moving forward, users are required to use the new API to manipulate fabrics, spaces and subnets. **Advanced Network and Storage Configuration only available for Ubuntu deployments** Users can now perform advanced network and storage configurations for nodes before deployment. The advanced configuration is only available for Ubuntu deployments. All other deployments using third party OS', including CentOS, RHEL, Windows and Custom Images, won't result in such configuration. **Re-commissioning required for upgraded MAAS** Now that storage partitioning and advanced configuration is supported natively, VM nodes in MAAS need to be re-commissioned. * If upgrading from MAAS 1.8, only VM nodes with VirtIO storage devices need to be re-commissioned. * If upgrading from MAAS 1.7, all nodes will need to be re- commissioned in order for MAAS to correctly capture the storage and networking devices. This does not affect nodes that are currently deployed. **Default Storage Partitioning Layout - Flat** With the introduction of custom storage, MAAS has also introduced the concept of partitioning layouts. Partitioning layouts allow the user to quickly auto-configure the disk partitioning scheme after first commissioning or re-commissioning (if selected to do so). The partitioning layouts are set globally on the `Settings` page. The current default Partitioning layout is 'Flat', maintaining backwards compatibility with previous MAAS releases. This means MAAS will take the first disk it finds in the system and use it as the root and boot disk. **Deployment with configured /etc/network/interfaces** Starting with MAAS 1.9, all node deployments will result in writing `/etc/network/interfaces` statically, by default. This increases MAAS' robustness and reliability as users no longer have to depend on DHCP for IP address allocation solely. MAAS will continue to provide IP addresses via DHCP, even though interfaces in `/etc/network/interfaces` may have been configured statically. Major new features -- **Storage Partitioning and Advanced Configuration** MAAS now supports Storage Partitioning and Advanced Configuration natively. This allows MAAS to deploy machines with different Storage Layouts, as well as different complex partitioning configurations. Storage support includes: * LVM * Bcache * Software RAID levels 0, 1, 5, 6, 10. * Advanced partitioning Storace configuration is available both via the WebUI and API. For more information refer to :ref:`storage`. **Advanced Networking (Fabrics, Spaces, Subnetworks) and Node Network Configuration** MAAS now supports Advanced Network
[Bug 1509147] Re: [SRU] MAAS 1.9.0
** No longer affects: maas (Ubuntu Vivid) ** Also affects: maas (Ubuntu Wily) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to maas in Ubuntu. https://bugs.launchpad.net/bugs/1509147 Title: [SRU] MAAS 1.9.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1509147/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1509147] Re: [SRU] MAAS 1.9.0
** Description changed: We would like to request a SRU for MAAS 1.9. This follow the approval by the Ubuntu Technical Board for backporting new MAAS upstream releases. [Impact] This is a new version of MAAS that provides new features as well as various bug fixes against various issues. It increases MAAS' reliability and serviceability and greatly improves MAAS as a whole. [Regression Potential] Minimal. MAAS has been thoroughly tested stand alone and upgrading from 1.7 and 1.8. It has been QA'd in a CI lab as well as other production deployments: Tests done: 1. Upgraded a production lab from 1.7.6 to 1.9.0 (and 1.9.0 later on). MAAS 1.9 has proven to be more robust, and higher deployment rates - without failures than 1.9.0. This lab is a high load lab that stress + without failures than 1.7.6. This lab is a high load lab that stress tests deployments with MAAS. 2. Every MAAS release is thoroughly tested for upgrades. For 1.9, upgrade tests include: - Upgrading from 1.5 to 1.9 directly - Upgrading from 1.5 to 1.7 to 1.8 to 1.9 - Upgrading from 1.7 to 1.9 3. MAAS CI Lab: - Tests Installation (from pkgs), configuration / customization of MAAS, enlistment, commissioning. It also tests deployments with Juju. - Tests various API's - Tests are performed against Trusty. 4. Other manual testing include: - Installation (both fresh and upgrades) - Configuration - Taking nodes through the lifecycle for regression testing. - Custom configuration to ensure proper operation. - Tests API's for regressions, and keeping backwards compatibility. 5. Landscape has thoroughly tested 1.9 before moving away from 1.7, not only to ensure backwards compatibility but also to test new features and capabilities. = Changelog = 1.9.0 = Important announcements --- **New Networking Concepts and API's: Fabrics, Spaces and Subnets** With the introduction of new MAAS networking concepts, new API's are also been introduced. These are: * fabrics * spaces * subnets * vlans * fan-networks MAAS 1.9.0 will continue to provide backwards compatibility with the old network API for reading purposes, but moving forward, users are required to use the new API to manipulate fabrics, spaces and subnets. **Advanced Network and Storage Configuration only available for Ubuntu deployments** Users can now perform advanced network and storage configurations for nodes before deployment. The advanced configuration is only available for Ubuntu deployments. All other deployments using third party OS', including CentOS, RHEL, Windows and Custom Images, won't result in such configuration. **Re-commissioning required for upgraded MAAS** Now that storage partitioning and advanced configuration is supported natively, VM nodes in MAAS need to be re-commissioned. * If upgrading from MAAS 1.8, only VM nodes with VirtIO storage devices need to be re-commissioned. * If upgrading from MAAS 1.7, all nodes will need to be re-commissioned in order for MAAS to correctly capture the storage and networking devices. This does not affect nodes that are currently deployed. **Default Storage Partitioning Layout - Flat** With the introduction of custom storage, MAAS has also introduced the concept of partitioning layouts. Partitioning layouts allow the user to quickly auto-configure the disk partitioning scheme after first commissioning or re-commissioning (if selected to do so). The partitioning layouts are set globally on the `Settings` page. The current default Partitioning layout is 'Flat', maintaining backwards compatibility with previous MAAS releases. This means MAAS will take the first disk it finds in the system and use it as the root and boot disk. **Deployment with configured /etc/network/interfaces** Starting with MAAS 1.9, all node deployments will result in writing `/etc/network/interfaces` statically, by default. This increases MAAS' robustness and reliability as users no longer have to depend on DHCP for IP address allocation solely. MAAS will continue to provide IP addresses via DHCP, even though interfaces in `/etc/network/interfaces` may have been configured statically. Major new features -- **Storage Partitioning and Advanced Configuration** MAAS now supports Storage Partitioning and Advanced Configuration natively. This allows MAAS to deploy machines with different Storage Layouts, as well as different complex partitioning configurations. Storage support includes: * LVM * Bcache * Software RAID levels 0, 1, 5, 6, 10. * Advanced partitioning Storace configuration is available both via the WebUI and API. For more information refer to :ref:`storage`. **Advanced Networking (Fabrics,
[Bug 1509147] Re: [SRU] MAAS 1.9.0
** Description changed: We would like to request a SRU for MAAS 1.9. This follow the approval by the Ubuntu Technical Board for backporting new MAAS upstream releases. [Impact] This is a new version of MAAS that provides new features as well as various bug fixes against various issues. It increases MAAS' reliability and serviceability and greatly improves MAAS as a whole. [Regression Potential] Minimal. MAAS has been thoroughly tested stand alone and upgrading from 1.7 and 1.8. It has been QA'd in a CI lab as well as other production deployments: Tests done: 1. Upgraded a production lab from 1.7.6 to 1.9.0 (and 1.9.0 later on). MAAS 1.9 has proven to be more robust, and higher deployment rates - without failures than 1.7.6. This lab is a high load lab that stress + without failures than 1.9.0. This lab is a high load lab that stress tests deployments with MAAS. 2. Every MAAS release is thoroughly tested for upgrades. For 1.9, upgrade tests include: - Upgrading from 1.5 to 1.9 directly - Upgrading from 1.5 to 1.7 to 1.8 to 1.9 - Upgrading from 1.7 to 1.9 3. MAAS CI Lab: - Tests Installation (from pkgs), configuration / customization of MAAS, enlistment, commissioning. It also tests deployments with Juju. - Tests various API's - Tests are performed against Trusty. 4. Other manual testing include: - Installation (both fresh and upgrades) - Configuration - Taking nodes through the lifecycle for regression testing. - Custom configuration to ensure proper operation. - Tests API's for regressions, and keeping backwards compatibility. 5. Landscape has thoroughly tested 1.9 before moving away from 1.7, not only to ensure backwards compatibility but also to test new features and capabilities. = Changelog = 1.9.0 = Important announcements --- **New Networking Concepts and API's: Fabrics, Spaces and Subnets** - With the introduction of new MAAS networking concepts, new API's are also - been introduced. These are: + With the introduction of new MAAS networking concepts, new API's are also been introduced. These are: * fabrics * spaces * subnets * vlans * fan-networks - MAAS 1.9.0 will continue to provide backwards compatibility with the old - network API for reading purposes, but moving forward, users are required to - use the new API to manipulate fabrics, spaces and subnets. + MAAS 1.9.0 will continue to provide backwards compatibility with the + old network API for reading purposes, but moving forward, users are + required to use the new API to manipulate fabrics, spaces and subnets. **Advanced Network and Storage Configuration only available for Ubuntu deployments** - Users can now perform advanced network and storage configurations for nodes - before deployment. The advanced configuration is only available for Ubuntu - deployments. All other deployments using third party OS', including CentOS, - RHEL, Windows and Custom Images, won't result in such configuration. + Users can now perform advanced network and storage configurations for nodes before deployment. The advanced configuration is only available for Ubuntu deployments. All other deployments using third party OS', including CentOS, RHEL, Windows and Custom Images, won't result in such configuration. **Re-commissioning required for upgraded MAAS** - Now that storage partitioning and advanced configuration is supported natively, - VM nodes in MAAS need to be re-commissioned. - - * If upgrading from MAAS 1.8, only VM nodes with VirtIO storage devices need - to be re-commissioned. - - * If upgrading from MAAS 1.7, all nodes will need to be re-commissioned in - order for MAAS to correctly capture the storage and networking devices. + Now that storage partitioning and advanced configuration is supported natively, VM nodes in MAAS need to be re-commissioned. + + * If upgrading from MAAS 1.8, only VM nodes with VirtIO storage + devices need to be re-commissioned. + + * If upgrading from MAAS 1.7, all nodes will need to be re- + commissioned in order for MAAS to correctly capture the storage and + networking devices. This does not affect nodes that are currently deployed. **Default Storage Partitioning Layout - Flat** - With the introduction of custom storage, MAAS has also introduced the concept - of partitioning layouts. Partitioning layouts allow the user to quickly - auto-configure the disk partitioning scheme after first commissioning or - re-commissioning (if selected to do so). The partitioning layouts are set - globally on the `Settings` page. - - The current default Partitioning layout is 'Flat', maintaining backwards - compatibility with previous MAAS releases. This means MAAS will take the - first disk it finds in the system and use it as the root and boot disk. + With the introduction of custom
[Bug 1509147] Re: [SRU] MAAS 1.9.0
** Summary changed: - [SRU] MAAS 1.8.3 + [SRU] MAAS 1.9.0 ** Description changed: We would like to request a SRU for MAAS 1.8. This follow the approval by the Ubuntu Technical Board for backporting new MAAS upstream releases. [Impact] This is a new version of MAAS that provides new features as well as various bug fixes against various issues. It increases MAAS' reliability and serviceability and greatly improves MAAS as a whole. [Regression Potential] Minimal. MAAS has been thoroughly tested stand alone and upgrading from 1.7 and 1.8. It has been QA'd in a CI lab as well as other production deployments: Tests done: - 1. Upgraded a production lab from 1.7.6 to 1.8.2 (and 1.8.3 later on). - MAAS 1.8 has proven to be more robust, and higher deployment rates - without failures than 1.7.6. This lab is a high load lab that stress + 1. Upgraded a production lab from 1.7.6 to 1.9.0 (and 1.9.0 later on). + MAAS 1.9 has proven to be more robust, and higher deployment rates + without failures than 1.9.0. This lab is a high load lab that stress tests deployments with MAAS. - 2. Every MAAS release is thoroughly tested for upgrades. For 1.8, upgrade tests include: - - Upgrading from 1.5 to 1.8 directly - - Upgrading from 1.5 to 1.7 to 1.8 - - Upgrading from 1.7 to 1.8 + 2. Every MAAS release is thoroughly tested for upgrades. For 1.9, upgrade tests include: + - Upgrading from 1.5 to 1.9 directly + - Upgrading from 1.5 to 1.7 to 1.8 to 1.9 + - Upgrading from 1.7 to 1.9 3. MAAS CI Lab: - Tests Installation (from pkgs), configuration / customization of MAAS, enlistment, commissioning. It also tests deployments with Juju. - Tests various API's - Tests are performed against Trusty. 4. Other manual testing include: - Installation (both fresh and upgrades) - Configuration - Taking nodes through the lifecycle for regression testing. - Custom configuration to ensure proper operation. - Tests API's for regressions, and keeping backwards compatibility. - 5. Landscape has thoroughly tested 1.8 before moving away from 1.7, not + 5. Landscape has thoroughly tested 1.9 before moving away from 1.7, not only to ensure backwards compatibility but also to test new features and capabilities. = Changelog = - 1.8.3 - = - - See https://launchpad.net/maas/+milestone/1.8.3 for full details. - - Bug Fix Update - -- - - #1495064Declare dependency on metadataserver migration 0015 by - maasserver migration 0121 to allow upgrades from 1.5.4 to 1.8 to work. - - #1484696Fix the issue where the included ':', apache2 wont forward - the connection (LP: #1484696) - - #1489160WebUI - Fixes autocomplete styling for tagging - - #1491898Add HPDSA hardware drivers to the drivers config - - #1491822Always invoke the init system using the C.UTF-8 locale. - - #1471946Restart maas-clusterd in the event of startup failure due to - missing /var/lib/maas/secret - - #1483273Use Cluster's name instead of DNS name for the WebUi. - - #1504971Internal Server Error when trying to configure a cluster - interface in wily. - - 1.8.2 - = - - See https://launchpad.net/maas/+milestone/1.8.2 for full details. - - Bug Fix Update - -- - - #1484696Regenerate the connection URL on websocket client reconnect, - to fix CSRF after upgrade to 1.8.1. - - #1445942Validate the osystem and distro_series when using the deploy - action, which fixes win2012r2 deployment issues. - - #1481940Fix failure in MAAS startup messages by not generating dhcpd - config files when they are not in use. - - #1459865Fix enlistment to always use the correct kernel parameters. - - 1.8.1 - = - - See https://launchpad.net/maas/+milestone/1.8.1 for full details. - - Bug Fix Update - -- - - #1481118Add --username to maas-region-admin apikey command docs. - - #1472707Add ListBootImagesV2 RPC command. Fallback to using - ListBootImages RPC when the ListBootImagesV2 is not handled on the - cluster. - - #1470591Fix setting the default_distro_series over the API. - - #1413388Fix upgrade issue where it would remove custom DNS config, - potentially breaking DNS - - #1317705Commissioning x86_64 node never completes, sitting at grub - prompt, pserv py tbs - - #1389007Power monitor service hits amp.TooLong errors with > ~600 - nodes to a cluster - - #1436279Websocket server accessed over port 5240 - - #1469305If hostname not set, sudo warning make maas throw 500 - - #1470585Can't set a list of forwarders (BIND config) - - #1469846UCS chassis enlist Failed to probe and enlist UCS nodes: - list index out of range - - #1470276Add cisco snic to 3rd party driver - - #1402042console= parameters need to be added before -- on kernel - cmdline - - #1465722[UI] Machine details styling - - #1465737[UI] Actions design styles - - #1465740
