Page History

...

commit 516a8ca0bcdd81670c4505f0301263fcc17f4e06 6a8cb4f3e54bb186331e7fbb4062551f63366461 (HEAD, origin/master, origin/HEAD, master)
Author: Yuta HIGUCHI [y-higuchi@ak.jp.nec.comSimon Hunt [simon@onlab.us]
AuthorDate: Fri Tue Aug 5 9 15:1008:00 57 2016 -0700
Commit: Gerrit Code Review [gerrit@onlabSimon Hunt [simon@onlab.us]
CommitDate: Fri Tue Aug 5 239 20:0031:01 24 2016 +0000
Typo fix-0700

ONOS-4970: Device data for topology view -- WIP.

Case 1: Constructing test variables and building ONOS package - PASS

...

• 16.1 Balancing mastership of switches - PASS

Case 1000: Host Intents Test - 1 NODE(S) - OF 1.3 - Using Flow Rules -

...

FAIL

This test case tests Host intents using 1 node(s) cluster; Different type of hosts will be tested in each step such as IPV4, Dual stack, VLAN etc; The test will use OF 1.3 OVS running in Mininet and compile intents using Flow Rules

• 1000.1 IPV4: Add and test host intents between h1 and h9 - PASS FAIL
• Assertion result for IPV4 host intent with mac addresses
• Install Intent State Passed
• Flow duration check failed
• 1000.2 DUALSTACK1: Add host intents between h3 and h11 - PASS
• 1000.3 DUALSTACK2: Add host intents between h1 and h11 - PASS
• 1000.4 1HOP: Add host intents between h1 and h3 - PASS
• 1000.5 VLAN1: Add vlan host intents between h4 and h12 - PASS
• 1000.6 Confirm that ONOS leadership is unchanged - PASS

...