Last Update:
by:
ID | Description | Mode | Prio | Passing Criteria | TestON Test | TestON Case | Roadmap | Current Status (In Progress/Complete) |
| Single instance, distribute core |
|
|
|
|
|
| |
FN-1 | Starting single instance ONOS, install ONOS, start onos-service and obtain all the component (ONOS bench, ONOScli,ONOS instance, Mininet) handles | Reactive |
| check Karaf Log with "onos started" | ProdFunc | CASE 1 | Now | |
FN-2 | Controller assignment to the switches | Reactive |
| Using the command sh ovs-vsctl get-controller {swName} | ProdFunc | CASE 4 | Now | |
FN-3 | Host Discovery before adding intents | Reactive |
| Pingall | ProdFunc | CASE 4 | Now | |
FN-4 | Point Intent Addition (matching on port numbers) | Proactive |
| ping between the hosts | ProdFunc | CASE 4 | Now | |
FN-5 | Host Intent Addition | Proactive |
| ping between the hosts | ProdFunc | CASE 4 | Now | |
FN-6 | Compare ONOS topo & mininet topo | Proactive |
| using STS | ProdFunc | CASE 7,5 | Now | |
FN-7 | Link discovery consistency - | Proactive |
|
| ProdFunc | CASE 7 | Now | |
FN-8 | Switch down discovery | Proactive | High |
|
|
|
| |
FN-9 | Verify Intents with VLAN-id | Proactive | Low |
|
|
| Sprint32 | |
FN-10 | Link Discover using BDDP; Steps:
| ? | Low | ONOS reportes topo matches MN topo | None | None | Sprint32 | |
FN-11 | Rewrite actions in intents | ? | High |
|
|
| Sprint32 | |
FN-12 | Remove previously added intents before adding new type of intents | ? | High | Ping Test |
|
| Sprint32 | |
FN-13 | Point to Point Intent Addition (match on arbitrary fields, may be ip) |
| Medium |
|
|
| Sprint32 | |
FN-14 | Port up/down discovery |
| High | Compare MN topo and ONOS topo |
|
| Sprint32 |