The goal of this page is to gather from every team their needs in term of lab requirements. In Amsterdam we have been using extensively Windriver cloud and while the current Windriver infrastructure will remain in place for Beijing, we need to insure we are provisioning adequate lab resource for Integration testing.
see https://lists.onap.org/pipermail/onap-discuss/2017-November/006619.html
2 flavors of requirements have been so far identified:
- Minimum set for Functional Testing
- Minimum set for geo-Redundant Testing
For each flavor, could you fill out the table below with your estimate. This don't need to be 100% accurate. The goal is the come up with a ballpark estimate so we can budget accordingly. Each row is for one instance of your component. We will take this data an calculate resources needed for "functional test environments" like Integration SB0, SB1 etc and resources needed for H/A and Geo Redundant testing. For HA/Geo Redundant testing provide numbers for each "site" and comment on whether how the numbers change with a two site geo-redundancy (e.g. X2 for Geo Redundancy testing).
HA / Geo-Redundant Testing may not be relevant for all applications (especially those qualified as "Design-Time"), in that case enter NA.
Project Name | Project Tech. Lead | Minimum set for Functional Testing | Minimum set for HA / Geo-Redundant Testing | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| CPU | Mem | Storage | VMs | CPU | Mem | Storage | VMs | Comments | |||
| 1 | A & AI | 4 | 16G | 40G | 2 | 4 | 16G | 80G | 5/10 | 5 VMs for local H/A (2 for application servers, 3 for cassandra cluster). For geo-redundant config, need 5 in each site | |
| 2 | Application Authorization Framework | 4 | 8G | 80G | 2 | 4 | 16G | 100G | 2 | ||
| 3 | APPC | 4 | 8G | 80G | 1 | 4 | 8G | 80G | 5/9 | Per site: 3 app (ODL cluster) /2 DB | |
| 4 | CLAMP | 2 | 2G | 10G | 2 | 2 | 2G | 10G | 2 | ||
| 5 | Common Controller SDK | NA | NA | NA | NA | NA | NA | NA | NA | As a library/framework, CCSDK doesn't run standalone, so does not need its own VMs | |
| 6 | DCAE | 10 | 20G | 100G | 2 | 26/54 | 50G/106G | 200G/500G | 13/20 | Note: 1) the mim for functional testing is for the "lab configuration" to be delivered as part of R2; 2) for HA requirements, the first number is w/o CDAP, the 2nd number is with; 3) geo-red can be HA requirements per site | |
| 7 | DMaaP | 4 8 8 4 4 28 | 16G 16G 32G 16G 16G 98G | 100G 160G 160G 100G 100G 620G | 2 2 2 1 1 8 | 16 8 16 8 8 56 | 32 16G 64G 32G 32G 176G | 200 160G 320G 200G 200G 1TB | 4 2 4 2 2 14 | MR DRPS DRNS DBC Bridge TOTAL | |
| 9 | External API Framework | NA | NA | NA | NA | NA | NA | NA | NA | NA based in Brian F suggestion | |
| 10 | Holmes | 4 | 2G | 10G | 1 | 4 | 2G | 10G | 2 | ||
| 12 | Logging Enhancements Project | 4-8 | 8-16G | 80G | 1 | 8-16 | 16-32G | 160G | 2 | ELK stack | |
| 13 | Microservices Bus | 4 | 16G | 10G | 1 | 4 | 16G | 10G | 2 | ||
| 14 | Modeling | 4 | 8G | 20G | 3 | 4 | 8G | 20G | 4 | ||
| 15 | Multi VIM/Cloud | 4 | 16G | 40G | 4 | 4 | 16G | 40G | 4 | ||
| 16 | ONAP CLI | 1 | 2G | 20G | 1 | 1 | 2G | 20G | 1 | ||
| 17 | ONAP Operations Manager (OOM) | 6 + 114 + (8 to 32) = 128 - 152 | 12G + 268G + 64G = 354G | 3G + 100G + 120G = 223G | 3 + 29 + 1 = 33 | 16 to 64 | 128G | 240G | 2 | OOM as an ONAP Deployment (like the demo project) (OOM itself is infrastructure undercloud) | |
| 18 | ONAP Optimization Framework | ||||||||||
| 19 | Usecase UI | 2 | 2G | 10G | 1 | 2 | 2G | 10G | 2 | ||
| 20 | Policy Framework | 6 | 16G | 10G | 1 | 6 | 16G | 10G | 2 | ||
| 21 | Portal Platform | 2 | 8G | 20G | 1 | 2 | 8G | 20G | 2 | ||
| 22 | SDN-C | 4 | 8G | 80G | 1 | 4 | 8G | 80G | 7/14 | 7 VMs needed for local HA (3 controller tier / OpenDaylight + 2 database tier + 2 web tier). Double that for geo redundancy. | |
| 23 | Service Design & Creation | 8 | 16G | 100G | 1 | 8 | 16G | 100G | 4/8 | for HA we need 4 VM FE/BE/CS/ES and Double that for geo redundancy. | |
| 24 | Service Orchestrator | 4 | 8G | 80G | 1 | 4 | 8G | 80G | 2/4 | 2 VMs for local HA (4 for geo distribution, considering 2 replicas) | |
| 25 | VF-C: Virtual Function Controller | 8 | 16G | 80G | 1 | 8 | 16G | 80G | 2 | ||
| 26 | VID | 2 | 2G | 10G | 1 | 2 | 2G | 10G | 2 | ||
| 27 | VNF SDK | 4 | 4G | 80G | 1 | NA (design time component) | |||||
| 28 | VNF Requirements | NA | NA | NA | NA | NA | NA | NA | NA | As documentation directed to VNF Providers, VNFRQTS does not need run time resources | |
| 29 | VNF Validation (VVP) | ||||||||||