[FFe] Feature freeze exception for maas in Quantal

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

Bug Description

Hi,

I'd like a feature freeze exception for the maas package. The maas package contains the successor to the Orchestra provisioning system,and in Quantal continues with the improvements of the MAAS released with Precise, which include cobbler replacement. Approval of uploads to the package should cause minimal disruption for users as:

 * It's only installed optionally.
 * It contains a comprehensive unit tests test suite. Upstream developers use TDD.
 * A CI integration system is being setup to bless every new version of the package for integration in Ubuntu.

Missing feature that are going to land over the forthcoming months:

 * Cobbler Removal (Elimination of maas-provision)
 * MAAS Managed DHCP Server
 * MAAS Managed DNS Server

Related branches

description: updated
Revision history for this message
Dave Walker (davewalker) wrote :

Do we have a list of things that will require either NEW and/or MIR review?

description: updated
summary: - [FFe] Standing feature freeze exception for maas in Quantal
+ [FFe] Feature freeze exception for maas in Quantal
description: updated
Revision history for this message
Scott Kitterman (kitterman) wrote : Re: [Bug 1044367] Re: [FFe] Standing feature freeze exception for maas in Quantal

Also, it looks like Maas has a large number of High/Critical bugs that are
mostly unaddressed. In this stage of the release, I think that's probably
more important. Wouldn't it be better to fix those now and then backport the
new features from "R" when they are ready?

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

Hi Scott,

Some of those MAAS bugs are related to the usage of cobbler and its related DNS/DHCP. This new upstream release drops the usage of cobbler and should be able to fix most of the bugs. This is what we are targetting in Quantal, to be able to backport to Precise.

Cheers

Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package maas - 0.1+bzr971+dfsg-0ubuntu1

---------------
maas (0.1+bzr971+dfsg-0ubuntu1) quantal; urgency=low

  * New upstream release (LP: #1044367)

  [ Julian Edwards ]
  * Fix 02-pserv-config.patch to handle new default tftp directory

  [ Andres Rodriguez ]
  * debian/maas.postinst:
    - include '/MAAS' for DEFAULT_MAAS_URL.(LP: #1033956)
    - Update bzr version to safely upgrade.
  * Add maas-dns package that configures DNS in MAAS (LP: #1030860)
  * Remove cobbler related bits
    - debian/maas.postinst: Drop cobbler configuration
    - debian/maas.install: Drop installation of snippets/preseeds.
    - debian/control:
      + Drop Depends on maas-provision. (LP: #975473)
      + Depends on bind9utils.
      + Depends on python-lockfile (LP: #1037400)
      Add necessary Conflicts/Replaces. Add conflicts to tftpd-hpa and dnsmasq.
      Depends on isc-dhcp-server for maas-dhcp, and syslinux-common.
    - debian/extras/maas-provision: Add missing "$@" (LP: #1040462)
    - debian/patches:
      + 02-pserv-config.patch: Updated. Do not patch cobbler related bits.
        patch tftp config to default.
  * maas-dhcp: Re-add to handle initial configuration of MAAS DHCP server.
  * Allow restart of 'isc-dhcp-server' by adding a sudoers file:
    - debian/extras/99-maas-sudoers: Added.
    - debian/maas.install: Install 99-maas-sudoers
  * Minor improvements on dbconfig-common handling:
    - debian/maas.config: Only call dbc_go when scripts present.
    - debian/maas.postrm: Only call dbc_go when config file exists.
  * debian/maas.maas-celery.upstart: Enable Beat and set scheduler db file.
  * debian/maas-dns.postinst: Set correct permissions. (LP: #1042868)
  * debian/maas-dhcp.config:
    - Ask whether we want to enable DHCP (LP: #1044229)
    - Add debconf question for network interfaces
  * debian/maas.prerm: Stop services before removing database (LP: #1044559)
 -- Andres Rodriguez <email address hidden> Thu, 02 Aug 2012 09:01:43 -0400

Changed in maas (Ubuntu):
status: New → Fix Released
Revision history for this message
Stefano Rivera (stefanor) wrote : Re: [Bug 1044367] Re: [FFe] Feature freeze exception for maas in Quantal

> This bug was fixed in the package maas - 0.1+bzr971+dfsg-0ubuntu1

Hrm. This upload was accepted while the FFe was still pending review.

An upload acceptance accident? Or did someone just forget to comment?

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

Hi Stefano,

This was approved, I guess Daviey forgot to comment on the bug report. You
can check with him.

Cheers.

On Tue, Sep 4, 2012 at 4:48 PM, Stefano Rivera <email address hidden>wrote:

> > This bug was fixed in the package maas - 0.1+bzr971+dfsg-0ubuntu1
>
> Hrm. This upload was accepted while the FFe was still pending review.
>
> An upload acceptance accident? Or did someone just forget to comment?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1044367
>
> Title:
> [FFe] Feature freeze exception for maas in Quantal
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1044367/+subscriptions
>

--
Andres Rodriguez (RoAkSoAx)
Ubuntu Server Developer
MSc. Telecom & Networking
Systems Engineer

Revision history for this message
Dave Walker (davewalker) wrote :

@Stefano. Yes.. Apologies for not adequately commenting.

This was accepted during the beta freeze, whilst not beta critical - it has been accepted as an opportunity target include, rather than spin-centric. It cannot impact non-maas testcases that i can see, so is largely self contained to the package itself. It was shared with me the testing that this package had received and I was satisfied.

Andres committed to driving away any potential regression... even if that mean't a reverting the upload. Therefore, satisfied.

Thanks.

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.