Current documentation for “MAAS”

To classify a blueprint as documentation, set the Implementation status to “Informational” When the blueprint's Definition status is marked “Approved”, it will appear in this listing.

Debugging failures in MAAS is hard, we should aim so that everything we ship with MAAS - i.e. outside of its core - should work through the API, even debugging tools. Customers - or PES - should not have to perform brain surgery on MAAS to diagnose a tagging issue, for example. Any solution we come up with has to w...
Support for upgrading BIOS and firmware during the commissioning cycle
Plan for wider /easier testing of MAAS with a range of servers. Possibly the easiest is going to be a USB live image which comes up with MAAS all set (providing DHCP, PXE on say) so users can boot it on their laptops attached to a switch, with a single server on the same switch. Ideally it: * looks f...
Support for installing CentOS and VMWare ESXi
Can we use ceph instead of downloading ephemeral images across all clusters
Consider the typical office where many workers leave for the day and leave their PCs switched on overnight. MAAS could re-provision these during non-office hours to use as another resource and then put them back as desktop machines in the morning before the workers arrive in the office.
Diskless Nodes for MAAS
Support for network-mounted root filesystems on nodes
Discuss documentation pain points and missing parts
Discuss alternatives to sphinx
The new user's experience during the first 30 minutes - what can we do to make this a good experience, such as scripted installation scenarios and guided installation.
MAAS is not like a public cloud where there are known locations for the Juju tools, which requires the user to use --upload-tools, or have an internet connection to pull down the tools. We can do better by having MAAS store the juju tools and publish its own simplestreams data for them.
Can we save power by suspending nodes that are not in use, and re-activating them on demand when necessary?
The new Curtin installer is much quicker that d-i but still takes a couple of minutes. Do we need to devise a pre-installation scheme so nodes can be accessed almost instantly?
MAAS currently detects whether it's running on a QEMU instance but ignores all other virtual appliance types. Can we use the imvirt package to improve this?

14 blueprint(s) listed.