Convert block storage files to RST

- Converted section_ts_no_emulator_x86_64.xml
- Fixed references in keystone_integrate_with_ldap.rst and keystone_integrate_identity_backend_ldap.rst

Change-Id: Id9168f30553e45cfbe63412c4211679e20298a00
Implements: blueprint reorganise-user-guides

doc/admin-guide-cloud-rst/source/blockstorage.rst

@@ -30,3 +30,66 @@ Amazon EC2 Elastic Block Storage (EBS) offering.
 
 .. _`Storage Decisions`: http://docs.openstack.org/openstack-ops/content/storage_decision.html
 .. _`OpenStack Operations Guide`: http://docs.openstack.org/ops/
+
+.. include:: blockstorage_nfs_backend.rst
+.. include:: blockstorage_glusterfs_backend.rst
+.. include:: blockstorage_multi_backend.rst
+.. include:: blockstorage_backup_disks.rst
+
+.. toctree::
+   :hidden:
+
+   blockstorage_nfs_backend.rst
+   blockstorage_glusterfs_backend.rst
+   blockstorage_multi_backend.rst
+   blockstorage_backup_disks.rst
+
+.. TODO (MZ) Convert and include the following sections
+   include: blockstorage/section_volume-migration.xml
+   include: blockstorage/section_glusterfs_removal.xml
+   include: blockstorage/section_volume-backups.xml
+   include: blockstorage/section_volume-backups-export-import.xml
+
+Use LIO iSCSI support
+---------------------
+
+The default mode for the ``iscsi_helper`` tool is ``tgtadm``.
+To use LIO iSCSI, install the ``python-rtslib`` package, and set
+``iscsi_helper=lioadm`` in the :file:`cinder.conf` file.
+
+Once configured, you can use the :command:`cinder-rtstool` command to
+manage the volumes. This command enables you to create, delete, and
+verify volumes and determine targets and add iSCSI initiators to the
+system.
+
+.. TODO (MZ) Convert and include the following sections
+   include: blockstorage/section_consistency_groups.xml
+   include: blockstorage/section_driver_filter_weighing.xml
+   include: blockstorage/section_ratelimit-volume-copy-bandwidth.xml
+   include: blockstorage/section_over_subscription.xml
+
+Troubleshoot your installation
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+This section provides useful tips to help you troubleshoot your Block
+Storage installation.
+
+.. toctree::
+   :maxdepth: 2
+
+   ts_cinder_config.rst
+   ts_vol_attach_miss_sg_scan.rst
+   ts_non_existent_host.rst
+   ts_non_existent_vlun.rst
+   ts_no_emulator_x86_64.rst
+
+
+.. TODO (MZ) Convert and include the following sections
+   include: blockstorage/section_ts_multipath_warn.xml
+   include: blockstorage/section_ts_eql_volume_size.xml
+   include: blockstorage/section_ts_HTTP_bad_req_in_cinder_vol_log.xml
+   include: blockstorage/section_ts_duplicate_3par_host.xml
+   include: blockstorage/section_ts_failed_attach_vol_after_detach.xml
+   include: blockstorage/section_ts_failed_attach_vol_no_sysfsutils.xml
+   include: blockstorage/section_ts_failed_connect_vol_FC_SAN.xml
+

doc/admin-guide-cloud-rst/source/keystone_integrate_identity_backend_ldap.rst

@@ -7,9 +7,9 @@ administrators to use users and groups in LDAP.
 
 .. important::
 
-   For OpenStack Identity Service to access LDAP servers, you must
+   For OpenStack Identity service to access LDAP servers, you must
    define the destination LDAP server in the ``keystone.conf`` file.
-   For more information, see ?.
+   For more information, see Integrate Identity with LDAP.
 
 .. TODO (DC) Add link to keystone_integrate_identity_with_ldap.rst
 

doc/admin-guide-cloud-rst/source/keystone_integrate_with_ldap.rst

@@ -24,15 +24,18 @@ providing user authentication through the LDAP directory.
    For OpenStack Identity service to access LDAP servers, you must
    enable the ``authlogin_nsswitch_use_ldap`` boolean value for SELinux
    on the Openstack Identity server. To enable and make the option
-   persistent across reboots::
+   persistent across reboots:
 
-      # setsebool -P authlogin_nsswitch_use_ldap on
+.. code-block:: console
+
+   # setsebool -P authlogin_nsswitch_use_ldap on
 
 Identity configuration is split into two separate back ends; identity
 (back end for users and groups), and assignments (back end for domains,
 projects, roles, role assignments). To configure Identity, set options
-in the :file:`/etc/keystone/keystone.conf` file. See ? for Identity back end
-configuration examples and ? for assignment back end configuration examples.
+in the :file:`/etc/keystone/keystone.conf` file. See Integrate Identity back
+end with LDAP for Identity back end configuration examples and Integrate
+Assignment back end with LDAP for assignment back end configuration examples.
 Modify these examples as needed.
 
 .. TODO (DC) Add links to keystone_integrate_identity_backend_ldap.rst and
@@ -46,8 +49,7 @@ Modify these examples as needed.
    with SQL or LDAP), or multiple back ends using domain-specific
    configuration files.
 
-To define the destination LDAP server
--------------------------------------
+**To define the destination LDAP server**
 
 Define the destination LDAP server in the  :file:`keystone.conf` file:
 
@@ -72,8 +74,8 @@ Define the destination LDAP server in the  :file:`keystone.conf` file:
       [ldap]
       dumb_member = cn=dumb,dc=nonexistent
 
-Additional LDAP integration settings
-------------------------------------
+**Additional LDAP integration settings**
+
 
 Set these options in the :file:`/etc/keystone/keystone.conf` file for a
 single LDAP server, or :file:`/etc/keystone/domains/keystone.DOMAIN_NAME.conf`

doc/admin-guide-cloud-rst/source/ts_no_emulator_x86_64.rst

@@ -0,0 +1,19 @@
+Cannot find suitable emulator for x86_64
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+Problem
+-------
+
+When you attempt to create a VM, the error shows the VM is in the
+``BUILD`` then ``ERROR`` state.
+
+Solution
+--------
+
+On the KVM host run, ``cat /proc/cpuinfo``. Make sure the ``vme`` and
+``svm`` flags are set.
+
+Follow the instructions in the `enabling KVM
+section <http://docs.openstack.org/kilo/config-reference/content/kvm.html#section_kvm_enable>`__
+of the Configuration Reference to enable hardware virtualization support
+in your BIOS.