Providing the autoinstall config
The autoinstall config is provided via cloud-init configuration, which is almost endlessly flexible. In most
scenarios the easiest way will be to provide user-data via the nocloud data source.
The autoinstall config should be provided under the autoinstall key in the config. For example:
#cloud −c o n f i g
a u t o i n s t a l l :
v e r s i o n : 1
. . .
Running a truly automatic autoinstall
Even if a fully noninteractive autoinstall config is found, the server installer will ask for confirmation before
writing to the disks unless autoinstall is present on the kernel command line. This is to make it harder to
accidentally create a USB stick that will reformat a machine it is plugged into at boot. Many autoinstalls
will be done via netboot, where the kernel command line is controlled by the netboot config – just remember
to put autoinstall in there!
Quick start
So you just want to try it out? Well we have the page for you.
Creating an autoinstall config
When any system is installed using the server installer, an autoinstall file for repeating the install is created
at /var/log/ installer / autoinstall −user−data.
The snap described here does not yet exist
Alternatively there is a snap, autoinstall −editor, that can be used to either edit or create from scratch an
autoinstall config (it is actually mostly the same code as that that runs the installation in interactive mode).
# s t a r t e d i t i n g new c o n f i g f i l e
$ a u t o i n s t a l l −e d i t o r
# dump out t o s t d o u t a c o m p l e t e a u t o i n s t a l l c o n f i g
with d e f a u l t an swe r s
e v e ry w he re
$ a u t o i n s t a l l −e d i t o r −−c r e a t e > my−a u t o i n s t a l l . yaml
# e d i t e x i s t i n g a u t o i n s t a l l c o n f i g
$ a u t o i n s t a l l −e d i t o r my−a u t o i n s t a l l . yaml
307
Do'stlaringiz bilan baham: |