The feature that I would like in maas to address this is the ability for
the user to provide "installer config" (in addition to user-data). This
installer config would be passed wholesale through maas to curtin (or
d-i). .
This would allow either
a.) the user to provide curtin-config without modi
Something we want to add to MAAS is the idea of recommissioning, i.e.
when a node is released back to MAAS, it runs a cycle that does a bunch
of things to get the machine ready to go out the door again. For
example, reset BIOS settings, erase disks. Like commissioning, a MAAS
admin would be able to
Roderick,
To quote the page you referenced:
| Ubuntu Server (CLI) Installation
| 300 MHz x86 processor
| 192 MiB of system memory (RAM)
| 1 GB of disk space
| Graphics card and monitor capable of 640x480
| CD drive
1GB for server. so 2GB is *twice* the *recommended* (not required)
amo
The official Ubuntu system requirements include 5GB of disk space
(https://help.ubuntu.com/community/Installation/SystemRequirements), so
installing to a 2GB disk is just plain wrong.
This bug report was just bumped in priority because it's similar to
problems being experienced with other configur
Roderick,
fwiw, its not terribly obvious that the 2GB disk is "wrong".
Why would you want your root disk of your OS to be the big one?
instead, use the small one that is sufficient, and put all your data on the
big one.
--
You received this bug notification because you are a member of Ubunt
** Also affects: curtin (Ubuntu)
Importance: Undecided
Status: New
** Changed in: curtin (Ubuntu)
Status: New => Confirmed
** Changed in: curtin (Ubuntu)
Importance: Undecided => Critical
--
You received this bug notification because you are a member of Ubuntu
Server Team, w