anchor.diff:  $ bosh stemcells
   No stemcells
   </pre>
  -
   
   ### <a id="release"></a> Upload the Release ###
   
  
positive.code: 
  ### <a id=""></a> Target and log into MicroBOSH ###
  
  Use the `bosh target` command so that the BOSH CLI runs on the MicroBOSH you want to use to deploy software.
  Then log in on the MicroBOSH.
  Run the `bosh vms` command which shows VMs that the (Micro)BOSH has deployed.
  For now, `bosh vms` shows no VMs deployed.
  
  <pre class="terminal">
  $ bosh target 172.16.99.11
  Target set to `embarcadero-microbosh'
  
   |1.9.3-p484| embarcadero in ~/bosh
  $ bosh login admin ********
  Logged in as `admin'
  
   |1.9.3-p484| embarcadero in ~/bosh
  $ bosh vms
  No deployments
  </pre>
  
  ## <a id="deploying"></a> Deploying ##
  
  
  
  ### <a id="stemcell"></a> Upload the Stemcell ###
  
  
negative.code: Deployed `manifest.yml' to `embarcadero-microbosh'
  </pre>
  
  ### <a id="verify"></a> Verify ###
  
  While the output you have seen indicates that deployment was successful,
  you can run some basic checks on your new multi-VM BOSH.
  
  Set your local BOSH CLI to communicate with the new BOSH Director.
  
  <pre class="terminal">
  $ bosh target 172.16.69.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
  Config
               /Users/pivotal/.bosh_config
  
  Director
    Name       bosh2
    URL        https://172.16.69.232:25555
    Version    1.2131.0 (release:bee75ed2 bosh:bee75ed2)
    User       admin
    UUID       d2ad4585-ea92-4652-8c07-1ba6625b9220
    CPI        vsphere
    dns        enabled (domain_name: bosh)
    compiled_package_cache disabled
    snapshots  enabled
  
  Deployment
    not set
  </pre>
  
  
  ## <a id="example-manifest"></a> Manifest for Deploying BOSH with MicroBOSH ##
  
  ~~~yaml
  ---
  