anchor.diff:  1. Inside each deployment directory, a directory to contain mainly manifests.
   1. Inside the manifests directory, directories for each product you intend to deploy.
   
  -* For example, you could create a directory structure like this:
  -
  -1. A top-level directory called `deployments-aws`.
  -1. Inside the top-level directory, a directory named `boshtest` that is named for your planned MicroBOSH deployment.
  -1. Inside `boshtest`, a directory named `manifests`.
  -1. Inside `manifests`, a directory named `micro`.
  -
   ### <a id="stemcell"></a> Obtain a stemcell  ###
   
   [Download](http://bosh-artifacts.cfapps.io/) a stemcell that is appropriate for your preferred combination of IaaS and VM type.
  -_Comment about where to download to._
  -
  -* For example, the stemcell for CentOS on AWS is called `light-bosh (aws xen centos)`.
  -"Light BOSH" stemcells are AWS-specific.
  -They are actually just pointers to stemcells that already exist on AWS.
  -Using a light BOSH stemcell spares you from the "uploading a stemcell" step later on.
  -
  +Download to the directory of your choice, and remember its path for later use.
   
   ### <a id="enviro"></a> Set up your local environment   ###
   
  
positive.code: 
  ## <a id="verify"></a> Verifying your Deployment  ##
  
  _Mention that BATS is not needed here, provide a simple sanity check._
  
  
  
  
negative.code: 
      `env | grep BOSH`
  
  ### <a id="manifest"></a> Create the manifest  ###
  
  If you are using an IaaS other than AWS, you need to use a text editor to create a deployment manifest, which is a YAML file named `micro-bosh.yml`.
  