Rename devbox-photon to devbox

Change-Id: Idfc27440b5df5a0e066d58e6f3140f4ac273cf30

Author: achandrasekar

README.md

@@ -22,7 +22,7 @@ If you're looking to play with the code, keep reading.
 
 The product is arranged in a single repository, with subdirectories arranged by language. See the individual READMEs for instructions on building the code.
 
-* [Devbox](devbox-photon/README.md): Devbox uses [Vagrant](http://vagrantup.com) to create a small standalone deployment of Photon Controller for test purposes.
+* [Devbox](devbox/README.md): Devbox uses [Vagrant](http://vagrantup.com) to create a small standalone deployment of Photon Controller for test purposes.
 * [Java](java/README.md): Most of the Photon Controller management plane is written in Java, with many individual services implemented on top of the [Xenon framework](http://vmware.github.io/xenon).
 * [Python](python/README.md): The ESX agent and its test and analysis collateral are implemented in Python.
 * [Ruby](ruby/README.md): The Photon Controller CLI is implemented in Ruby, as are the integration tests for the product.
@@ -38,7 +38,7 @@ If you have not signed our contributor license agreement (CLA), our bot will upd
 All pull requests satisfy the following criteria:
 
 1. Pass **unit tests** according to the instructions in the appropriate language-specific README file.
-2. Pass **integration tests** according to the instructions for [Devbox](devbox-photon/README.md).
+2. Pass **integration tests** according to the instructions for [Devbox](devbox/README.md).
 
 We will run any changes through our own validation process which ensures that both conditions are met, but it's in everyone's interest if you take care of this on your own first.
 

devbox-photon/.gitignore devbox/.gitignoredevbox-photon/.gitignore renamed to devbox/.gitignore

@@ -30,13 +30,13 @@ In order to control the devbox VM, Vagrant needs a plugin for Photon OS. The plu
 
 #### Start and provision devbox
 
-We use Gradle for building and provisioning the devbox. From `/java` or `/devbox-photon`, run:
+We use Gradle for building and provisioning the devbox. From `/java` or `/devbox`, run:
 
 	./gradlew :devbox:up
 
 This will bring up Vagrant, create one VM (two if ENABLE_AUTH is set to `true`), build all service containers, then start them. Your devbox is now ready.
 
-If devbox is being used as a management VM, you need to seed a deployment document into Photon Controller for some system properties. These properties can be set from environment variables (see below). From `/devbox-photon`, run:
+If devbox is being used as a management VM, you need to seed a deployment document into Photon Controller for some system properties. These properties can be set from environment variables (see below). From `/devbox`, run:
 
     ./seed_deployment.sh
 
@@ -89,9 +89,9 @@ If for some reason devbox VM cannot be destroyed via Vagrant command (`vagrant d
 
 Sample output may look like this:
 
-    "devbox-photon_photon_1446051688357_62198" {4b963230-c8b4-434d-b70d-39270373fa65}
+    "devbox_photon_1446051688357_62198" {4b963230-c8b4-434d-b70d-39270373fa65}
 
-Notice the machine ID ("devbox-photon_photon_1446051688357_62198").
+Notice the machine ID ("devbox_photon_1446051688357_62198").
 
 * If the VM is not running, identify it with the following command:
 
@@ -103,15 +103,15 @@ Notice the machine ID ("devbox-photon_photon_1446051688357_62198").
 
 for example:
 
-    vboxmanage controlvm devbox-photon_photon_1446051688357_62198 poweroff
+    vboxmanage controlvm devbox_photon_1446051688357_62198 poweroff
 
 * Unregister the VM (with optional deletion of its artifacts)
 
     `vboxmanage unregistervm <machine ID> [--delete]`
 
 for example:
 
-    vboxmanage unregistervm devbox-photon_photon_1446051688357_62198 --delete
+    vboxmanage unregistervm devbox_photon_1446051688357_62198 --delete
 
 ## Controlling devbox behavior with environment variables
 
@@ -315,4 +315,4 @@ To start everything:
 These start scripts will stop, remove, and restart their respective service containers.
 
 ## Gradle wrapper
-The root of the Gradle project is under `/java`, so a wrapper is provided under `/devbox-photon` that forwards calls to `/java/gradlew`. This is just for the convenience of invoking `./gradlew` from `/devbox-photon` without having to change directories or open another shell.
+The root of the Gradle project is under `/java`, so a wrapper is provided under `/devbox` that forwards calls to `/java/gradlew`. This is just for the convenience of invoking `./gradlew` from `/devbox` without having to change directories or open another shell.

devbox-photon/README.md devbox/README.mddevbox-photon/README.md renamed to devbox/README.md

@@ -33,7 +33,7 @@ vagrant ssh -c "sudo docker cp photon-controller-core:/etc/esxcloud-deployer/ /e
 vagrant ssh -c "sudo mkdir -p /usr/lib/esxcloud/photon-controller-core/"
 vagrant ssh -c "sudo docker cp photon-controller-core:/usr/lib/esxcloud/photon-controller-core/scripts/ /usr/lib/esxcloud/photon-controller-core/"
 
-photon_vm=$(VBoxManage list runningvms | grep devbox-photon_photon | sed 's/"\(.*\)".*/\1/')
+photon_vm=$(VBoxManage list runningvms | grep devbox_photon | sed 's/"\(.*\)".*/\1/')
 
 # removing all docker containers in the vagrant box
 #