Page History

HAminorityRestart at 21 Sep 20 Oct 2015 0208:3106:4103

commit cba4b63f76550a242af085b79ec272a6a13a47c6 b0e1dd018a160134bc8fdd874a787f2bad3fc6dd (HEAD, origin/onos-1.3, onos-1.3)
Author: Brian O'Connor [bocon@onlabJonathan Hart [jono@onlab.us]
AuthorDate: Fri Wed Sep 18 1423 17:4054:38 11 2015 -0700
Commit: Brian O'Connor [bocon@onlabJonathan Hart [jono@onlab.us]
CommitDate: Fri Thu Sep 18 1424 13:4022:38 23 2015 -0700
Starting snapshot 1.3.1-SNAPSHOT
IntentManager: Don't compile all failed intents on every event

Case 1: Setting up test environment - PASS

...

• 8.1 Comparing ONOS topology to MN - No Result
• 8.2 Collecting topology information from ONOS - PASS
• 8.3 Hosts view is consistent across all ONOS nodes - PASS
• 8.4 Hosts information is correct - PASS
• 8.5 Host attachment points to the network - PASS
• 8.6 Clusters view is consistent across all ONOS nodes - PASS
• 8.7 There is only one SCC - PASS
• 8.8 Device information is correct - PASS
• 8.9 Links are correct - PASS
• 8.10 Checking ONOS nodes - 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 - 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 - PASS
• 3.7 Intent Anti-Entropy dispersion - PASS

...

Case 6: Restart minority of ONOS nodes - PASS

• 6.1 Checking ONOS Logs for errors - No Result
• 6.2 Killing 2 Killing 3 ONOS nodes - PASS
• 6.2 3 Checking if ONOS is up yet - PASS
• 6.3 4 Restarting ONOS main.CLIs - PASS

...