diff options
| author |   Eric Debeau <eric.debeau@orange.com> | 2019-05-22 07:37:45 +0000 |
|---|---|---|
| committer | Eric Debeau <eric.debeau@orange.com> | 2019-05-22 07:40:40 +0000 |
| commit | 4378efdf61bcf5c901690e2acf39a5bfc9d61003 (patch) | |
| tree | 6636228dcb0d56dbf9d3663bdd61f1350cf848b8 /docs/guides/onap-developer/settingup/index.rst | |
| parent | b18b9bff9ac093490c36fe86cfcea49e7cfef6ab (diff) | |
Update SettingUP
Upadte ONAP footprint
Update Components versions
Remove Heat installation
Remove individual installation
Issue-ID: DOC-427
Signed-off-by: Eric Debeau <eric.debeau@orange.com>
Change-Id: I85e720a9a27fc17b3ebc63e04d76beace4da3117
Diffstat (limited to 'docs/guides/onap-developer/settingup/index.rst')
| -rw-r--r-- | docs/guides/onap-developer/settingup/index.rst | 46 |
1 files changed, 20 insertions, 26 deletions
diff --git a/docs/guides/onap-developer/settingup/index.rst b/docs/guides/onap-developer/settingup/index.rst index 2b9f8b133..f1724d4c3 100644 --- a/docs/guides/onap-developer/settingup/index.rst +++ b/docs/guides/onap-developer/settingup/index.rst @@ -25,17 +25,21 @@ The following is the recommended component version. =========== ========= Software Version =========== ========= - Kubernetes 1.11.5 - Helm 2.9.1 - kubectl 1.11.5 - Docker 17.03.x + Kubernetes 1.13.5 + Helm 2.12.3 + kubectl 1.13.5 + Docker 18.09.5 =========== ========= The ONAP full installation is validated with the following footprint: - - 14 VM (1 Rancher, 13 K8s nodes) - - 8 vCPU - - 16 GB RAM - - 160 GB Storage + +.. csv-table:: Validated installation footprint + :widths: 3,5,10 + + VM number, VM flavor, VM role + 12, 16 GB RAM - 8 vCPUs, Running the K8S worker role + 3, 8 GB RAM - 4 vCPUs, Running the K8S controller role + 1, 8 GB RAM - 4 vCPUs, Running the shared NFS server for /dockerdata-nfs/ Installation ------------ @@ -64,6 +68,14 @@ Alternative way of offline ONAP installation is described here: ../../../../submodules/oom/offline-installer.git/docs/index.rst +.. note:: + Prior to deployment of ONAP, there is no need to download manually any Docker container. + The OOM deployment takes care to automatically download the Docker containers. + + It is also possible to deploy a subset of ONAP components on a single VM. + The VM flavor to be used depends on the number of ONAP components to be + deployed. + NodePorts --------- @@ -91,21 +103,3 @@ Kubernetes command: kubectl get svc -n onap -o go-template='{{range .items}}{{range.spec.ports}}{{if .nodePort}}{{.nodePort}}{{.}}{{"\n"}}{{end}}{{end}}{{end}}' - -.. note:: - Prior to deployment of ONAP, there is no need to download manually any Docker container. - The OOM deployment takes care to automatically download the Docker containers. - - It is also possible to deploy a subset of ONAP components on a single VM. - The VM flavor to be used depends on the number of ONAP components to be - deployed. - -.. note:: - For test purposes, it is possible to use other installations: - -.. toctree:: - :maxdepth: 1 - :titlesonly: - - onap_heat.rst - onap_individual.rst |