anchor.diff:  
   ### <a id='cloud'></a> The cloud block ###
   
  -The resources block specifies the IaaS you want to use in the `plugin` attribute,
  -and `properties`, whose content differs from IaaS to IaaS.
  +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:
  
positive.code:     ntp:
        - 0.north-america.pool.ntp.org
        - 1.north-america.pool.ntp.org
  </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 ###
  
  ~~~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: AKIAIYJWVDUP4KRESQ
        secret_access_key: EVGFswlmOvA33ZrU1ViFEtXC5Sugc19yPzoWRf
        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 ###
  
  Explanatory comments follow this example.
  
  ~~~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: <static_ip>
    cloud_properties:
      net_id: <network_uuid>
  
  resources:
    persistent_disk: 16384
    cloud_properties:
      instance_type: <flavor_name>
  
  cloud:
    plugin: openstack
    properties:
      openstack:
        auth_url: http://<identity_server>:5000/v2.0
        username: <username>
        api_key: <password>
        tenant: <tenant>
        region: <region> # Optional
        default_security_groups: ["ssh", "bosh"]
        default_key_name: <microbosh_keypair>
        private_key: <path_to_microbosh_keypar_private_key>
  
  apply_spec:
    properties:
      director:
        max_threads: 3
      hm:
        resurrector_enabled: true
      ntp:
        - 0.north-america.pool.ntp.org
        - 1.north-america.pool.ntp.org
  ~~~
  
  Adapt the `micro_bosh.yml` file to your environment settings:
  
  #### <a id="network_properties"></a>Network properties ####
  
  This section sets the network configuration for your Micro BOSH.
  
  If you are using nova-network, adapt the network section with below settings:
  
  ~~~yaml
  network:
    type: dynamic
    vip: <allocated_floating_ip> # Optional
  ~~~
  
  * The `vip` option is optional, and allows you to associate a floating IP address to the Micro Bosh vm in case you want to access it from outside of the vm network. If set, `allocated_floating_ip` **must** be a previously allocated floating ip.
  
  If you are using the new [OpenStack Networking](http://www.openstack.org/software/openstack-networking/) component, adapt the network section with below settings:
  
  1. If your network has DHCP enabled, you can let OpenStack pick an IP address:
  
  ~~~yaml
  network:
    type: dynamic
    vip: <allocated_floating_ip> # Optional
    cloud_properties:
      net_id: <network_uuid>
  ~~~
  
  * The `vip` option is optional, and allows you to associate a floating IP address to the Micro Bosh vm in case you want to access it from outside of the vm network. If set, `allocated_floating_ip` **must** be a previously allocated floating ip.
  * The `net_id` option sets the OpenStack network to use. `network_uuid` **must** be an existing Network UUID (you can list your OpenStack networks using the command `quantum net-list`).
  
  1. If you want to set the Micro Bosh IP address manually:
  
  ~~~yaml
  network:
    type: manual
    vip: <allocated_floating_ip> # Optional
    ip: <static_ip>
    cloud_properties:
      net_id: <network_uuid>
  ~~~
  
  * The `vip` option is optional, and allows you to associate a floating IP address to the Micro Bosh vm in case you want to access it from outside of the vm network. If set, `allocated_floating_ip` **must** be a previously allocated floating ip.
  * The `ip` option sets the IP address to assign to the Micro BOSH vm. `static_ip` **must** be an IP address belonging to the IP range of one of the network subnets set in `net_id`.
  * The `net_id` option sets the OpenStack network to use. `network_uuid` **must** be an existing Network UUID (you can list your OpenStack networks using the command `quantum net-list`).
  
  #### <a id="resources_properties"></a>Resources properties ####
  
  This section sets the resources configuration for your Micro Bosh.
  
  ~~~yaml
  resources:
    persistent_disk: 16384
    cloud_properties:
      instance_type: <flavor_name>
  ~~~
  
  
  * The `instance_type` set the OpenStack flavor used for the Micro BOSH vm. The `flavor_name` **must** have ephemeral disk (check the [validate your OpenStack](validate_openstack.html) guide)
  
  #### <a id="cloud_properties"></a>Cloud properties ####
  
  This section sets the cloud configuration for your Micro BOSH.
  
  ~~~yaml
  cloud:
  
negative.code: 
  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 :
  
  