...
| Metric | Min | Full System | Notes | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| vCPU | 8 | 64 recommended (16/32 ok) | The full ONAP system of 85+ containers is CPU and Network bound on startup - therefore if you pre pull the docker images to remove the network slowdown - vCPU utilization will peak at 52 cores on a 64 core system and bring the system up in under 4 min. On a system with 8/16 cores you will see the normal 13/7 min startup time as we throttle 52 to 8/16.
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| RAM | 7g (a couple components) | 55g (75 containers) | Note: you need at least 53g RAM (3g is for Rancher/Kubernetes itself (the VFs exist on a separate openstack). 53 to start and 57 after running the system for a day | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| HD | 60g | 120g+ | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Software | Beijing/Master | Rancher v1.6.14 Kubernetes server 1.8.5, Kubectl client 1.9.2 Docker 17.03.2-ce HELM 2.8.0 on openlab, Rackspace and AWS - as of master 20180124
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Amsterdam | Rancher 1.6.10 (kubectl 1.7.7), Helm 2.3, Docker 1.12, Kubectl 1.7.7 - test downgrade from 1.8.6) |
We need a kubernetes installation either a base installation or with a thin API wrapper like Rancher.
...