Versions Compared

Key

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

...

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

commit c90af240ebf85b2954d414afceafddca5b7d5ef6 48f1033bf1fb0b06c2e57962f6b110c231811533 (HEAD -] master, origin/master, origin/HEAD)
Author: Daniel Park [dan.mcpark84@gmail.com]
AuthorDate: Mon Jul 30 13:00:32 Thu Aug 2 10:57:27 2018 +0900
Commit: Andrea Campanella Jian Li [andrea@opennetworkingpyguni@gmail.orgcom]
CommitDate: Tue Jul 31 01:11:28 Thu Aug 2 14:00:17 2018 +0000
Implements ICMPEcho packet type
Adds default router option only when the gateway is set in subnet.

Case 1: Starting up 7 node(s) ONOS cluster - PASS

Set up ONOS with 7 node(s) ONOS cluster

  • 1.1 Constructing test variables - PASS (tick)
  • 1.2 Apply cell to environment - PASS (tick)
  • 1.3 Uninstalling Atomix - PASS (tick)
  • 1.4 Uninstalling ONOS package - PASS (tick)
  • 1.5 Starting Mininet - PASS (tick)
  • 1.6 Creating ONOS package - PASS (tick)
  • 1.7 Installing Atomix - PASS (tick)
  • 1.8 Installing ONOS package - PASS (tick)
  • 1.9 Set up ONOS secure SSH - PASS (tick)
  • 1.10 Checking ONOS service - PASS (tick)
  • 1.11 Starting ONOS CLI sessions - PASS (tick)
  • 1.12 Checking ONOS nodes - PASS (tick)
  • 1.13 Activate apps defined in the params file - No Result (warning)
  • 1.14 Set ONOS configurations - PASS (tick)
  • 1.15 Check app ids - PASS (tick)
  • 1.16 Set logging levels - PASS (tick)

Case 2: Assigning devices to controllers - PASS

Assign switches to ONOS using 'ovs-vsctl' and check that an ONOS node becomes the master of the device.

  • 2.1 Assign switches to controllers - PASS (tick)

Case 8: Compare ONOS Topology view to Mininet topology - PASS

Compare topology objects between Mininet and ONOS

  • 8.1 Comparing ONOS topology to MN topology - PASS (tick)
  • 8.2 Hosts view is consistent across all ONOS nodes - PASS (tick)
  • 8.3 Hosts information is correct - PASS (tick)
  • 8.4 Host attachment points to the network - PASS (tick)
  • 8.5 Clusters view is consistent across all ONOS nodes - PASS (tick)
  • 8.6 There is only one SCC - PASS (tick)
  • 8.7 Device information is correct - PASS (tick)
  • 8.8 Links are correct - PASS (tick)
  • 8.9 Hosts are correct - PASS (tick)
  • 8.10 Checking ONOS nodes - PASS (tick)

Case 21: Assigning Controller roles for switches - PASS

Check that ONOS is connected to each device. Then manually assign mastership to specific ONOS nodes using 'device-role'

  • 21.1 Assign mastership of switches to specific controllers - PASS (tick)
  • 21.2 Check mastership was correctly assigned - PASS (tick)

Case 3: Adding host Intents - FAIL