Page History

...

commit 4f56bbd82905e316b57be30b543158e6fb1f368a da1dfa67ee811e67d9eb885294ab8e34b0d683f4 (HEAD, origin/master, origin/HEAD, master)
Author: Yuta HIGUCHI [y-higuchi@ak.jp.nec.Jian Li [pyguni@gmail.com]
AuthorDate: Thu Tue Apr 27 1725 01:3856:20 19 2017 -0700+0900
Commit: Yuta HIGUCHI [y-higuchi@ak.jp.nec.Jian Li [pyguni@gmail.com]
CommitDate: Thu Sat Apr 27 1729 04:38:20 14 2017 -0700
Cosmetic fix about constant name
+0000

[ONOS-6349] Augment mapping CLI to print out json formatted string

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

...

• 17.1 Enabling Flow Objectives - PASS

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

...

PASS

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 Objectives

• 1000.1 IPV4: Add and test host intents between h1 and h9 - FAIL
• Assertion result for IPV4 host intent with mac addresses
• Install Intent State Passed
• Flow duration check failed
• PASS
• 1000.2 DUALSTACK1: Add host intents between h3 and h11 - FAIL
• Assertion Result for dualstack IPV4 with MAC addresses
• Install Intent State Passed
• Flow duration check failed
• PASS
• 1000.3 DUALSTACK2: Add host intents between h1 and h11 - FAIL
• Assertion Result for dualstack2 host intent
• Install Intent State Passed
Flow duration check failed
• 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

...