![]() ![]() # Display the VirtualBox GUI when booting the machine Sat.vm.network :forwarded_port, guest: 5985, host: 5987, id: "winrm", auto_correct: true We’ll be using VirtualBox since it’s multi-platform and supports hardware virtualisation (that we’ll need).Ĭonfig.vm.box = "ferventcoder/win2008r2-圆4-nocm"ĭev.vm.network "private_network", ip: "192.168.100.10"ĭev.vm.network :forwarded_port, guest: 5985, host: 5985, id: "winrm", auto_correct: trueįat.vm.network "private_network", ip: "192.168.100.11"įat.vm.network :forwarded_port, guest: 5985, host: 5986, id: "winrm", auto_correct: true The Vagrant Fileįirst we need to set up our box. ![]() This 64-bit Windows 2008 installation will suit just fine for running our. For our mini network, we’ll be using ferventcoder/win2008r2-圆4-nocm from Atlas. There are a lot of Vagrant base boxes available online. ![]() Configure Octopus Tentacle for use with our installation.Install Octopus Tentacle for deployment.Create a new Windows Server machine with a valid name.We’ll set up three boxes for testing – Dev (for local, ongoing development), FAT (Factory Acceptance Testing) and SAT (Site Acceptance Testing). Once you have Vagrant installed, you can create a new file at the command line using the command:Īs well as giving instructions for setting up the box, the Vagrant file also allows provisioning using various scripts. The entry point for creating a Vagrant box is through the Vagrantfile. I had planned on using Octopus Deploy to do this so Vagrant seemed like the best choice for getting new machines set up. As part of testing for our new Continuous Integration set-up, I needed to pull together a bunch of machines for testing deployments. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |