COOK-2556 - Change IP of Vagrant VM to avoid conflicts with other coo…

…kbook Vagrant VMs.

All Berkshelf Vagrantfiles spin up on :hostonly network IP of 33.33.33.10 by default. This change will modify the IP of the chef-server Vagrant guest, so that client Vagrant guests can run simultaneously without modification to any files.

README.md

@@ -207,10 +207,12 @@ for a more in depth explanation of available commands.
 The running Chef-Server components are accessible from the host machine
 using the following URLs:
 
-* Web UI: https://33.33.33.10/
-* Version Manifest: https://33.33.33.10/version
+* Web UI: https://33.33.33.50/ (Note: Attempts to hit via straight http will be redirected to the Vagrant guest's internal hostname)
+* Version Manifest: https://33.33.33.50/version
 * Chef Server API (routing requires `X-OPS-USERID` HTTP header being properly
-set): https://33.33.33.10/
+set): https://33.33.33.50/
+
+*Note: It can be helpful to use the host workstation's /etc/hosts file to map 33.33.33.50 to chef-server-berkshelf.*
 
 ## Contribute to and Hack on Chef Server (including Erchef)
 

Vagrantfile

@@ -39,7 +39,7 @@ Vagrant::Config.run do |config|
   # via the IP. Host-only networks can talk to the host machine as well as
   # any other machines on the same network, but cannot be accessed (through this
   # network interface) by any external networks.
-  config.vm.network :hostonly, "33.33.33.10"
+  config.vm.network :hostonly, "33.33.33.50"
 
   # Assign this VM to a bridged network, allowing you to connect directly to a
   # network using the host's network device. This makes the VM appear as another