Documentation reorganization and cleanup

This removes empty documentation pages and places the
troubleshooting docs to the top of the docs/source tree. Also
places the pod disruption budget docs to the rest of the
getting-started docs, which are primarily concepts used in
openstack-helm

Change-Id: Ic3f8deefbd873ae5332e14a12351d9967eb22b1b

doc/source/devref/dev-helm/helm-toolkit.rst

@@ -1,3 +0,0 @@
-============
-Helm-Toolkit
-============

doc/source/devref/dev-helm/index.rst

@@ -1,11 +0,0 @@
-Helm development
-================
-
-Contents:
-
-.. toctree::
-   :maxdepth: 2
-
-   helm-toolkit
-   registration
-   tips

doc/source/devref/dev-helm/registration.rst

@@ -1,18 +0,0 @@
-============
-Registration
-============
-
-User
-====
-
-Domain
-======
-
-Host
-====
-
-Service
-=======
-
-Endpoint
-========

doc/source/devref/dev-helm/tips.rst

@@ -1,2 +0,0 @@
-Tips and Tricks
-===============

doc/source/devref/dev-kubernetes/considerations.rst

@@ -1,3 +0,0 @@
-=====================================
-Kubernetes Development Considerations
-=====================================

doc/source/devref/dev-kubernetes/index.rst

@@ -1,9 +0,0 @@
-Kubernetes development
-======================
-
-Contents:
-
-.. toctree::
-   :maxdepth: 2
-
-   considerations

doc/source/devref/getting-started/index.rst

@@ -8,6 +8,7 @@ Contents:
 
    values
    overrides
+   pod-disruption-budgets
    replicas
    images
    resources

doc/source/devref/getting-started/pod-disruption-budgets.rst

@@ -0,0 +1,34 @@
+=====================
+Kubernetes Operations
+=====================
+
+Init-Containers
+===============
+
+Jobs
+====
+
+Pod Disruption Budgets
+======================
+OpenStack-Helm leverages PodDistruptionBudgets to enforce quotas
+that ensure that a certain number of replicas of a pod are available
+at any given time.  This is particularly important in the case when a Kubernetes
+node needs to be drained.
+
+
+These quotas are configurable by modifying the ``minAvailable`` field
+within each PodDistruptionBudget manifest, which is conveniently mapped
+to a templated variable inside the ``values.yaml`` file.
+The ``min_available`` within each service's ``values.yaml`` file can be
+represented by either a whole number, such as ``1``, or a percentage,
+such as ``80%``.  For example, when deploying 5 replicas of a pod (such as
+keystone-api), using ``min_available: 3`` would enfore policy to ensure at
+least 3 replicas were running, whereas using ``min_available: 80%`` would ensure
+that 4 replicas of that pod are running.
+
+**Note:** The values defined in a PodDisruptionBudget may
+conflict with other values that have been provided if an operator chooses to
+leverage Rolling Updates for deployments.  In the case where an
+operator defines a ``maxUnavailable`` and ``maxSurge`` within an update strategy
+that is higher than a ``minAvailable`` within a pod disruption budget,
+a scenario may occur where pods fail to be evicted from a deployment.

doc/source/devref/index.rst

@@ -7,5 +7,3 @@ Contents:
    :maxdepth: 2
 
    getting-started/index
-   dev-helm/index
-   dev-kubernetes/index