Differences between revisions 29 and 30
⇤ ← Revision 29 as of 2015-06-11 10:42:29 →
Size: 2618
Editor: EmmanuelKasper
Comment:
← Revision 30 as of 2015-06-21 15:09:17 → ⇥
Size: 2624
Editor: EmmanuelKasper
Comment:
Deletions are marked like this. Additions are marked like this.
Line 25: Line 25:
See [[Cloud/RebuildVagrantBaseBoxes]] to build the boxes yourself or extend them. See [[Teams/Cloud/RebuildVagrantBaseBoxes]] to build the boxes yourself or extend them.

Contents

  1. General guidelines
  2. Current Status
    1. Content
    2. Build process
    3. DFSG
    4. Security
    5. Debian account on Atlas
  3. Todo list
  4. People Involved

General guidelines

This is a Work in Progress attempt to build official Debian base boxes for Vagrant that shall be available in Atlas, the vagrant cloud backend, and maybe via debian-cd.

Current Status

Content

Standard Debian system, as created by the Debian Installer (all packages with priority required, important, standard), with the following Vagrant specific enhancements:

  • ?Chef and Puppet provisioners, python-apt for ?Ansible, installed with our the preseed file we use

  • vagrant unix user, setup according to Upstream recommendations

  • Speed improvements, such as tweak sshd to prevent DNS resolution (speed up logins) and remove 5s grub timeout to speed up booting

  • Virtual Box Guest additions, build with ?DKMS using the virtualbox-guest-additions-iso package

  • Disk size improvement, such as removing kernel-headers and build-essential after the DKMS step, filling swap with nulls before packaging

Build process

The boxes are currently with Packer from the following git repository http://anonscm.debian.org/cgit/cloud/debian-vm-templates.git/ and uploaded to Hashicorps's Atlas.

See ?Teams/Cloud/RebuildVagrantBaseBoxes to build the boxes yourself or extend them.

DFSG

The build process requires the non-free virtualbox-guest-additions-iso package, but Templates, Builder, and installed packages are DFSG compliant.

Security

When using vagrant init debian/jessie64, boxes are downloaded via HTTPS, and then checksummed from a md5sum stored in Atlas.

For end to end verification, vagrant has also built-in checksumming support, so if checksums of the boxes are available on a separate site, this coud be used like: 

vagrant box add --checksum 00e88116f98368a25b73018dac9478f2 --checksum-type md5 http://cloud-images.debian.org/wheezy64 debian-780-wheezy.box

Debian account on Atlas

Currently owned by EmmanuelKasper and AntonioTerceiro will be shared in the future with JanNiggemann.

Todo list

We use this trello board: https://trello.com/b/lVRI6QJt/offical-debian-vagrant-base-boxes

People Involved

JanNiggemann, EmmanuelKasper