Blueprint changed by Andres Rodriguez:
Whiteboard set to:
UDS Session Notes:
ARM Support
Support for different ARM flavours is complex
But a lot is shared with the desktop images, if not all
Sub-architecture support should be out of the scope
Minimum requirement is being able to netboot with pxelinux U-Boot emulation and
full IPMI-based system management support.
MAAS requires that ARM servers have a baseline of system management support
IPMI necessary to ARM (no WoL) - but IPMI is planned for Q for all archs anyway.
Dropping/replacing Cobbler dependency
PowerManagement
IPMI
Fence agents
NUT?
Commissioning Environment
Burn-in and hardware exploration tests: what tools?
* bonnie
* stress
* iobench
* checkbox does some of these already could utilize
* checkbox should report back to MAAS, perhaps with an option to report
to central checkbox server
* autotest can run the tests remotely or locally, and also have a bunch of
test cases already
* facter (ruby) takes track of edge cases.
* make sure that you collect enough data for use by juju
* Investigate facter and alternatives
Faster install:
* Use a SquashFS image
* Keep in mind the complexity of a server regarding multiple nics multiple
block storage devices.
Web app UI:
- en masse actions
- overview of the whole MAAS cluster
- command line ui
Start node without Juju:
User Stories:
Assumptions:
Test Plan:
--
MAAS Next Steps
https://blueprints.launchpad.net/ubuntu/+spec/servercloud-q-maas-next-steps
--
Ubuntu-server-bugs mailing list
[email protected]
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
