You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 26 Next »

Beijing Specific Tests

Test No.

Category

(Stability, Resiliency, ConfigScaleOut, Scalability)

Description

Status

(Not Started, In-Progress, Pass, Fail)

Notes
1StabilityExecute Restart Test for 72 hour periodPassTested against Amsterdam code due to defect APPC-658 which prevents DMaaP messages from being received or sent.  Test results and notes can be found at:  ONAP APPC 72 Hour Stability Test Results
2StabilityExecute Rebuild Test for 72 hour periodPassTested against Amsterdam code due to defect APPC-658 which prevents DMaaP messages from being received or sent.  Test results and notes can be found at:  ONAP APPC 72 Hour Stability Test Results
3StabilityExecute Start Test for 72 hour periodPassTested against Amsterdam code due to defect APPC-658 which prevents DMaaP messages from being received or sent.  Test results and notes can be found at:  ONAP APPC 72 Hour Stability Test Results
4StabilityExecute Stop Test for 72 hour periodPassTested against Amsterdam code due to defect APPC-658 which prevents DMaaP messages from being received or sent.  Test results and notes can be found at:  ONAP APPC 72 Hour Stability Test Results
5Resiliency

Verify that loss of one MYSQL slave instance does not impact DB availability.

Pass (on Carbon ODL)

Pass (on Nitrogen ODL)

Since MariaDB and Galera support is not being introduced in this release, this test involves terminating the one MySQL instance and verifying that Kubernetes brings the instance back up successfully.
6Resiliency

Verify that loss of one APPC controller instance does not impact application availability

Pass (on Carbon ODL)

Pass (on Nitrogen ODL)

Loss of one APPC controller instance does not impact application availability.
7

Scalability

Scale (up or down) MySQL dynamically.FailDynamic scaling for the database is scheduled to be supported with the introduction of MariaDB and Galera in a future release.
8

Scalability

Scale (up or down) APPC controller dynamically.

Pass with issue (on Carbon ODL)

Pass with issue (on Nitrogen ODL)

The APPC controller can be dynamically scaled; however, the ODL cluster is not configured properly after the scaling operation. Based on this issue, it is recommended to use static scaling such that the cluster size is set appropriately at the time of installation to ensure a properly functioning ODL cluster.
9ConfigScaleOut






















Regression Tests

TC No.

Action Heat

OOM

LCM API ProviderAPPC ProviderVia DGOrchestratorDirect to OpenStackThru MultiVIMQuery AAINetConfVia DMaaPStatusNotes

ModifyConfig

N/A







vFW

HealthcheckYes


Yes





Need jar containing simulator with a service running in order to test.

RestartYesYes*Yes
YesYes
Yes
YesPass

RestartYes
Yes

Yes
Yes
Yes
This test is using the Generic_Restart DG designed to allow for VIM.

RestartYesYes*
Yes
Yes
No
NoPass

Restart
Yes*
Yes
Yes



Pass

StopYesYes*Yes
YesYes
Yes
YesPass

StartYesYes*Yes
YesYes
Yes
YesPass

RebuildYesYes*Yes
YesYes
Yes
YesPass

RebuildYesYes*
Yes
Yes
No

Pass

2018-04-26 14:04:12,445 | INFO | p1257028015-1480 | eelf | 401 - appc-common - 1.3.0.SNAPSHOT - - | APPC0120I Rebuild '1' finished with status SUCCESS. Reason: Success


SnapshotYesYes
Yes
Yes
No
NoPartialSnapshot created successfully but the image verification failed due to APPC-869.













*For OOM - APPC MySQL sql_mode differs from the standard OOM MySQL deployment due to restrictions when sql_mode has "only_full_group_by" enabled.  APPC-878
  • No labels