http/install-common.sh:
Instead of `--age 12` use `--latest 20` as parameter to `reflector`
which brings down the mirrorlist creation from over two minutes to about
12s.

Fixes #122

http/install-common.sh:
Order pacman-init.service and reflector-init.service before
cloud-final.service, as the latter may install packages using pacman and
will introduce a broken pacman keyring if started simultaneously with
pacman-init.service.
The mirrorlist should be set before cloud-final.service is running, so
that pacman can use it.

.gitlab-ci.yml:
When testing the cloud image using cloud-init:
* Use the `packages` and `runcmd` directives to install packages using
  cloud-init (which is done during `cloud-final.service`).
* Check for packages installed via cloud-init.
* Write a test file to disk and check for its existence.

Fixes #121

cloud-init handles it + most of the "user and groups"-module options is
ignored if the user already exist.

[1] https://cloudinit.readthedocs.io/en/latest/topics/modules.html#users-and-groups

cloud-init is responsible for handling it in the cloud-image.

Fix #89

I'm not sure polkit is needed in the vagrant images, but it is
definitely not needed in the cloud-image.

Using actual VMs to build VMs is slow and error-prone (you need to use
VNC to see what is going on, and booting takes over +110 seconds as we
wait to be sure Arch Linux is ready).

build.sh can build all three images in ~135 seconds (assuming all the
packages is cached), we still need to use a VM for the actually building
in GitLab CI (as that is the only safe way it can be done at the
moment), which is a bit slower (~22 min vs ~13 min (Packer)), but that
isn't really a big issue.

In the future we can hopefully switch to Kate Containers[1] and reduce
the build time significantly.

[1] infrastructure#108

Kristian Klausen authored Feb 23, 2020 and Christian Rebischke committed Feb 24, 2020

Signed-off-by: Kristian Klausen <kristian@klausen.dk>

Kristian Klausen authored Feb 23, 2020 and Christian Rebischke committed Feb 24, 2020

Disabling it by masking 99-default.link works, but it "breaks":
udevadm test-builtin net_setup_link, as a default link configuration
isn't created. Breaking net_setup_link breaks cloud-init, which means
the cloud image doesn't work.
So with this commit we disable it the same way as Debian does[1], by
adding "net.ifnames=0" to the kernels command line.

See also #30

[1] https://salsa.debian.org/openstack-team/debian/openstack-debian-images/blob/fb1d5be0b84895c96f8209f6e7177cf1f6bf1b25/build-openstack-debian-image#L1861

Signed-off-by: Kristian Klausen <kristian@klausen.dk>

Kristian Klausen authored Feb 23, 2020 and Christian Rebischke committed Feb 24, 2020

Signed-off-by: Kristian Klausen <kristian@klausen.dk>

Signed-off-by: Christian Rebischke <chris@nullday.de>

Signed-off-by: Christian Rebischke <chris@nullday.de>

Signed-off-by: Christian Rebischke <chris@nullday.de>

This is supposed to fix #41

.
Vagrant is able to provision boxes, therefore we need to make sure
that the box has finished all Pacman keyring initialization before
Vagrant is able to login via SSH and provision the box.
Signed-off-by: Christian Rebischke <chris@nullday.de>

We need to re-initialize the pacman keyring for every machine,
otherwise every machine would have the same pacman master key. The same
pacman master key opens the possibility for Mitm-attacks.
Signed-off-by: Christian Rebischke <Chris.Rebischke@posteo.de>

added polkit to pacstrap for systemctl poweroff, added sudo to poweroff
command, moved link for systemd-resolved to postinstall.sh

added new postinstall.sh, moved the controllers to postinstall.sh and added the script to vagrant.json