[FFe] Standing FFe for MAAS 2.0

Bug #1553261 reported by Andres Rodriguez
This bug affects 1 person
Affects Status Importance Assigned to Milestone
maas (Ubuntu)

Bug Description

Dependencies & Upgrade

MAAS users that are upgrading to 2.0, they will be able to continue to use MAAS exactly the same way how they were using it before, right after the upgrade without any user intervention. While MAAS 2.0 adds significant changes, it however, is currently provides full feature parity with any earlier version of MAAS.

MAAS introduces several new features/changes:

 - Introduce Rack Controllers
 - It introduces a new API 2.0 to support the changes above
 - New DNS model that provides full support for managing DNS records.
 - Improves the IP Ranges support.
 - Introduces High Availability for DHCP

NOTE: Even with the newly introduced features, MAAS 2.0 is currently feature parity with older MAAS releases. This means that users will continue to use MAAS the same way they used to do it in previous releases, and current users upgrading wont be broken. The new features being introduced only enhance functionality.


 - We perform new install package testing to ensure that the package is rock solid on fresh installations.
 - We perform upgrade testing from previous MAAS and Ubuntu Releases. At the moment we perform upgrade testing covering upgrades from MAAS 1.9, 1.10. The upgrade ensures that MAAS after the upgrade is up and running with no issues.


MAAS 2.0 is targeted to be releases early next week. After that, the plan is to upload weekly to bi-weekly releases until Xenial closes.

The goal is definitely to release a final 2.0 version but as far as dates. We don't have a exact date for final, but we are targeting for the first week of April, depending on the quality at the time.

NOTE: The only reason why MAAS 2.0 is being released as alpha, is due to the introduction of the new features. However, MAAS 2.0 currently provides full feature parity with earlier MAAS releases.

Related branches

Changed in maas (Ubuntu):
importance: Undecided → Critical
Revision history for this message
Stéphane Graber (stgraber) wrote :

Can you talk a bit about your rdepends and how they'll be impacted with this change?

Also, what's your testing story for Ubuntu package?

You're asking for a standing FFe which I suspect means we'll be getting a bunch of uploads of MAAS, when do you expect the first upload to happen and what version (alpha? beta?) will that be?

Then how often do you expect to upload new releases and when do you plan on having 2.0 final into the archive?

I basically just want to make sure that we won't be breaking downstream MAAS users at the last minute with limited to no way to fix things.

Revision history for this message
Andres Rodriguez (andreserl) wrote :

Hi Stephane,

I've updated the bug report. I just wanna be clear with something though. The introduction of the NEW MAAS 2.0 features enhance functionality of MAAS and will not break users using previous releases, as MAAS 2.0 provides full feature parity.

Hope these answer all your questions, if not, please do let me know!

description: updated
description: updated
Revision history for this message
Stéphane Graber (stgraber) wrote :

Ok, I'm assuming you meant "2.0 alpha" in the updated description.

Anyway, sounds fine to me, approved.

Changed in maas (Ubuntu):
status: New → Triaged
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package maas - 2.0.0~alpha1+bzr4736-0ubuntu1

maas (2.0.0~alpha1+bzr4736-0ubuntu1) xenial; urgency=medium

  * New usptream release, 2.0.0 bzr 4736 (LP: #1553261):
    - Deprecate Cluster Controllers in favor of Rack Controllers.
    - Deprecate API 1.0 in favor if API 2.0.
    - DHCP & Rack Controller High Availability.
    - Networking - IP Ranges.
    - Networking - DNS.
    - BMC Model.
  * Rename maas-cluster* to maas-rack* and handle the upgrade path.
  * Fix installation of init scripts and daemon systemd units.
  * Allow 'dhcpd' to access /usr/sbin/maas-provision via
    sudoers file (LP: #1552775)
  * debian/control: Depends on iproute2 instead.

 -- Andres Rodriguez <email address hidden> Mon, 01 Feb 2016 18:18:52 +0100

Changed in maas (Ubuntu):
status: Triaged → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers