Automate the deployment of the VMs

Issue Background

We need to document the creating release procedure

Issue description

Instructions for creating and uploading box and associated files

Clone a new version of the repos and step through the setup on the wiki, cloning the linux-cip repos running a build. Configure the notification email smtp settings.

• Run the webserver and check that the successful build is visible
• Run a health check on a Beaglebone Black verify that it completes successfully - including a notification to the cip-testing-results list (or preferably to the box builder instead?).
• Remove any local email settings from the box

On the VM, edit mybbb.dat to reset IP address to the default 'localhost' (thus matching the wiki instructions) - and add it in that state to the data dictionary. (to avoid a surprise for the user?)

sudo apt-get clean -y
sudo apt-get autoclean -y
cd git-repos/linux-cip
make clean
git clean -dfx
sudo rm -rf /var/lib/lava/dispatcher/slave/tmp/* # if lava is still not clearing this area (if still on 2016-12)
sudo dd if=/dev/zero of=/EMPTY bs=1M
sudo rm /EMPTY

Will also need to clear up ~/work for the initramfs build, and then on the host (in the git board-at-desk-single-dev directory)

for the release
vagrant package --output ../cip_board_at_desk_v0.9.n.box
for betas:
vagrant package --output ../cip_board_at_desk_v0.9.n.beta_YYYY_MM_DD.box 

(replacing YYYY-MM-DD with the box creation date aka ../cip_board_at_desk_v0.9.date +%Y_%m_%d.box as we will be losing the beta)

We will also need to generate a hash of the release and the source code and upload it all to the download area.

**Finally, ** so that we can estimate for the release, we need an accurate record of how long the process takes including the complete upload to all required data to the website.

Acceptance criteria

This procedure needs retaining somewhere or this ticket should be kept open?