...
There is one primary use case and one enabler use case
UC1: Provide for transaction tracing via search or dashboard for distributed transactions across ONAP components - enabled by the logs shipped to the ELK stack - in real time. UC2: Provide for UC1 tracing via standardized logs - ideally via marker/mdc (label/key:value pair) markup |
Logging Alignment before enhancement
...
Pod | Container/service | Tech | URLs | logback | library | dependencies | |||||
---|---|---|---|---|---|---|---|---|---|---|---|
aaf |
| ||||||||||
aai |
| ||||||||||
appc |
| ||||||||||
Deployment Profile
Type | VMs | Total RAM vCores HD | VM Flavor | K8S/Rancher Idle RAM | Deployed | Deployed ONAP RAM | Pods | Max vCores | Idle vCores | HD/VM | HD NFS only | IOPS | Date | Notes deployment post 75min |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Full Cluster (14 + 1) - recommended | 15 | 224G 112 vC 100G/VM | 16G, 8 vCores C5.2xLarge | 187Gb | 102Gb | 248 total 241 onap 217 up 0 error 24 config | 18 | 6+G master | 8.1G | 20181106 | ||||
Single VM (possible - not recommended) | 1 | 432G 64 vC 120G | 256G+ 32+ vCores | Rancher: 13G Kubernetes: 8G Top: 10G | 151Gb | 141Gb | 240 total | 55 | 22 | 108 of 128G | n/a | Max: 550/sec Idle: 220/sec | 20181105 | Tested on 432G/64vCore azure VM - R 1.6.22 K8S 1.11 |
Developer 1-n pods | 1 | 16G | 16/32G 4-16 vCores | 14Gb | 10Gb | 120+G | n/a | AAI+robot only |
Example 15 node (1 master + 14 nodes) OOM Deployment
...
Existing Library Research
Portal/SDK
SO
AAI
Library Selected for Reference Implementation
...