Comment 10 for bug 1281881

Agreed, apologies for not confirming.

Steve, can you recover the upload from rejected?

Thanks
 On 2 Apr 2014 20:31, "Steve Langasek" <email address hidden> wrote:

> It sounds like the MAAS team have answered all of Daviey's questions
> here, and the clock is ticking. It looks like the upload has been ready
> since before beta2, we're now after beta2 and only blocking on release
> team approval. So FFe granted, please upload ASAP.
>
> ** Changed in: maas (Ubuntu)
> Status: New => Confirmed
>
> --
> You received this bug notification because you are a member of Ubuntu
> Release Team, which is subscribed to the bug report.
> https://bugs.launchpad.net/bugs/1281881
>
> Title:
> [FFe] FFe for 14.04 features
>
> Status in “maas” package in Ubuntu:
> Confirmed
>
> Bug description:
> [Rationale]
> MAAS requires the following features to land after the Feature Freeze:
> * support for third party hardware drivers
> * support for tracking which NICs on each node are associated with a
> particular network
> * support for UEFI
> * support for Other Hardware Devices.
>
> For this reason, we are requesting an *Standing* Feature Freeze
> Exception for MAAS' features described above. Uploads will only
> contain the features described above as well as any bugfixes that
> might come out of other features.
>
> Third party hardware drivers
> ============================
> [Description]
> This is related to bug 1281765 and forms the infrastructure to enable
> hardware enablement teams to write drivers for hardware not already
> supported in MAAS.
>
> This is essential work to prevent these teams from blocking on the
> core MAAS development team, and to make writing new drivers an order
> of magnitude quicker and easier.
>
> [Proposed Changes]
> The feature is already half implemented; bi-directional comms between
> clusters and the region controller is now established but further work is
> required to add an API layer between these comms and the driver code.
>
> The API layer will translate the various requirements that a driver
> should provide into calls to the region, and vice versa.
> Additionally, all current code that is part of hardware enablement,
> such as architecture types and power parameter choices, will be moved
> into new driver code that will become part of each cluster controller.
>
> NIC tracking
> ============
> [Description]
> A feature is already landed to support network tracking on Nodes that
> MAAS manages. This needs to be extended to track on which NIC the network
> is available.
>
> This is essential otherwise the existing work is of no use to API
> clients if they cannot know on which NIC the network is to be used.
>
> [Proposed changes]
> The database will gain a link table between MACAddress and Network, and
> the UI will change so that it lets the user link networks against MACs on
> the node rather than the node as a whole. API calls will also change
> accordingly.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1281881/+subscriptions
>
>