...
Hardware Base OS | Openstack Software Configured on Base OS | VMs Deployed by Openstack | Kubernetes Software Configured on VMs | Pods Deployed by Kubernetes | Docker Containers Deployed within a POD |
|---|---|---|---|---|---|
Computer 1 | Controller Node | ||||
| Computer 2 | Compute | VM 1 | k8s-master | ||
| Computer 3 | Compute | VM 2 | k8s-node1 | appc-0 | appc-controller-container, filebeat-onap |
| appc-db-0 | appc-db -container, xtrabackup , | ||||
| Computer 4 | Compute | VM 3 | k8s-node2 | appc-1 | appc-controller-container, filebeat-onap |
| Computer 5 | Compute | VM 4 | k8s-node3 | appc-2 | appc-controller-container, filebeat-onap |
Setting up an OpenStack lab is out of scope for this tutorial. Assuming that you have a lab, you will need to create 1+n VMs: one to be configured as the Kubernetes master node, and "n" to be considered as Kubernetes worker nodes. We will create 3 Kubernetes worker nodes for this tutorial because we want each of our SDN-Cs to appear on a different VM for resiliency.
...
Customize the oom/kubernetes/onap parent chart, like the values.yaml file, to suit your deployment. You may want to selectively enable or disable ONAP components by changing the subchart **enabled** flags to *true* or *false*.
| Code Block |
|---|
ubuntu@k8s-s1-master:/home/ubuntu/#$ vi oom/kubernetes/onap/values.yaml Example: ... robot: # Robot Health Check enabled: true sdc: enabled: false appc: enabled: true so: # Service Orchestrator enabled: false |
...