Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Published from Jenkins build: https://jenkins.onosproject.org/job/FUNC-pipeline-1.13/1037/

...

HTML
<img src="https://jenkins.onosproject.org/view/QA/job/postjob-VM/lastSuccessfulBuild/artifact/FUNCintentRest_onos-1.13_20-builds_graph.jpg", alt="FUNCintentRest", style="width:525px;height:350px;border:0">

commit 6f58cf1e5aae371cb8c7e0ad69552f3e68672f05 848a7c61cddcce0db50877af5b6af1eae3edc22e (HEAD -] onos-1.13, origin/onos-1.13)
Author: Saurav Das [sauravdas@alumni.stanford.edursahot036 [ruchi_sahota@comcast.com]
AuthorDate: Thu Mon Oct 11 15 17:2946:24 14 2018 -07000400
Commit: Saurav Das Thomas Vachuska [sauravdas@alumnitom@opennetworking.stanford.eduorg]
CommitDate: Thu Tue Oct 11 16 14:1449:12 2018 -0700
Allow applications to specify a few other packet-request flow priorities.20 2018 +0000

REST API support for packet-processors
--
(cherry picked from commit 4df80f17964cafba44e59065ffd5fe6e4a42ef56)

Case 1: Pull onos branch and build onos on Teststation. - PASS

...

  • 16.1 Balancing mastership of switches - PASS (tick)

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

...

PASS

This test case tests Host intents using 3 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 - FAIL (error)
  • Assertion result for IPV4 host intent with mac addresses
  • Install Intent State Passed
  • Flow duration check failed
  • PASS (tick)
  • 1000.2 DUALSTACK1: Add host intents between h3 and h11 - PASS (tick)
  • 1000.3 DUALSTACK2: Add host intents between h1 and h11 - PASS (tick)
  • 1000.4 1HOP: Add host intents between h1 and h3 - PASS (tick)
  • 1000.5 VLAN1: Add vlan host intents between h4 and h12 - PASS (tick)
  • 1000.6 Confirm that ONOS leadership is unchanged - PASS (tick)

...