[doc-migration] Add user folder for related documents

Change-Id: I7e5f854612130e57e05f4633d9ce3d88c9447785

doc/source/index.rst

@@ -58,10 +58,7 @@ User Documentation
 .. toctree::
    :maxdepth: 1
 
-   dev/cluster-type-definition.rst
-   dev/kubernetes-load-balancer.rst
-   heat-templates
-
+   user/index
 
 Contributor Guide
 =================
@@ -92,5 +89,5 @@ Work In Progress
    :maxdepth: 1
 
    admin/troubleshooting-guide.rst
-   userguide.rst
+   user/index.rst
    admin/configuring.rst

doc/source/user/cluster-type-definition.rst

@@ -1,7 +1,3 @@
-=======================
-Cluster Type Definition
-=======================
-
 There are three key pieces to a Cluster Type Definition:
 
 1. Heat Stack template - The HOT file that Magnum will use to generate a

doc/source/user/heat-templates.rst

@@ -1,7 +1,3 @@
-====================
-Heat Stack Templates
-====================
-
 Heat Stack Templates are what Magnum passes to Heat to generate a cluster. For
 each ClusterTemplate resource in Magnum, a Heat stack is created to arrange all
 of the cloud resources needed to support the container orchestration

doc/source/user/index.rst

@@ -21,6 +21,8 @@ Contents
 #. `Python Client`_
 #. `Horizon Interface`_
 #. `Cluster Drivers`_
+#. `Cluster Type Definition`_
+#. `Heat Stack Templates`_
 #. `Choosing a COE`_
 #. `Native Clients`_
 #. `Kubernetes`_
@@ -34,6 +36,7 @@ Contents
 #. `Image Management`_
 #. `Notification`_
 #. `Container Monitoring`_
+#. `Kubernetes External Load Balancer`_
 
 ===========
 Terminology
@@ -693,16 +696,16 @@ Other operations are not yet supported and the CLI should be used for these.
 Following is the screenshot of the Horizon view showing the list of cluster
 templates.
 
-.. image:: images/cluster-template.png
+.. image:: ../images/cluster-template.png
 
 Following is the screenshot of the Horizon view showing the details of a
 cluster template.
 
-.. image:: images/cluster-template-details.png
+.. image:: ../images/cluster-template-details.png
 
 Following is the screenshot of the dialog to create a new cluster.
 
-.. image:: images/cluster-create.png
+.. image:: ../images/cluster-create.png
 
 
 ===============
@@ -810,6 +813,18 @@ Installing a cluster driver
 *To be filled in*
 
 
+=======================
+Cluster Type Definition
+=======================
+
+.. include:: cluster-type-definition.rst
+
+====================
+Heat Stack Templates
+====================
+
+.. include:: heat-templates.rst
+
 ==============
 Choosing a COE
 ==============
@@ -2794,3 +2809,9 @@ the service is running, the Grafana dashboards can be accessed through port
 
 For both Prometheus and Grafana, there is an assigned *systemd* service
 called *kube-enable-monitoring*.
+
+=================================
+Kubernetes External Load Balancer
+=================================
+
+.. include:: kubernetes-load-balancer.rst

doc/source/user/kubernetes-load-balancer.rst

@@ -1,7 +1,3 @@
-===============================================
-Using Kubernetes external load balancer feature
-===============================================
-
 In a Kubernetes cluster, all masters and minions are connected to a private
 Neutron subnet, which in turn is connected by a router to the public network.
 This allows the nodes to access each other and the external internet.
@@ -28,7 +24,7 @@ configuration required for the external load balancer.  This document describes
 how to use this feature.
 
 Steps for the cluster administrator
-===================================
+-----------------------------------
 
 Because the Kubernetes master needs to interface with OpenStack to create and
 manage the Neutron load balancer, we need to provide a credential for
@@ -85,7 +81,7 @@ this occurs, delete the neutron objects manually (lb-pool, lb-vip, lb-member,
 lb-healthmonitor) and then run cluster-delete again.
 
 Steps for the users
-===================
+-------------------
 
 This feature requires the OpenStack cloud provider to be enabled.
 To do so, enable the cinder support (--volume-driver cinder).
@@ -207,7 +203,7 @@ NOTE: it is not necessary to indicate port :80 here but it is shown to
 correlate with the port that was specified in the service manifest.
 
 How it works
-============
+------------
 
 Kubernetes is designed to work with different Clouds such as Google Compute
 Engine (GCE), Amazon Web Services (AWS), and OpenStack;  therefore, different