Due to a ransomware attack, the wiki was reverted to a July 2022 version. . We apologize for the lack of a more recent valid backup.
Purpose:
The purpose of this platform test is to test ONOS on the platform level.
Test Overview:
Objectives:
- Pull latest ONOS (image, tar ball, etc)
- Starting up ONOS
- Form a cluster
- Activate and deactivate applications after startup
Test Suite: PLATdockertest
| Test Case # | Description | Pass/Fail Criteria | Implementation Status |
|---|---|---|---|
| 0 | Pull all docker images and get a list of image tags. | Pass: No duplicate image tags, and image tag list pulled successfully. | FINISHED |
| 1 | Set up test parameters | Pass: Parameters are set and docker service is running. | FINISHED |
| 5 | Pull "onosproject/onos:latest" image from docker repo. (unused) | Pass: Image is pulled successfully. | FINISHED |
| 10 | Start three ONOS containers as standalone ONOS and obtain IPs of all nodes. | Pass: ONOS node IPs are obtained and container successfully started. | FINISHED |
| 110 | Step 1: Check default startup standalone ONOS applications status. | Pass: "drivers" app is in ACTIVE state AND all builtin apps have "INSTALLED" state. | FINISHED |
| Step 2: Form ONOS cluster with all nodes. | Pass: ONOS forms cluster with correct number of nodes. | FINISHED | |
| Step 3: Check cluster startup apps status. | Pass: "drivers" app is in ACTIVE state AND all builtin apps have "INSTALLED" state | FINISHED | |
| Step 4: Activate "proxyarp" and "fwd" apps and check apps status. | Pass: Newly activated apps have "ACTIVE" state. | FINISHED | |
| Step 5: Deactivate "proxyarp" and "fwd" apps and check app status. | Pass: Newly deactivated apps have "INSTALLED state. | FINISHED | |
| 900 | Check ONOS log for exceptions after test. | Pass: Exception check passes. | FINISHED |
| 1000 | Pre/Post-test clean environment: Delete ONOS container (if existing), delete images with <none>:<none> tag (if existing). | Pass: Containers and images do not exist in docker. | FINISHED |