| 2014-02-19 03:08:11 |
Julian Edwards |
bug |
|
|
added bug |
| 2014-02-19 03:08:25 |
Julian Edwards |
bug task added |
|
maas (Ubuntu) |
|
| 2014-02-19 03:08:56 |
Julian Edwards |
bug |
|
|
added subscriber Ubuntu Release Team |
| 2014-02-19 03:09:10 |
Julian Edwards |
maas: status |
New |
Triaged |
|
| 2014-02-19 03:09:11 |
Julian Edwards |
maas: importance |
Undecided |
Critical |
|
| 2014-02-19 23:43:11 |
Julian Edwards |
summary |
FFE: maas support for third party hardware drivers |
FFE: 14.04 features |
|
| 2014-02-19 23:43:16 |
Julian Edwards |
description |
[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. |
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
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. |
|
| 2014-03-03 14:43:58 |
Andres Rodriguez |
summary |
FFE: 14.04 features |
[FFe] Standing FFe for 14.04 features |
|
| 2014-03-03 14:44:25 |
Andres Rodriguez |
description |
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
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. |
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.
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. |
|
| 2014-03-03 14:46:56 |
Andres Rodriguez |
description |
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.
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. |
[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.
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. |
|
| 2014-03-03 14:47:19 |
Andres Rodriguez |
bug task deleted |
maas |
|
|
| 2014-03-03 14:47:26 |
Andres Rodriguez |
maas (Ubuntu): importance |
Undecided |
Critical |
|
| 2014-03-03 14:47:41 |
Andres Rodriguez |
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 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. |
[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.
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. |
|
| 2014-03-12 21:21:39 |
Andres Rodriguez |
maas (Ubuntu): milestone |
|
ubuntu-14.04-beta-2 |
|
| 2014-03-13 11:19:07 |
Anders |
maas (Ubuntu): status |
New |
Confirmed |
|
| 2014-03-20 11:09:06 |
Dave Walker |
maas (Ubuntu): status |
Confirmed |
Incomplete |
|
| 2014-03-27 16:28:25 |
Andres Rodriguez |
summary |
[FFe] Standing FFe for 14.04 features |
[FFe] FFe for 14.04 features |
|
| 2014-03-27 16:28:33 |
Andres Rodriguez |
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 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. |
[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. |
|
| 2014-03-27 16:29:01 |
Andres Rodriguez |
maas (Ubuntu): status |
Incomplete |
New |
|
| 2014-04-01 23:25:45 |
Nobuto Murata |
bug |
|
|
added subscriber Nobuto MURATA |
| 2014-04-02 19:21:44 |
Steve Langasek |
maas (Ubuntu): status |
New |
Confirmed |
|
| 2014-04-02 20:09:17 |
Launchpad Janitor |
branch linked |
|
lp:ubuntu/trusty-proposed/maas |
|
| 2014-04-02 20:20:14 |
Launchpad Janitor |
maas (Ubuntu): status |
Confirmed |
Fix Released |
|
