anchor.diff:  
   logging:
     # If needed increase the default logging level to trace REST traffic with IaaS providers. Default is info
  -  level: info
  +  level: debug
     # Default location is <deployment_dir>/bosh_micro_deploy.log
     # file :
   
  
positive.code:       subnet: subnet-d597b993
  </pre>
  
  This `cloud properties` sub-block is IaaS-dependent, because subnets, and other
  keys may differ from IaaS to IaaS.
  
  ### <a id='resources'></a> The resources block ###
  
  The resources block specifies the size of the `persistent_disk`
  to be created and attached to the MicroBOSH VM.
  MicroBOSH stores its data on the persistent disk, so that no data
  is lost when the VM is restarted or when you update MicroBOSH.
  
  `persistent_disk` is specified in megabytes.
  For example, a value of `16384` equates to 16 Gigabytes.
  
  The content of the `cloud_properties` sub-block varies from IaaS to IaaS.
  
  For example:
  
  
negative.code: 
  ### <a id='cloud'></a> The cloud block ###
  
  The cloud block specifies the IaaS you want to use, in the `plugin` attribute.
  Next comes the `properties` sub-block, whose content differs from IaaS to IaaS.
  
  For example:
  
  <pre class="terminal">
  cloud:
    plugin: openstack
    properties:
      openstack:
        auth_url: http://<identity_server>:5000/v2.0
        username: &lt;username&gt;
        api_key: &lt;password&gt;
        tenant: &lt;tenant&gt;
        region: &lt;region&gt; # Optional
        default_security_groups: ["ssh", "bosh"]
        default_key_name: &lt;microbosh_keypair&gt;
        private_key: &lt;path_to_microbosh_keypar_private_key&gt;
  </pre>
  
  ### <a id='apply'></a> The apply_spec block ###
  
  The content of the `apply_spec` block varies from IaaS to IaaS.
  
  In this block you specify configuration information for
  MicroBOSH components like the Director and the Health Monitor, as
  well as for elements of infrastructure like the vCenter in vSphere.
  
  MicroBOSH has a nameserver component called `powerDNS`.
  If, after you deploy MicroBOSH, you use it deploy other software,
  MicroBOSH will create VMs as it deploys that software.
  VMs that MicroBOSH creates use the powerDNS on their parent VM to resolve IP addresses.
  
  In the `dns` sub-block of the `apply_spec` block, you specify the IP of the nameserver,
  or recursor, that powerDNS should use to resolve names external to its domain.
  
  For example:
  
  <pre class="terminal">
  apply_spec:
    properties:
      director:
        max_threads: 3
      hm:
        resurrector_enabled: true
      ntp:
        - 0.north-america.pool.ntp.org
        - 1.north-america.pool.ntp.org
      dns:
        recursor: &lt;ip_for_dns&gt;
  </pre>
  
  ## <a id="creating"></a> How to Create a Manifest ##
  
  You can modify example manifests to suit your purposes.
  Another approach is to use a tool like [spiff](https://github.com/cloudfoundry-incubator/spiff)
  to create a manifest.
  
  ## <a id="examples"></a> Example Manifests ##
  
  These examples are designed to illuminate what each IaaS requires in a MicroBOSH deployment manifest.
  
  ### <a id="ex-aws"></a> AWS ###
  
  You can adapt this example to your environment settings.
  
  ~~~yaml
  name: microbosh-aws
  
  logging:
    # If needed increase the default logging level to trace REST traffic with IaaS providers. Default is info
    level: debug
    # Default location is <deployment_dir>/bosh_micro_deploy.log
    # file :
  
  network:
    type: dynamic
    vip: x.x.x.x    #Change this to the allocated IP address from Step 2
  
  resources:
    persistent_disk: 20000
    cloud_properties:
      instance_type: m1.small
      availability_zone: us-east-1a
  
  cloud:
    plugin: aws
    properties:
      aws:
        access_key_id: <access_key_id>
        secret_access_key: <secret_access_key>
        default_key_name: bosh
        default_security_groups: ["bosh"]
        ec2_private_key: ~/.ssh/bosh
        ec2_endpoint: ec2.us-east-1.amazonaws.com
        region: us-east-1
  
  apply_spec:
    agent:
      blobstore:
        address: x.x.x.x    #Change this to the allocated IP address from Step 2
      nats:
        address: x.x.x.x    #Change this to the allocated IP address from Step 2
    properties:
      registry:
        address: x.x.x.x    #Change this to the allocated IP address from Step 2
  ~~~
  
  ### <a id="ex-openstack"></a> OpenStack ###
  
  You can adapt this example to your environment settings.
  
  ~~~yaml
  ---
  name: microbosh-openstack
  
  logging:
    # If needed increase the default logging level to trace REST traffic with IaaS providers. Default is info
    level: debug
    # Default location is <deployment_dir>/bosh_micro_deploy.log
    # file :
  
  network:
    type: manual
    vip: <allocated_floating_ip> # Optional
    ip: <tatic_ip>
    cloud_properties:
      net_id: <network_uuid>
  
  resources:
    persistent_disk: 16384
    cloud_properties:
      instance_type: <flavor_name>
  
  cloud:
    plugin: openstack
    properties:
  