blob: fabdd27093d7dad2dd1d3f069abe7ef1882977d1 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
|
.. This work is licensed undera Creative Commons Attribution 4.0
.. International License.
.. http://creativecommons.org/licenses/by/4.0
.. Copyright 2018 ONAP
.. index:: Setting Up Full ONAP using Containers
====================================
**Setting Up ONAP using Kubernetes**
====================================
.. _installing-onap-k8s:
**Context**
===========
The recommended ONAP deployment is based on Kubernetes and Docker containers.
This method is also called deployment through OOM.
The following is the recommended component version.
=========== =========
Software Version
=========== =========
Kubernetes 1.11.2
Helm 2.9.1
kubectl 1.11.2
Docker 17.03.x
=========== =========
Creation of Kubernetes cluster is described here:
.. toctree::
:maxdepth: 1
:titlesonly:
../../../../submodules/oom.git/docs/oom_cloud_setup_guide.rst
The ONAP full installation was validated with the following footprint:
- 14 VM (1 rancher, 13 k8s nodes)
- 8 vCPU
- 16 GB RAM
- 160 GB Storage
ONAP installation is described here:
.. toctree::
:maxdepth: 1
:titlesonly:
../../../../submodules/oom.git/docs/oom_quickstart_guide.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.
|
