FUNCintent at 11 Nov 2015 05:04:23
commit 6f3f79f7f5edc4f6b0e79ccb1a6f3d8cf9c25e35 (HEAD, origin/onos-1.2, onos-1.2)
Author: Jon Hall [jhall@onlab.us]
AuthorDate: Tue Aug 25 16:22:41 2015 -0700
Commit: Brian O'Connor [bocon@onlab.us]
CommitDate: Thu Sep 3 19:11:53 2015 +0000
ONOS-2801
--
(cherry picked from commit df6a6e4af8eb704529b985e4a9f9b7edbb337703)
Case 1: Constructing test variables and building ONOS package - PASS
This test case is mainly for loading from params file, and pull and build the latest ONOS package
- 1.1 Constructing test variables - PASS
Case 2: Starting up 1 node(s) ONOS cluster - PASS
Set up ONOS with 1 node(s) ONOS cluster
- 2.1 Apply cell to environment - PASS
- 2.2 Creating ONOS package - PASS
- 2.3 Uninstalling ONOS package - PASS
- 2.4 Installing ONOS package - PASS
- 2.5 Starting ONOS service - PASS
- 2.6 Start ONOS cli - PASS
Case 10: Start Mininet topology with OF 1.0 switches - PASS
Start mininet topology with OF 1.0 switches to test intents, exits out if topology did not start correctly
- 10.1 Starting Mininet topology with OF 1.0 switches - PASS
Case 12: Assign switches to controllers - PASS
Assign OF 1.0 switches to ONOS nodes
- 12.1 Assigning switches to controllers - PASS
Case 8: Compare ONOS Topology view to Mininet topology - FAIL
Compare topology elements between Mininet and ONOS
- 8.1 Conmparing Mininet topology to ONOS topology - FAIL
- ONOS incorrectly discovered the topology
Case 13: Discover all hosts - PASS
- 13.1 Discover all hosts using pingall - PASS
Case 1000: Host Intents Test - 1 NODE(S) - OF 1.0 - FAIL
This test case tests Host intents using 1 node(s) cluster;
Different type of hosts will be tested in each step such as IPV4, Dual stack, VLAN etc;
The test will use OF 1.0 OVS running in Mininet
- 1000.1 IPV4: Add host intents between h1 and h9 - FAIL
- Assertion Result for IPV4 host intent with mac addresses
- Initial Pingall Failed
- Link Down Passed
- Link Down Topology State Passed
- Link Down Pingall Failed
- Link Down Intent State Failed
- Link Up Passed
- Link Up Topology State Passed
- Link Up Pingall Failed
- Link Up Intent State Failed
- Remove Intents Passed
- 1000.2 DUALSTACK1: Add host intents between h3 and h11 - FAIL
- Assertion Result for dualstack IPV4 with MAC addresses
- Initial Pingall Failed
- Link Down Passed
- Link Down Topology State Passed
- Link Down Pingall Failed
- Link Down Intent State Failed
- Link Up Passed
- Link Up Topology State Passed
- Link Up Pingall Failed
- Link Up Intent State Failed
- Remove Intents Passed
- 1000.3 DUALSTACK2: Add host intents between h1 and h11 - FAIL
- Assertion Result for dualstack2 host intent
- 1000.4 1HOP: Add host intents between h1 and h3 - FAIL
- Assertion Result for 1HOP for IPV4 same switch
- 1000.5 VLAN1: Add vlan host intents between h4 and h12 - FAIL
- Assertion Result vlan IPV4
- Initial Pingall Failed
- Link Down Passed
- Link Down Topology State Passed
- Link Down Pingall Failed
- Link Down Intent State Failed
- Link Up Passed
- Link Up Topology State Passed
- Link Up Pingall Failed
- Link Up Intent State Failed
- Remove Intents Passed
- 1000.6 VLAN2: Add inter vlan host intents between h13 and h20 - PASS
Case 2000: Point Intents Test - 1 NODE(S) - OF 1.0 - No Result
- 2000.1 NOOPTION: Add point intents between h1 and h9 - FAIL
- Assertion Result for NOOPTION point intent
- Link Down Topology State Passed
- Link Down Intent State Failed
- Link Up Topology State Passed
- Link Up Intent State Failed
- 2000.2 IPV4: Add point intents between h1 and h9 - FAIL
- Assertion Result for IPV4 point intent
- Link Down Topology State Passed
- Link Down Intent State Failed
- Link Up Topology State Passed
- Link Up Intent State Failed
- 2000.3 IPV4_2: Add point intents between h1 and h9 - FAIL
- Assertion Result for IPV4 no mac address point intents
- Link Down Topology State Passed
- Link Down Intent State Failed
- Link Up Topology State Passed
- Link Up Intent State Failed
- 2000.4 SDNIP-ICMP: Add point intents between h1 and h9 - FAIL
- Assertion Result for SDNIP-ICMP IPV4 using TCP point intents