anchor.diff:  Finished	2014-03-07 06:39:52 UTC
   Duration	00:01:40
   
  -Deployed `manifest.yml' to `embarcadero-microbosh'
  +Deployed `manifest.yml' to `boshtest-microbosh'
   </pre>
   
   ## <a id="verify"></a> Verifying the Deployment ##
  
positive.code: 
  Uploading stemcell...
  
  bosh-stemcell: 100% |oooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooo| 558.9MB  39.4MB/s Time: 00:00:14
  </pre>
  
  Run the `bosh stemcells` command to verify that the stemcell you had before is no longer present on your local system,
  because it has been uploaded to MicroBOSH:
  
  <pre class="terminal">
  $ bosh stemcells
  No stemcells
  </pre>
  
  ### <a id="release"></a> Upload the Release ###
  
  <pre class="terminal">
  $ bosh upload release ~/Downloads/bosh-2131.tgz
  
negative.code: While the output you have seen indicates that deployment was successful,
  you can run some basic checks on your new multi-VM BOSH.
  
  Verify that your MicroBOSH has successfully deployed two VMs,
  and that they have the expected IP addresses:
  
  <pre class="terminal">
  $ bosh vms
  Deployment `bosh2'
  
  Director task 33
  
  Task 33 done
  
  +-------------+---------+---------------+---------------+
  | Job/index   | State   | Resource Pool | IPs           |
  +-------------+---------+---------------+---------------+
  | bosh_api/0  | running | default       | 192.168.1.232 |
  | bosh_data/0 | running | default       | 192.168.1.233 |
  +-------------+---------+---------------+---------------+
  
  VMs total: 2
  </pre>
  
  Set your local BOSH CLI to communicate with the new BOSH Director:
  
  <pre class="terminal">
  $ bosh target 192.168.1.232
  Target set to `bosh2'
  Your username: admin
  Enter password: *****
  Logged in as `admin'
  </pre>
  
  Run `bosh status` to verify that everything looks right:
  
  <pre class="terminal">
  $ bosh status
  