Added structure for OPNFV documentation

Having this structure in place is a requirement for passing release
milestone M2. This change does not modify the content of the
current documentation / deployment guide.

Signed-off-by: Georg Kunz <georg.kunz@ericsson.com>
Change-Id: I07e8820901970da1199f4a474161e49f25707ecc
Reviewed-on: https://gerrit.opnfv.org/gerrit/c/kuberef/+/71298
Tested-by: jenkins-ci <jenkins-opnfv-ci@opnfv.org>
Reviewed-by: Michael Pedersen <michaelx.pedersen@intel.com>
Reviewed-by: Sofia Wallin <sofia.wallin@est.tech>

2 files changed, 77 insertions, 0 deletions

diff --git a/docs/release/installation/deployment-guide.rst b/docs/release/installation/deployment-guide.rst
new file mode 100644
index 0000000..0875bcf
--- /dev/null
+++ b/docs/release/installation/deployment-guide.rst
@@ -0,0 +1,60 @@
+===================================
+Welcome to Kuberef's documentation!
+===================================
+
+Introduction
+============
+
+Kuberef aims to develop and deliver a Kubernetes-based reference
+implementation according to CNTT RA-2 in close collaboration with the
+CNTT RI-2 workstream.
+
+The entire implementation is divided into two stages - Host provisioning
+and Kubernetes provisioning.
+
+This guide describes how to get started with a potential RI-2 deployment
+using `Cloud Infra Automation Framework <https://docs.nordix.org/submodules/infra/engine/docs/user-guide.html#framework-user-guide>`_
+for the Host provisioning stage and Intel's `BMRA <https://github.com/intel/container-experience-kits>`_
+for the Kubernetes provisioning stage.
+
+.. note::
+
+    This is just an example of a possible RI-2 deployment. Kuberef aims to
+    support and include other potential hardware and Kubernetes deployers as well. More
+    details can be found in the `Kuberef Wiki <https://wiki.opnfv.org/spaces/viewspace.action?key=KUB>`_.
+
+Infrastructure Prerequisites
+=============================
+
+You need one physical server acting as a jump server along with minimum of two additional
+servers on which RI-2 will be deployed. Please refer to Chapter 3 in CNTT RI-2 Documentation
+for detailed information on the server and network specifications.
+
+Additionally, please make sure that you have KVM installed and set up on your jump server. This
+is needed because the deployment will spin up a VM which will then carry out the host and
+Kubernetes installation.
+
+Deployment
+=============================
+
+Before initiating the deployment, please note the following:
+
+1. Add your configuration templates, ``pdf.yaml`` and ``idf.yaml`` under ``hw_config/<vendor>``.
+
+2. Modify the environmental variables defined in ``deploy.env`` to match your setup.
+
+3. Update ``hw_config/<vendor>/setup_network.sh`` with your correct networking info. This particular
+   script sets up networking on the provisioned nodes after the host provisioning stage is successful.
+
+.. note::
+
+    Depending on your setup, this script might not be needed. #WIP
+
+Once ready, issue the following command to initiate the deployment
+
+.. code-block:: bash
+
+   ./deploy.sh
+
+
+Once the deployment is successful, you will have a fully functional RI-2 setup!
diff --git a/docs/release/installation/index.rst b/docs/release/installation/index.rst
new file mode 100644
index 0000000..fe2d1af
--- /dev/null
+++ b/docs/release/installation/index.rst
@@ -0,0 +1,17 @@
+.. This work is licensed under a Creative Commons Attribution 4.0 International License.
+.. http://creativecommons.org/licenses/by/4.0
+.. (c) OPNFV, Ericsson AB and others.
+
+.. _kubref-releasenotes:
+
+==================================================
+Kuberef Installation Guide
+==================================================
+
+.. toctree::
+   :numbered:
+   :maxdepth: 2
+
+   deployment-guide.rst
+
+Build date: |today|