[Bug 1281881] Re: [FFe] Standing FFe for 14.04 features

[Andres Rodriguez]

** Summary changed:

- FFE: 14.04 features
+ [FFe] Standing FFe for 14.04 features

** Description changed:

  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 third party hardware drivers
+  * support for tracking which NICs on each node are associated with a particular network
+  * support for ppc64el
+  * support for UEFI
+  * Support for Other Hardware Devices.
  
  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.

** Description changed:

+ [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 ppc64el
-  * support for UEFI
-  * Support for Other Hardware Devices.
+  * support for ppc64el
+  * 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.

** No longer affects: maas

** Changed in: maas (Ubuntu)
   Importance: Undecided => Critical

** Description changed:

  [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 ppc64el
   * support for UEFI
-  * Support for Other Hardware Devices.
+  * 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.

-- 
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/1281881

Title:
  [FFe] Standing FFe for 14.04 features

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1281881/+subscriptions