Include windows 2012 and Virtualbox builder declarations

[dylanmei]

This may not be the direction you were going, but I've added a Windows 2012 and Virtualbox builder declarations. I'm also using Puppet instead of Chef so found myself arranging the scripts differently.

[joefitzgerald]

Thanks for the contribution, Dylan... I will validate on VMware Fusion tonight, but the changes look good. Cheers!

[dylanmei]

Good news, thanks. Cheers

[sneal]

@dylanmei 👍

[joefitzgerald]

@dylanmei Had to make a couple of minor changes to the VMware provisioners, but otherwise all good. Thanks again for the contribution!

@dylanmei @sneal I have been thinking about introducing a build process to generate the .json file for a specific OS / provisioner combination (e.g. Windows 2008 R2 + Puppet vs Windows 2012 + Chef). I think this would help to support many different configurations without having an increasing amount of duplication. Windows Server 2012 R2 will be out any time now, and with Chef / Puppet / No provisioner variants, the number of JSON files we maintain will spiral out of control.

What do you think?

[sneal]

If there's enough duplication between json files then I think that makes a lot of sense. Would it hurt customizability?

[dylanmei]

A template to bootstrap the template. :) Ideally the customizability is covered in provisioning. I could do a lot with a build that did a bare bones Autounattended.xml, installed cygwin, VM tools/additions, and then simply picked up provisioning snippets from a directory.

[joefitzgerald]

@sneal @dylanmei Moved this discussion to #3.