Page History

...

23

commit 33ab26928c6c002357d967ca7ff56f1ab1fd2af0 a8d896cbb614b89c99a53241685d4fcb1afde6a3 (HEAD, origin/master, origin/HEAD, master)
Author: Simon Hunt [simon@onlab.usDaniel Park [dan.park@sk.com]
AuthorDate: Mon Fri Aug 29 2126 14:0831:42 33 2016 -0700+0900
Commit: Simon Hunt [simon@onlab.usDaniel Park [dan.park@sk.com]
CommitDate: Mon Aug 29 21:08:42 2016 -0700
Fix glyph names.Thu Sep 1 13:37:02 2016 +0900

[ONOS-5114] Fix to send icmp packet from vm to gateway when floating is assigned

<iframe src="https://onos-jenkins.onlab.us/job/HAfullNetPartition/plot/Plot-HA/getPlot?index=21&width=500&height=300"noborder="0" width="500" height="300" scrolling="yes" seamless="seamless"></iframe>

...

• 21.1 Assign mastership of switches to specific controllers - PASS
• 21.2 Check mastership was correctly assigned - PASS

Case 3: Adding host Intents -

...

PASS

Discover hosts by using pingall then assign predetermined host-to-host intents. After installation, check that the intent is distributed to all nodes and the state is INSTALLED

• 3.1 Install reactive forwarding app - PASS
• 3.2 Check app ids - FAIL
Something is wrong with app Ids
• PASS
• 3.3 Discovering Hosts( Via pingall for now ) - FAIL
• Reactive Pingall failed, one or more ping pairs failed
• PASS
• 3.4 Uninstall reactive forwarding app - PASS
• 3.5 Check app ids - PASS
• 3.6 Add host intents via cli - FAIL
• Error looking up host ids
• PASS
• 3.7 Intent Anti-Entropy dispersion - FAIL PASS

Case 4: Verify connectivity by sending traffic across Intents -

...

PASS

Ping across added host intents to check functionality and check the state of the intent

• 4.1 Check Intent state - FAIL
• Intents are not all in INSTALLED state
• PASS
• 4.2 Ping across added host intents - FAIL
• Intents have not been installed correctly, pings failed.
• PASS
• 4.3 Check leadership of topics - PASS
• 4.4 Wait a minute then ping again - FAIL
Intents have not been installed correctly, pings failed.
• PASS

Case 5: Setting up and gathering data for current state -

...

PASS

• 5.1 Check that each switch has a master - PASS
• 5.2 Get the Mastership of each switch from each controller - PASS
• 5.3 Check for consistency in roles from each controller - PASS
• 5.4 Get the intents from each controller - PASS
• 5.5 Check for consistency in Intents from each controller - PASS
• 5.6 Get the flows from each controller - PASS
• 5.7 Check for consistency in Flows from each controller - PASS
• 5.8 Get the OF Table entries - No Result
• 5.9 Start continuous pings - No Result
• 5.10 Collecting topology information from ONOS - No Result
• 5.11 Host view is consistent across ONOS nodes - PASS
• 5.12 Each host has an IP address - PASS
• 5.13 Cluster view is consistent across ONOS nodes - FAIL
• ONOS nodes have different views of clusters
• PASS
• 5.14 Cluster view correct across ONOS nodes - FAIL
• ONOS shows 11 SCCs
• PASS
• 5.15 Comparing ONOS topology to MN - PASS
• 5.16 Device information is correct - FAIL
• Device information is incorrect
• PASS
• 5.17 Links are correct - PASS
• 5.18 Hosts are correct - PASS

Case 14: Start Leadership Election app - PASS

• 14.1 Install leadership election app - PASS
• 14.2 Run for election on each node - PASS
• 14.3 First node was elected leader - PASS

Case 16: Install Primitives app - PASS

...

• 16.1 Install Primitives app - PASS

...

Case 61: Partition ONOS nodes into two distinct partitions - PASS

...

• 61.1 Checking ONOS Logs for errors - No Result
• 61.2 Partitioning ONOS nodes - PASS
• 61.3 Sleeping 60 seconds - No Result