History
Before Frankfurt
Until Frankfurt there were 2 tests
- stability test: vFw (then vFWCL) run continuously
- resilency test: test when we destroy some pods and retest that the use case vFw is still OK (only up to El Alto)
In frankfurt we also consider the stability of the installation through teh Dialy chains
Guilin
The stability tests considered for the release were:
- 1 week stability test based on basic_vm
- 1 day HC verification
- Daily CI Guilin installation chain
See https://docs.onap.org/projects/onap-integration/en/guilin/integration-s3p.html#integration-s3p
Evolution for Honolulu
In Honolulu we would like to revisit the stability/resiliency testing part by introducing automated tests on CI weekly chain.
It means we want to execute tests over a week to verify the resiliency and the stability of the solution during the development life cycle.
Definition of the KPIs
what do we want to test, which figures? Nb of onboardings / instantiations? test duration//
we estimate our needs to < to be discussed/commented/challenged/questioned/...>:
- 10 // service onboarding
- 50 // intsantiation
- ....
Parallel onboarding tests
Description
The goal of this test is to create in parallel several services in the SDC.
We estimate that this number is not very high in the reality of operations because it corresponds to the upload of a new service model, which does not occur frequently.
Environment
Tests executed on a Guilin lab. Reused of the basic_vm with different service names (it means that we recreate all the SDC objects VSP, VF Services).
2 series run several times:
- 5 // onboarding
- 10 // onboarding
The main component used for this test is the SDC (+AAI).
During the test we monitor the ONAP cluster resources through a prometheus/grafana
<graph grafana memory & CPU générale>
<graph grafana memory & CPU SDC>
Results
5 // onboarding
| criteria \ Serie | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | Average |
|---|---|---|---|---|---|---|---|---|---|---|---|
| Success rate (%) | 100 | 100 | 100 | 100 | 100 | 80 | 100 | 100 | 100 | 100 | 98 |
| Min duration | |||||||||||
| Max duration | |||||||||||
| Mean duration | |||||||||||
| Average duration | |||||||||||
| Comments/Errros |
<graph min/max/mean/average = f(serie)
10 // onboarding
| criteria \ Serie | 1 | 2 | 3 | 4 | 5 | Average |
|---|---|---|---|---|---|---|
| Success rate (%) | 100 | 100 | 100 | 100 | 100 | 98 |
| Min duration | ||||||
| Max duration | ||||||
| Mean duration | ||||||
| Average duration | ||||||
| Comments/Errros |
<graph min/max/mean/average = f(serie)
<pour toutes les séries durée =f(time)>
Conclusions
ONAP is able to support 10 parallel onboard, which is what we do expect.
The creation of resources is linear. It means that on serie 10, 9 services have been already created. We could have expected a linear increase of the onboarding duration because the client used for test list several times the services.So the more services in SDC, the bigger the list is. So globally the SDC resources increase continuously because we cannot delete them but it has no direct impact on the onboarding duration.
The duration evolution is not linear and the duration may depend on the cluster status.