[FFe] MAAS New 1.7 Upstream Release

Bug #1370628 reported by Andres Rodriguez
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
maas (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

We would like to request a Feature Freeze for MAAS 1.7.

In Utopic, we successfully released MAAS 1.7 Beta 1. That release included a preview of some of the new upcoming features. It is important to have this new release, because apart from having various bug fixes for 1.7beta1, in includes the completion of the various features in 1.7.

MAAS 1.7 Final release will include:

- Finish base support for IPv6.
  * Allow machines to be deploying with IPv6 addresses.
  * MAAS runs its own DHCPv6.

- Finish Robustness.
  * This includes the re-definition of the machine lifecycle in MAAS.
    (MAAS now tracks when a machine is owned, installing, installed or
    failed install).
  * Robust power actions (MAAS no longer fires and forgets)
  * Power status tracking (MAAS now tracks the power status of a machine
    regardless of the state it is in)
  * Disk wiping (can wipe the disks if the user wishes so)

- Finish removal of the usage of Celery in favor of using twisted RPC.
  * Completely uses Twisted RPC instead of Celery for communication
    between Region/Cluster and performing actions.
  * Reduces the dependencies. We no longer depend on Celery, Rabbitmq,
    txlonpoll.
  * Reduces the amount of MAAS daemons.

- Finish new Image Store and Syncing.
  * MAAS Region can now sync images and spread them over to the clusters.
  * Allow's offline operation.
  * Allow's uploading custom images or other OS images.

- Finish support for Third Party OS.
  * Supports other OS's (CentOS/Windows).
  * Support custom Images/OS.

description: updated
description: updated
description: updated
description: updated
description: updated
description: updated
description: updated
Revision history for this message
Adam Conrad (adconrad) wrote :

Can I get a diff here for review? The changelog is helpful, but I'd like to see the general impact before I say "yes".

Revision history for this message
Steve Langasek (vorlon) wrote :

From discussions on IRC, I believe this FFe is blocked by the corresponding FFe on psycopg2, https://bugs.launchpad.net/ubuntu/+source/psycopg2/+bug/1366104

Revision history for this message
Andres Rodriguez (andreserl) wrote :
Revision history for this message
Scott Kitterman (kitterman) wrote : Re: [Bug 1370628] Re: [FFe] MAAS New 1.7 Upstream Release

Does this still required the psycopg2 change?

Revision history for this message
Adam Conrad (adconrad) wrote :

I'm not convinced the two FFes are actually tied to each other, but some confirmation from the MaaS team would be nice.

ie: I don't see why this new MaaS version would suddenly be more or less broken with or without the psycopg2 change.

Revision history for this message
Adam Conrad (adconrad) wrote :

@Andres: A debdiff from utopic to utopic might have been easier to review than the 7MB (!) diff from trusty. :P

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

He he oops! I'll attach one once o get my hands to a computer!
On Oct 8, 2014 6:45 PM, "Adam Conrad" <adconrad@0c3.net> wrote:

> @Andres: A debdiff from utopic to utopic might have been easier to
> review than the 7MB (!) diff from trusty. :P
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1370628
>
> Title:
> [FFe] MAAS New 1.7 Upstream Release
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1370628/+subscriptions
>

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

These two FFe's are not tied together. The psycopg issue only affects MAAS
by preventing it from uploading large objects to the database (larger than
2gb). In MAAS terms it prevents from uploading OS images larger than 2gb,
that don't affect Ubuntu deployments, but do affect third part OS image
upload.
On Oct 8, 2014 6:45 PM, "Adam Conrad" <adconrad@0c3.net> wrote:

> I'm not convinced the two FFes are actually tied to each other, but some
> confirmation from the MaaS team would be nice.
>
> ie: I don't see why this new MaaS version would suddenly be more or less
> broken with or without the psycopg2 change.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1370628
>
> Title:
> [FFe] MAAS New 1.7 Upstream Release
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1370628/+subscriptions
>

Revision history for this message
Scott Kitterman (kitterman) wrote :

On Wednesday, October 08, 2014 17:28:13 you wrote:
> These two FFe's are not tied together. The psycopg issue only affects MAAS
> by preventing it from uploading large objects to the database (larger than
> 2gb). In MAAS terms it prevents from uploading OS images larger than 2gb,
> that don't affect Ubuntu deployments, but do affect third part OS image
> upload.

Does the proposed upload guard against use of objects larger than 2GB to avoid
crashing pyscopg2? Given we're unlikely to go forward with the psycopg2
change this cycle, it'd make sense to protect against use off excessively large
objects instead of just exploading.

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

Sorry for the late reply but have been traveling.

MAAS by default guards against any upload regardless of its size. Nothing will crash when trying to upload an image.

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

$ rmadison maas
 maas | 0.1+bzr482+dfsg-0ubuntu1 | precise | source, all
 maas | 1.2+bzr1373+dfsg-0ubuntu1~12.04.6 | precise-security | source, all
 maas | 1.2+bzr1373+dfsg-0ubuntu1~12.04.6 | precise-updates | source, all
 maas | 1.5+bzr2252-0ubuntu1 | trusty | source, all
 maas | 1.5.4+bzr2294-0ubuntu1.2 | trusty-security | source, all
 maas | 1.5.4+bzr2294-0ubuntu1.3 | trusty-updates | source, all
 maas | 1.7.0~beta8+bzr3272-0ubuntu1 | utopic | source, all
 maas | 1.7.0~beta8+bzr3272-0ubuntu1.2 | utopic-security | source, all
 maas | 1.7.0~beta8+bzr3272-0ubuntu1.2 | utopic-updates | source, all
 maas | 1.7.1+bzr3341-0ubuntu1 | vivid | source, all

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

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.