Requirements
------------
-+-------------+-----+-------+
-| Machine | CPU | RAM |
-+-------------+-----+-------+
-| Operator | 1 | 1GiB |
-+-------------+-----+-------+
-| Devstack | 1 | 4GiB |
-+-------------+-----+-------+
-| K8s Control | 1 | 1GiB |
-+-------------+-----+-------+
-| K8s Worker | 4 | 20GiB |
-+-------------+-----+-------+
-| TOTAL | 7 | 26GiB |
-+-------------+-----+-------+
++-------------+-----+-------+---------+
+| Machine | CPU | RAM | Storage |
++-------------+-----+-------+---------+
+| Operator | 1 | 1GiB | 32GiB |
++-------------+-----+-------+---------+
+| Devstack | 1 | 4GiB | 32GiB |
++-------------+-----+-------+---------+
+| K8s Control | 1 | 1GiB | 32GiB |
++-------------+-----+-------+---------+
+| K8s Worker | 8 | 64GiB | 64GiB |
++-------------+-----+-------+---------+
+| TOTAL | 11 | 70GiB | 160GiB |
++-------------+-----+-------+---------+
Table above is based on current experience and may be subject to change.
vagrant ssh operator
Although appropriate context is set for `kubectl` on login, when interacting with the cluster the
-`onap` namespace has to be explicitly specified.
+`onap` namespace has to be explicitly specified. Example:
+
+.. code-block:: sh
+ # Operator's machine shell
+ kubectl -nonap get pods
vm_memory = 1 * 1024
vm_memory_os = 4 * 1024
-vm_memory_onap = 20 * 1024
+vm_memory_onap = 64 * 1024
vm_cpu = 1
-vm_cpus = 4
+vm_cpus = 8
vm_box = "generic/ubuntu1804"
vm_disk = 32
vm_disk_onap = 64
SCRIPT
$deploy_onap = <<-SCRIPT
- OVERRIDE="${1:-${HOME}/oom/kubernetes/onap/resources/environments/minimal-onap.yaml}"
+ OVERRIDE="${1:-${HOME}/oom/kubernetes/onap/resources/environments/core-onap.yaml}"
ENV="${2:-#{os_env}}"
export $(cat "$ENV" | xargs)
export KUBECONFIG="${HOME}/.kube/config.onap"
- helm deploy minimal local/onap --namespace onap -f "$OVERRIDE" --verbose --timeout 900
+ helm deploy core local/onap --namespace onap -f "$OVERRIDE" --verbose --timeout 900
SCRIPT
Vagrant.configure('2') do |config|