Versions Compared

Old Version 5

changes.mady.by.user Jenkins Technical User

Saved on

compared with

New Version Current

changes.mady.by.user Jenkins Technical User

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

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

commit 35a35c52a9d7b2d4e9d27a861a4f33e48e081285 d95d3524caff5449aded4ff9397c3ed717fc91e6 (HEAD -] , origin/onos-2.2, origin/ onos-2.2)
Author: ONOS Jenkins User [jenkins@onlab.usJian Li [pyguni@gmail.com]
AuthorDate: Fri Thu Aug 30 2012 18:1103:47 2019 30 2021 +00000900
Commit: ONOS Jenkins User [jenkins@onlab.usJian Li [pyguni@gmail.com]
CommitDate: Fri Thu Aug 30 2012 18:1158:47 2019 19 2021 +0000
Starting snapshot 2.2.1-SNAPSHOT0900

Add default route option to kubevirt network

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

...

  • 1.1 Constructing test variables - PASS (tick)

Case 2: Starting

...

up

...

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

Case 10: Start Mininet topology with OF 1.0 switches - PASS

Start mininet topology with OF 1.0 switches to test intents, exits out if topology did not start correctly

  • 10.1 Starting Mininet topology with OF 1.0 switches - PASS (tick)

Case 12: Assign switches to controllers - PASS

Assign OF 1.0 switches to ONOS nodes

  • 12.1 Assigning switches to controllers - PASS (tick)

Case 13: Create scapy components - PASS

  • 13.1 Create scapy components - No Result (warning)
  • 13.2 Start scapy components - PASS (tick)

Case 15: Discover all hosts using scapy - PASS

  • 15.1 Send packets from each host to the first host and confirm onos discovery - PASS (tick)
  • 15.2 Populate hostsData - PASS (tick)

Case 16: Balance mastership of switches - PASS

  • 16.1 Balancing mastership of switches - PASS (tick)

...

1

...

node(s)

...

ONOS

...

Case 2000: Point Intents Test - 1 NODE(S) - OF 1.0 - Using Flow Rules - FAIL

...

cluster

...

- FAIL

...

  • Assertion Result for SDNIP-ICMP IPV4 using TCP point intents
  • Install Intent State Passed
  • Flow duration check Passed
  • Initial Intent State Passed
  • Initial Flow State Passed
  • Initial Ping Failed
  • Link Down Passed
  • Link Down Intent State Passed
  • Link Down Flow State Passed
  • Link Down Topology State Passed
  • Link Down Pingall Failed
  • Link Up Passed
  • Link Up Intent State Passed
  • Link Up Flow State Passed
  • Link Up Topology State Passed
  • Link Up Scapy Packet Recieved Failed
  • Remove Intents PassedAfter removing intents Flow State Passed

...

Case 3000: Single to Multi Point Intents Test - 1 NODE(S) - OF 1.0 - Using Flow Rules - PASS

This test case will test single point to multi point 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.0 OVS running in Mininet and compile intents using Flow Rules

  • 3000.1 NOOPTION: Install and test single point to multi point intents - PASS (tick)
  • 3000.2 IPV4: Install and test single point to multi point intents - PASS (tick)
  • 3000.3 IPV4_2: Add single point to multi point intents - PASS (tick)
  • 3000.4 VLAN: Add single point to multi point intents - PASS (tick)
  • 3000.5 VLAN: Add single point to multi point intents - PASS (tick)

Case 4000: Multi To Single Point Intents Test - 1 NODE(S) - OF 1.0 - Using Flow Rules - PASS

This test case will test single point to multi point 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.0 OVS running in Mininet and compile intents using Flow Rules

  • 4000.1 NOOPTION: Add multi point to single point intents - PASS (tick)
  • 4000.2 IPV4: Add multi point to single point intents - PASS (tick)
  • 4000.3 IPV4_2: Add multi point to single point intents - PASS (tick)
  • 4000.4 VLAN: Add multi point to single point intents - PASS (tick)
  • 4000.5 VLAN: Add multi point to single point intents - PASS (tick)
  • 4000.6 ENCAPSULATION: Add multi point to single point intents - PASS (tick)

Case 5000: Test host mobility with host intents - 1 NODE(S) - OF 1.0 - Using Flow Rules - PASS

  • 5000.1 Testing host mobility by moving h1 from s5 to s6 - PASS (tick)
  • 5000.2 IPV4: Add host intents between h1 and h9 - PASS (tick)

Case 6000: Test Multi to Single End Point Failure - 1 NODE(S) - OF 1.0 - Using Flow Rules - PASS

  • 6000.1 Installing Multi to Single Point intents with no options set - PASS (tick)
  • 6000.2 Installing Multi to Single Point intents with partial failure allowed - PASS (tick)
  • 6000.3 NOOPTION: Install and test single point to multi point intents - PASS (tick)
  • 6000.4 NOOPTION: Install and test single point to multi point intents with partial failures allowed - PASS (tick)

Case 18: Stop Mininet and Scapy - PASS

Stopping the current mininet topology to start up fresh

  • 18.1 Stopping and Removing Scapy Host Components - PASS (tick)
  • 18.2 Stopping Mininet - PASS (tick)

Case 19: Copy karaf logs - PASS

Copying the karaf logs to preserve them throughreinstalling ONOS

...