anchor.diff:      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 :
  -
  +~~~
  +
  +#### <a id="openstack-nw"></a>OpenStack networking options ####
  +
  +If you are using [nova-network](), the network block takes the following form:
  +
  +~~~yaml
   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 :
  -
  +  vip: <allocated_floating_ip> # Optional
  +~~~
  +
  +
  +If you are using the [OpenStack Networking](http://www.openstack.org/software/openstack-networking/) component,
  +the network block takes one of two forms, depending on whether you specify dynamic or manual
  +networking.
  +
  +In both cases, use the `net_id` attribute to set the `network_uuid` of the OpenStack network you want to use.
  +You must use an existing Network UUID.
  +You can list your OpenStack networks using the command `quantum net-list`.
  +
  +For dynamic networking, the network block takes the following form:
  +
  +~~~yaml
  +network:
  +  type: dynamic
  +  vip: <allocated_floating_ip> # Optional
  +  cloud_properties:
  +    net_id: <network_uuid>
  +~~~
  +
  +
  +For manual networking, the network block takes the following form:
  +
  +~~~yaml
   network:
     type: manual
     vip: <allocated_floating_ip> # Optional
     ip: <static_ip>
     cloud_properties:
       net_id: <network_uuid>
  -
  +~~~
  +
  +**Note**: Manual networking requires you to set the IP address of the MicroBOSH VM.
  +The IP address you choose must be within the IP range of a subnet set of the network specified in `net_id`.
  +
  +#### <a id="flavors"></a>OpenStack flavors ####
  +
  +OpenStack describes VMs in terms of flavors.
  +You specify the flavor in the `instance_type` attribute of the `cloud_properties` sub-block of the `resources` block.
  +Choose a flavor that has some ephemeral disk as described in [validate your OpenStack](validate_openstack.html).
  +
  +~~~yaml
   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.
  +~~~
  +
  +#### <a id="openstack-cloud-props"></a>OpenStack cloud properties ####
  +
  +The `properties` sub-block of the `cloud` block is where you set the following OpenStack configuration information:
  +
  +* `auth_url` is the [OpenStack identity](http://www.openstack.org/software/openstack-shared-services/) server.
  +* `username`, `api_key` and `tenant` are your OpenStack credentials.
  +* `region` is the OpenStack region (optional).
  +* `default_security_groups` sets the security groups used by Micro BOSH. These security groups must exist before deployment.
  +* `default_key_name` and `private_key` are the key pair used by Micro BOSH. This keypair must exist before deployment.
   
   ~~~yaml
   cloud:
  
positive.code: 
  apply_spec:
    properties:
      vcenter:
        host: <vcenter_ip>
        user: <vcenter_userid>
        password: <vcenter_password>
  
negative.code:       ntp:
          - <ntp_host_1>
          - <ntp_host_2>
       vcenters:	# here, list all vCenters that you want MicroBOSH to know about
         - host: <vcenter_ip>
           user: <vcenter_userid>
           password: <vcenter_password>
  