Page History

...

commit 6584989c59151a1f84eaee250116ac83ebeb305e 088f4ce0f898457cc6b72d0998090df4ad7f87e6 (HEAD, origin/master, origin/HEAD, master)
Author: Yuta HIGUCHI [y-higuchi@ak.jp.nec.comYi Tseng [yi@opennetworking.org]
AuthorDate: Fri Tue Aug 18 1315 10:0954:41 14 2017 -0700
Commit: Ray Milkey Carmelo Cascone [ray@opennetworkingcarmelo@opennetworking.org]
CommitDate: Sat Sun Aug 19 0220 23:5214:33 10 2017 +0000
minor fixes around HexString
[ONOS-6916] Fix bmv2 flow programmable and PiCriterionTranslator

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

...

• 2.1 Assign switches to controllers - PASS

Case 8: Compare ONOS Topology view to Mininet topology - PASS

Compare topology objects between Mininet and ONOS

• 8.1 Comparing ONOS topology to MN topology - PASS
• 8.2 Hosts view is consistent across all ONOS nodes - PASS
• 8.3 Hosts information is correct - PASS
• 8.4 Host attachment points to the network - PASS
• 8.5 Clusters view is consistent across all ONOS nodes - PASS
• 8.6 There is only one SCC - PASS
• 8.7 Device information is correct - PASS
• 8.8 Links are correct - PASS
• 8.9 Hosts are correct - PASS
• 8.10 Checking ONOS nodes - PASS

Case 21: Assigning Controller roles for switches - PASS

Check that ONOS is connected to each device. Then manually assign mastership to specific ONOS nodes using 'device-role'

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

Case 3: Adding host Intents - FAIL