Configure the xenial vagrant box the same way as the trusty

[christophe]

Currently it's not easy to migrate from the trusty vagrant box to the xenial box because of several differences :
- the vagrant user is not configured (#1569237)
- the virtual box extensions are not installed
- sudo doesn't resolve the hostname (#1561250)
- the disk space is 10GB instead of 40GB (#1580596)

I think that the process that was used to package the trusty box hasn't been used to package the xenial box. It seems the xenial box is a simple packaging of the raw image without any specific configuration for vagrant.

To see what should be done for a vagrant base box : https://www.vagrantup.com/docs/boxes/base.html

[Oliver Chick (oc243)]

The xenial box also doesn't have puppet-common installed, so I have had to insert a (nasty) inline shell to install it from apt-get.

[Marcello Di Marino Azevedo (marcello.dimarino)]

Also, sound support is enabled under Xenial, at Trusty it is disabled.

Both disks are SCSI at Xenial, for Trusty both are SATA.

Why packagers took a very different approach under Xenial?

[John Chittum (jchittum)]

closing due to age

at this point we follow all the basics provided by the base boxes example. `puppet-common` is out of scope for a base deployment.

both Trusty and Xenial are out of standard support.

as for things like disks, differences between major Ubuntu versions is to be expected. This _should_ all be publicly documented in our Ubuntu release notes, as well as public documentation provided by the Public Cloud team