anchor.diff:  These, and the static IPs, are off-limits to BOSH when BOSH needs to dynamically use an IP address for tasks like compilation.
   Always reserve the IP of the MicroBOSH that deploys BOSH.
   
  -### <a id=""></a> Create the manifest ###
  +### <a id="create-manifest"></a> Create the manifest ###
   
   The manifest should incorporate the network configuration information for your IaaS.
   It should also reflect the way you want to orchestrate the deployment across the multiple VMs.
  
positive.code: You need to set up your IaaS instance and collect the networking information that goes in the manifest.
  Then you create the manifest and obtain a release and a stemcell.
  
  ### <a id=""></a> Plan how you want to orchestrate your environment ###
  
  For the sake of this example, let's assume that you have decided to deploy BOSH to an environment with two VMs.
  One reason you might do this is to implement a security architecture where the data-storing parts of BOSH
  
negative.code: 
  The IaaS used in this example is vSphere.
  
  ### <a id="set-iaas"></a> Set up the IaaS ###
  
  Collect the information about your vSphere and vCenter that you need to configure the environment.
  
  