Affects Version/s: None
Fix Version/s: PUP 3.4.0
Sprint:Week 2013-09-04 to 2013-09-11, Week 2013-09-11 to 2013-09-18
This can be roughly based off of a combination of:
- Rob Reynolds's work so far on [Vagrant + Windows](https://github.com/ferventcoder/vagrant-windows-puppet)
- [Veewee templates for Win2008 R2 standard x64](https://github.com/jedi4ever/veewee/tree/master/templates/windows-2008R2-serverstandard-amd64-winrm)
- Ryan Gard [Config reference for Windows](https://confluence.puppetlabs.com/pages/viewpage.action?title=How+to+Manually+Create+Virtual+Machine+Templates+for+Windows&spaceKey=DEL) – and ensuring the box is properly dialed for development use
- This box will be for development only, and not for acceptance tests, which will likely require a similar but different configuration
- Current consensus points to building everything into a standard basebox with Packer, and to leave the `vagrant up` as simply a convenient mechanism to map ports, setup shares and configure the virtual environment. This will be the quickest to get up and running. At a later date, it may make sense to provision some application installation with Chocolatey / Puppet – but at this point in time, it's additional ceremony that can break.
- The assumption is that a users `~` directory will be mapped to `/home` under windows
- This requires Vagrant 1.2.6+ on the host machine
- Standard development tools / utils, like Ruby 1.9.3, Sysinternals, Vim, emacs, Sublime and Conemu will be installed on the basebox to make the box feature complete for those who prefer to RDP into the box.
The location for the actual baseboxes should be http://int-resources.ops.puppetlabs.net/vagrant/