Page History

...

commit 98ffca81bf4e82d772f4bdab6ca98087d9efe932 5c73fd92923601297084af7debc43ee4a84cf6e7 (HEAD, origin/master, origin/HEAD, master)
Author: Sho SHIMIZU [sshimizu@us.fujitsu.com]
AuthorDate: Mon Fri May 8 17:11 08:39:24 46 2015 -0700
Commit: Gerrit Code Review [gerrit@onlabThomas Vachuska [tom@onlab.us]
CommitDate: Mon May 11 1620:1429:19 48 2015 +0000
Save memory consumption by avoding unnecessary instantiation
Implement add() and subtract() methos in Bandwidth

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

...

• 8.1 Create TestONTopology object - No Result
• 8.2 Topology view is correct and consistent across all ONOS nodes - PASS
• 8.3 Checking ONOS nodes - PASS

Case 3: Adding host Intents -

...

PASS

• 3.1 Install reactive forwarding app - PASS
• 3.2 Check app ids - PASS
• 3.3 Discovering Hosts( Via pingall for now ) - FAIL 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

...

• 7.1 Check that each switch has a master - PASS
• 7.2 Read device roles from ONOS - PASS
• 7.3 Check for consistency in roles from each controller - PASS
• 7.4 Compare switch roles from before failure - FAIL 7.5 Get the intents and compare across all nodes - PASS
• 7.6 5 Check for consistency in Intents from each controller - PASS
• 7.7 6 Get the OF Table entries and compare to before component failure - FAIL
• 7.8 7 Check the continuous pings to ensure that no packets were dropped during component failure - FAIL

...

• 15.1 Run for election on each node - PASS
• 15.2 Check that each node shows the same leader - PASS
• 15.3 Find current leader and withdraw - PASS
• 15.4 Make sure new leader is elected - PASS
• 15.5 Run for election on old leader( just so everyone is in the hat ) - PASS
• 15.6 Leader did not change when old leader re-ran - PASS

Case 17: Check for basic functionality with distributed primitives -

...

PASS

Test the methods of the distributed primitives (counters and sets) throught the cli

• 17.1 Increment and get a default counter on each node - PASS
• 17.2 Increment and get an in memory counter on each node - PASS
• 17.3 Check counters are consistant across nodes - FAIL PASS
• 17.4 Counters we added have the correct values - FAIL PASS
• 17.5 Distributed Set get - FAIL PASS
• 17.6 Distributed Set size - FAIL PASS
• 17.7 Distributed Set add() - FAIL PASS
• 17.8 Distributed Set addAll() - FAIL PASS
• 17.9 Distributed Set contains() - FAIL PASS
• 17.10 Distributed Set containsAll() - PASS
• 17.11 Distributed Set remove() - FAIL PASS
• 17.12 Distributed Set removeAll() - FAIL PASS
• 17.13 Distributed Set addAll() - PASS
• 17.14 Distributed Set clear() - PASS
• 17.15 Distributed Set addAll() - PASS
• 17.16 Distributed Set retain() - PASS

...