Page History

...

commit c1fc0a86754ca93982273fe52c891e588264800f d299036a4d296d41e7af53477eb58f47a27f6745 (HEAD, origin/master, origin/HEAD, master)
Author: Brian O'Connor [bocon@onlab.usCharles Chan [rascov@gmail.com]
AuthorDate: Fri Mon Apr 22 1618 13:3244:41 03 2016 -0700
Commit: Brian O'Connor [bocon@onlabCharles Chan [charles@onlab.us]
CommitDate: Fri Sat Apr 23 22 16:3225:41 26 2016 -0700
Adding maven_coords for SNAPSHOT libs+0000

Segment Routing refactoring

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

...

• 1.1 Create cell file - No Result
• 1.2 Applying cell variable to environment - No Result
• 1.3 Starting Mininet - PASS
• 1.4 Git checkout and pull master - No Result
• 1.5 Using mvn clean install - PASS
• 1.6 Creating ONOS package - PASS
• 1.7 Installing ONOS package - FAIL
ONOS install failed
• PASS
• 1.8 Checking if ONOS is up yet - PASS
• 1.9 Checking ONOS nodes - FAIL
• Nodes check NOT successful
• 1.10 Activate apps defined in the params file - No Result
• 1.11 Set ONOS configurations - FAIL
• Failed to set config
• PASS
• 1.12 App Ids check - FAIL
• Something is wrong with app Ids

...

• 8.1 Comparing ONOS topology to MN topology - FAIL
• ONOS topology don't match Mininet
• 8.2 Hosts view is consistent across all ONOS nodes - FAIL
• ONOS nodes have different views of hosts
• 8.3 Hosts information is correct - FAIL
• Host information is incorrect
• 8.4 Host attachment points to the network - PASS
• 8.5 Clusters view is consistent across all ONOS nodes - FAIL
• ONOS nodes have different views of clusters
• 8.6 There is only one SCC - FAIL
• ONOS shows ERROR SCCs
• PASS
• 8.7 Device information is correct - FAIL
• Device information is incorrect
• 8.8 Links are correct - FAIL
• Links are incorrect
• 8.9 Hosts are correct - FAIL
• Hosts are incorrect
• 8.10 Checking ONOS nodes - FAIL
• Nodes check NOT successful

Case 3: Adding host Intents

...

- FAIL

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 - FAIL
Install fwd failed
• PASS
• 3.2 Check app ids - FAIL
• Something is wrong with app Ids
• 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 - FAIL
• Uninstall fwd failed
• PASS
• 3.5 Check app ids - FAIL
• Something is wrong with app Ids
• 3.6 Add host intents via cli - PASS
• 3.7 Intent Anti-Entropy dispersion - FAIL

Case 4: Verify connectivity by sending traffic across Intents - FAIL

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

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

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

• 5.1 Check that each switch has a master - FAIL
• Some devices don't have a master assigned
• 5.2 Get the Mastership of each switch from each controller - FAIL
• Error in reading roles from ONOS
• 5.3 Check for consistency in roles from each controller - FAIL
• ONOS nodes have different views of switch roles
• 5.4 Get the intents from each controller - FAIL
• Error in reading intents from ONOS
• 5.5 Check for consistency in Intents from each controller - FAIL
• ONOS nodes have different views of intents
• 5.6 Get the flows from each controller - FAIL
• Error in reading flows from ONOS Error looking up host ids