[config-ref] Convert compute chapter to RST

Change-Id: I053405db6382ad818ae3c9be0b9d0e8d445ab2fd
Implements: blueprint config-ref-rst

doc/config-ref-rst/source/compute.rst

@@ -5,6 +5,10 @@ Compute
 .. toctree::
    :maxdepth: 1
 
+   compute/nova-conf.rst
+   compute/logging.rst
+   compute/authentication-authorization.rst
+   compute/resize.rst
    compute/scheduler.rst
    compute/cells.rst
    compute/conductor.rst
@@ -12,3 +16,17 @@ Compute
    compute/nova-logs.rst
    compute/config-samples.rst
    tables/conf-changes/nova.rst
+
+The OpenStack Compute service is a cloud computing fabric
+controller, which is the main part of an IaaS system.
+You can use OpenStack Compute to host and manage cloud computing systems.
+This section describes the OpenStack Compute configuration options.
+
+To configure your Compute installation,
+you must define configuration options in these files:
+
+* ``nova.conf``. Contains most of the Compute configuration options.
+  Resides in the ``/etc/nova`` directory.
+* ``api-paste.ini``. Defines Compute limits.
+  Resides in the ``/etc/nova`` directory.
+* Related Image service and Identity service management configuration files.

doc/config-ref-rst/source/compute/authentication-authorization.rst

@@ -0,0 +1,17 @@
+==========================================
+Configure authentication and authorization
+==========================================
+
+There are different methods of authentication for the
+OpenStack Compute project, including no authentication.
+The preferred system is the OpenStack Identity service,
+code-named keystone.
+
+To customize authorization settings for Compute, use the configuration
+options documented in the table ":ref:`nova-authentication`".
+
+To customize certificate authority settings for Compute, use the
+configuration options documented in the table ":ref:`nova-ca`".
+
+To customize Compute and the Identity service to use LDAP as a backend,
+refer to the configuration options documented in the table :ref:`nova-ldap`".

doc/config-ref-rst/source/compute/logging.rst

@@ -0,0 +1,9 @@
+=================
+Configure logging
+=================
+
+You can use ``nova.conf`` file to configure where Compute logs events,
+the level of logging, and log formats.
+
+To customize log formats for OpenStack Compute, use the configuration
+option settings documented in the table ":ref:`nova-logging`".

doc/config-ref-rst/source/compute/nova-conf.rst

@@ -0,0 +1,87 @@
+=====================
+Overview of nova.conf
+=====================
+
+The ``nova.conf`` configuration file is an
+`INI file format <https://en.wikipedia.org/wiki/INI_file>`_
+as explained in :doc:`../config-format`.
+
+You can use a particular configuration option file by using the ``option``
+(``nova.conf``) parameter when you run one of the ``nova-*`` services.
+This parameter inserts configuration option definitions from the
+specified configuration file name, which might be useful for debugging
+or performance tuning.
+
+For a list of configuration options, see the tables in this guide.
+
+To learn more about the ``nova.conf`` configuration file,
+review the general purpose configuration options documented in
+the table ":ref:`nova-common`".
+
+.. important::
+
+   Do not specify quotes around nova options.
+
+Sections
+~~~~~~~~
+
+Configuration options are grouped by section.
+The Compute configuration file supports the following sections:
+
+[DEFAULT]
+  Contains most configuration options.
+  If the documentation for a configuration option does not specify
+  its section, assume that it appears in this section.
+[baremetal]
+  Configures the baremetal hypervisor driver.
+[cells]
+  Configures cells functionality. For details,
+  the section called ":doc:`Cells <cells>`".
+[conductor]
+  Configures the ``nova-conductor`` service.
+[database]
+  Configures the database that Compute uses.
+[glance]
+  Configures how to access the Image service.
+[hyperv]
+  Configures the Hyper-V hypervisor driver.
+[image_file_url]
+  Configures additional filesystems to access the Image service.
+[keymgr]
+  Configures the key manager.
+[keystone_authtoken]
+  Configures authorization via Identity service.
+[libvirt]
+  Configures the hypervisor drivers using the
+  Libvirt library: KVM, LXC, Qemu, UML, Xen.
+[matchmaker_redis]
+  Configures a Redis server.
+[matchmaker_ring]
+  Configures a matchmaker ring.
+[metrics]
+  Configures weights for the metrics weigher.
+[neutron]
+  Configures Networking specific options.
+[osapi_v3]
+  Configures the OpenStack Compute API v3.
+[rdp]
+  Configures RDP proxying.
+[serial_console]
+  Configures serial console.
+[spice]
+  Configures virtual consoles using SPICE.
+[ssl]
+  Configures certificate authority using SSL.
+[trusted_computing]
+  Configures the trusted computing pools functionality
+  and how to connect to a remote attestation service.
+[upgrade_levels]
+  Configures version locking on the RPC (message queue)
+  communications between the various Compute services
+  to allow live upgrading an OpenStack installation.
+[vmware]
+  Configures the VMware hypervisor driver.
+[xenserver]
+  Configures the XenServer hypervisor driver.
+[zookeeper]
+  Configures the ZooKeeper ServiceGroup driver.

doc/config-ref-rst/source/compute/resize.rst

@@ -0,0 +1,27 @@
+================
+Configure resize
+================
+
+Resize (or Server resize) is the ability to change the flavor of a server,
+thus allowing it to upscale or downscale according to user needs.
+For this feature to work properly, you might need to configure some
+underlying virt layers.
+
+KVM
+~~~
+
+Resize on KVM is implemented currently by transferring the images between
+compute nodes over ssh. For KVM you need hostnames to resolve properly
+and passwordless ssh access between your compute hosts. Direct access
+from one compute host to another is needed to copy the VM file across.
+
+Cloud end users can find out how to resize a server by reading the
+`OpenStack End User Guide <http://docs.openstack.org/user-guide/
+cli_change_the_size_of_your_server.html>`_.
+
+XenServer
+~~~~~~~~~
+
+To get resize to work with XenServer (and XCP), you need
+to establish a root trust between all hypervisor nodes and
+provide an ``/image`` mount point to your hypervisors dom0.