x
/
fuel-ccp-installer
Code Issues Proposed changes

Describe BM nodes pre deploy requirements 

Change-Id: I69137e4f201283e71e2b98aa604ccf834e1d176d
Signed-off-by: Bogdan Dobrelya <bdobrelia@mirantis.com>
This commit is contained in:
Bogdan Dobrelya 2016-09-29 10:59:33 +02:00
parent 10f6da9266
commit 11e179d8ac
1 changed files with 17 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

18
doc/source/quickstart.rst
View File

@ -5,7 +5,7 @@ Kubernetes deployment guide
This guide provides a step by step instruction of how to deploy k8s cluster on
bare metal or a virtual machine.
k8s node requirements
K8s node requirements
=====================
The recommended deployment target requirements:
@ -14,6 +14,18 @@ The recommended deployment target requirements:
- At least 8Gb of RAM per node
- At least 20Gb of disk space on each node.
Configure BM nodes (or the host running VMs) with the commands:
::
sysctl net.ipv4.ip_forward=1
sysctl net.bridge.bridge-nf-call-iptables=0
.. NOTE:: If you deploy on Ubuntu Trusty BM nodes or host running your VM
nodes, make sure you have at least Kernel version 3.19.0-15 installed
and ``modprobe br_netfilter`` enabled. Lucky you, if your provisioning
underlay took care for that! Otherwise you may want to
<persist `http://manpages.ubuntu.com/manpages/xenial/en/man5/sysctl.d.5.html`>_
that configuration change manually.
Admin node requirements
=======================
@ -69,6 +81,10 @@ Create deployment script:
Otherwise, it should take the `local` value.
- ``SLAVE_IPS`` - IPs of the k8s nodes.
.. NOTE:: If you deploy on Ubuntu Trusty BM nodes or host running your VM
nodes, make sure to add ``export CUSTOM_YAML='ipip: true'`` to the
``./deploy-k8s.sh`` file.
Run script:
::