Versions Compared

Old Version 212

changes.mady.by.user Jenkins Technical User

Saved on

compared with

New Version 213

changes.mady.by.user Jenkins Technical User

Saved on

Key

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

...

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

commit 2edfeefc3a1d0b8d453a9986650c787d7253f58e d29bc1ceef7c540ce57820d80ed5aa402fa6c25a (HEAD -] master, origin/master, origin/HEAD)
Author: Jordan Halterman Ray Milkey [jordan@opennetworkingray@opennetworking.org]
AuthorDate: Tue Jan 16 14:59:49 Mar 13 11:57:11 2018 -08000700
Commit: Jordan Halterman Thomas Vachuska [jordan@opennetworkingtom@opennetworking.org]
CommitDate: Thu Fri Mar 15 1016 20:3230:13 05 2018 -0700
[ONOS-7379] Use atomic operations for flow table updates to avoid losing flows during updates+0000

Improve unit test coverage for basic config classes

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

...

  • 2.1 Apply cell to environment - PASS (tick)
  • 2.2 Uninstalling ONOS package - PASS (tick)
  • 2.3 Creating ONOS package - PASS (tick)
  • 2.4 Installing ONOS package - PASS (tick)
  • 2.5 Set up ONOS secure SSH - PASS (tick)
  • 2.6 Checking ONOS service - PASS (tick)
  • 2.7 Starting ONOS CLI sessions - PASS (tick)

Case 3: Compare ONOS Topology view to Mininet topology -

...

FAIL

Compare topology elements between Mininet and ONOS

  • 3.1 Copy Mininet topology file - PASS (tick)
  • 3.2 Setup Mininet Topology - PASS (tick)
  • 3.3 Assign switch to controller - PASS (tick)
  • 3.4 Comparing Mininet topology to ONOS topology - PASS (tick)FAIL (error)
    • ONOS incorrectly discovered the topology
  • 3.5 Create hosts and start scapy - No Result (warning)
  • 3.6 Start scapy components - PASS (tick)

Case 5: Verify Group of type All are successfully Added -

...

Install a Group of type ALL Verify the Group is Added Add a flow using the group Send a packet that verifies the action bucket of the group

  • 5.1 Add Group using Rest api - PASS (tick)
  • 5.2 Check groups are in ADDED state - FAIL (error)
    • All Group is not in Added State
  • 5.3 Adding flow with Group using rest api - PASS (tick)
  • 5.4 Testing Group by sending packet using Scapy - PASS (tick)

Case 6: Delete the Group and Flow added through Rest api - PASS

...

No Result

...

  • 5

Case 7: Verify Group of type INDIRECT are successfully Added - No Result

  • 7.1 Add Group using Rest api - PASS (tick)